The coralbook is in development and published with access limited to developers.
The source files to build the book live in github; They are in the coralbook repository of the odealab github site (https://github.com/odealab/coralbook). The github user @odealab owns the repository, and the users @maurolepore and @melisacbl are collaborators. This means that not only the user @odealab (presumably Aaron) but also @maurolepore and @melisacbl can clone the repository to their local computers and have full privilege change the book at odealab/coralbook.
The coralbook is published through bookdown.org, at: https://bookdown.org/odealab/coralbook2. The world cannot see the publication yet because it is in development; access is limited to the developers with an account in bookdown.org. For now, only odealab and maurolepore can view and change the published book. Melisa will be added after she gets an account in bookdown.org. (Melisa: To do this, go to https://bookdown.org/ and hit login at the top.)
I think this proves that bookdown is a convenient platform.
@melisacbl: What have you found about getting a DOI for the book through figshare and about citing it later (#4)?
Cheers,
@maurolepore
PS. What do you think about using github issues (and pull requests) to keep discussions and progress all in one place, the repository itself? This should be easier than keeping track of disparate emails (https://guides.github.com/features/issues/).
Hi @melisacbl,
The coralbook is in development and published with access limited to developers. The source files to build the book live in github; They are in the coralbook repository of the odealab github site (https://github.com/odealab/coralbook). The github user @odealab owns the repository, and the users @maurolepore and @melisacbl are collaborators. This means that not only the user @odealab (presumably Aaron) but also @maurolepore and @melisacbl can clone the repository to their local computers and have full privilege change the book at odealab/coralbook. The coralbook is published through bookdown.org, at: https://bookdown.org/odealab/coralbook2. The world cannot see the publication yet because it is in development; access is limited to the developers with an account in bookdown.org. For now, only odealab and maurolepore can view and change the published book. Melisa will be added after she gets an account in bookdown.org. (Melisa: To do this, go to https://bookdown.org/ and hit login at the top.) I think this proves that bookdown is a convenient platform.
@melisacbl: What have you found about getting a DOI for the book through figshare and about citing it later (#4)?
Cheers, @maurolepore
PS. What do you think about using github issues (and pull requests) to keep discussions and progress all in one place, the repository itself? This should be easier than keeping track of disparate emails (https://guides.github.com/features/issues/).