Vincent made some good points. I have experiences writing this kind of
books, and I can testify. I have written the Museum of Spatial
Transcriptomics book, and the Voyager vignettes probably will
collectively become book sized as we are adding more vignettes about
different technologies. It tak
Vincent made some good points. I have experiences writing this kind of
books, and I can testify. I have written the Museum of Spatial
Transcriptomics book, and the Voyager vignettes probably will
collectively become book sized as we are adding more vignettes about
different technologies. It tak
On Thu, Jan 12, 2023 at 5:29 AM Lluís Revilla
wrote:
> Hi all,
>
> Perhaps instead of long vignettes, it would be better to use a book hosted
> and in sync with the packages at Bioconductor.
> There are already a few: https://www.bioconductor.org/books/release/
> But I was not able to find how to
Hi all,
Perhaps instead of long vignettes, it would be better to use a book hosted
and in sync with the packages at Bioconductor.
There are already a few: https://www.bioconductor.org/books/release/
But I was not able to find how to submit such bookdowns to Bioconductor (I
briefly searched the web
I am glad you brought this up here, and I welcome further discussion on
this mailing list. It is important to understand the constraints on
development
that arise from Bioconductor's package guidelines.
I don't think we want to change the limits on package payload size without
understanding the c
Hi Adam,
I also got this problem, and I would like some input from Bioc Core
Team. I worked around it by writing a minimal vignette in the main
branch. Then I made a documentation branch, where I have the same code
as in main branch, but with more elaborate vignettes used to build a
pkgdown w
