From 3ab36c1fb4f3aa63f02bccc54a6091616226d25a Mon Sep 17 00:00:00 2001 From: Peter Selby Date: Mon, 5 Jun 2023 14:32:01 -0400 Subject: [PATCH] update README --- Manubot-README.md | 119 ++++++++++++++++++++++++++++++++++++++++++++++ README.md | 115 ++++---------------------------------------- 2 files changed, 128 insertions(+), 106 deletions(-) create mode 100644 Manubot-README.md diff --git a/Manubot-README.md b/Manubot-README.md new file mode 100644 index 0000000..d584039 --- /dev/null +++ b/Manubot-README.md @@ -0,0 +1,119 @@ +# Automated scholarly manuscripts on GitHub + + + +[![HTML Manuscript](https://img.shields.io/badge/manuscript-HTML-blue.svg)](https://plantbreeding.github.io/BrAPI-Manuscript2/) +[![PDF Manuscript](https://img.shields.io/badge/manuscript-PDF-blue.svg)](https://plantbreeding.github.io/BrAPI-Manuscript2/manuscript.pdf) +[![GitHub Actions Status](https://github.com/plantbreeding/BrAPI-Manuscript2/workflows/Manubot/badge.svg)](https://github.com/plantbreeding/BrAPI-Manuscript2/actions) + +## Manuscript description + + + +This repository is a template manuscript (a.k.a. rootstock). +Actual manuscript instances will clone this repository (see [`SETUP.md`](SETUP.md)) and replace this paragraph with a description of their manuscript. + +## Manubot + + + +Manubot is a system for writing scholarly manuscripts via GitHub. +Manubot automates citations and references, versions manuscripts using git, and enables collaborative writing via GitHub. +An [overview manuscript](https://greenelab.github.io/meta-review/ "Open collaborative writing with Manubot") presents the benefits of collaborative writing with Manubot and its unique features. +The [rootstock repository](https://git.io/fhQH1) is a general purpose template for creating new Manubot instances, as detailed in [`SETUP.md`](SETUP.md). +See [`USAGE.md`](USAGE.md) for documentation how to write a manuscript. + +Please open [an issue](https://git.io/fhQHM) for questions related to Manubot usage, bug reports, or general inquiries. + +### Repository directories & files + +The directories are as follows: + ++ [`content`](content) contains the manuscript source, which includes markdown files as well as inputs for citations and references. + See [`USAGE.md`](USAGE.md) for more information. ++ [`output`](output) contains the outputs (generated files) from Manubot including the resulting manuscripts. + You should not edit these files manually, because they will get overwritten. ++ [`webpage`](webpage) is a directory meant to be rendered as a static webpage for viewing the HTML manuscript. ++ [`build`](build) contains commands and tools for building the manuscript. ++ [`ci`](ci) contains files necessary for deployment via continuous integration. + +### Local execution + +The easiest way to run Manubot is to use [continuous integration](#continuous-integration) to rebuild the manuscript when the content changes. +If you want to build a Manubot manuscript locally, install the [conda](https://conda.io) environment as described in [`build`](build). +Then, you can build the manuscript on POSIX systems by running the following commands from this root directory. + +```sh +# Activate the manubot conda environment (assumes conda version >= 4.4) +conda activate manubot + +# Build the manuscript, saving outputs to the output directory +bash build/build.sh + +# At this point, the HTML & PDF outputs will have been created. The remaining +# commands are for serving the webpage to view the HTML manuscript locally. +# This is required to view local images in the HTML output. + +# Configure the webpage directory +manubot webpage + +# You can now open the manuscript webpage/index.html in a web browser. +# Alternatively, open a local webserver at http://localhost:8000/ with the +# following commands. +cd webpage +python -m http.server +``` + +Sometimes it's helpful to monitor the content directory and automatically rebuild the manuscript when a change is detected. +The following command, while running, will trigger both the `build.sh` script and `manubot webpage` command upon content changes: + +```sh +bash build/autobuild.sh +``` + +### Continuous Integration + +Whenever a pull request is opened, CI (continuous integration) will test whether the changes break the build process to generate a formatted manuscript. +The build process aims to detect common errors, such as invalid citations. +If your pull request build fails, see the CI logs for the cause of failure and revise your pull request accordingly. + +When a commit to the `main` branch occurs (for example, when a pull request is merged), CI builds the manuscript and writes the results to the [`gh-pages`](https://github.com/plantbreeding/BrAPI-Manuscript2/tree/gh-pages) and [`output`](https://github.com/plantbreeding/BrAPI-Manuscript2/tree/output) branches. +The `gh-pages` branch uses [GitHub Pages](https://pages.github.com/) to host the following URLs: + ++ **HTML manuscript** at https://plantbreeding.github.io/BrAPI-Manuscript2/ ++ **PDF manuscript** at https://plantbreeding.github.io/BrAPI-Manuscript2/manuscript.pdf + +For continuous integration configuration details, see [`.github/workflows/manubot.yaml`](.github/workflows/manubot.yaml). + +## License + + + +[![License: CC BY 4.0](https://img.shields.io/badge/License%20All-CC%20BY%204.0-lightgrey.svg)](http://creativecommons.org/licenses/by/4.0/) +[![License: CC0 1.0](https://img.shields.io/badge/License%20Parts-CC0%201.0-lightgrey.svg)](https://creativecommons.org/publicdomain/zero/1.0/) + +Except when noted otherwise, the entirety of this repository is licensed under a CC BY 4.0 License ([`LICENSE.md`](LICENSE.md)), which allows reuse with attribution. +Please attribute by linking to https://github.com/plantbreeding/BrAPI-Manuscript2. + +Since CC BY is not ideal for code and data, certain repository components are also released under the CC0 1.0 public domain dedication ([`LICENSE-CC0.md`](LICENSE-CC0.md)). +All files matched by the following glob patterns are dual licensed under CC BY 4.0 and CC0 1.0: + ++ `*.sh` ++ `*.py` ++ `*.yml` / `*.yaml` ++ `*.json` ++ `*.bib` ++ `*.tsv` ++ `.gitignore` + +All other files are only available under CC BY 4.0, including: + ++ `*.md` ++ `*.html` ++ `*.pdf` ++ `*.docx` + +Please open [an issue](https://github.com/plantbreeding/BrAPI-Manuscript2/issues) for any question related to licensing. diff --git a/README.md b/README.md index d584039..3f08407 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# Automated scholarly manuscripts on GitHub +# BrAPI Project Manuscript V2 @@ -10,110 +10,13 @@ -This repository is a template manuscript (a.k.a. rootstock). -Actual manuscript instances will clone this repository (see [`SETUP.md`](SETUP.md)) and replace this paragraph with a description of their manuscript. +This is an updated manuscript for the BrAPI Project and Community. The [first BrAPI paper](https://academic.oup.com/bioinformatics/advance-article/doi/10.1093/bioinformatics/btz190/5418796) +was focused on the technical aspects of BrAPI and its potential. This manuscript gives us an opportunity to report on the project success so far and show how that potential has become a reality. -## Manubot +## Helpful Links - - -Manubot is a system for writing scholarly manuscripts via GitHub. -Manubot automates citations and references, versions manuscripts using git, and enables collaborative writing via GitHub. -An [overview manuscript](https://greenelab.github.io/meta-review/ "Open collaborative writing with Manubot") presents the benefits of collaborative writing with Manubot and its unique features. -The [rootstock repository](https://git.io/fhQH1) is a general purpose template for creating new Manubot instances, as detailed in [`SETUP.md`](SETUP.md). -See [`USAGE.md`](USAGE.md) for documentation how to write a manuscript. - -Please open [an issue](https://git.io/fhQHM) for questions related to Manubot usage, bug reports, or general inquiries. - -### Repository directories & files - -The directories are as follows: - -+ [`content`](content) contains the manuscript source, which includes markdown files as well as inputs for citations and references. - See [`USAGE.md`](USAGE.md) for more information. -+ [`output`](output) contains the outputs (generated files) from Manubot including the resulting manuscripts. - You should not edit these files manually, because they will get overwritten. -+ [`webpage`](webpage) is a directory meant to be rendered as a static webpage for viewing the HTML manuscript. -+ [`build`](build) contains commands and tools for building the manuscript. -+ [`ci`](ci) contains files necessary for deployment via continuous integration. - -### Local execution - -The easiest way to run Manubot is to use [continuous integration](#continuous-integration) to rebuild the manuscript when the content changes. -If you want to build a Manubot manuscript locally, install the [conda](https://conda.io) environment as described in [`build`](build). -Then, you can build the manuscript on POSIX systems by running the following commands from this root directory. - -```sh -# Activate the manubot conda environment (assumes conda version >= 4.4) -conda activate manubot - -# Build the manuscript, saving outputs to the output directory -bash build/build.sh - -# At this point, the HTML & PDF outputs will have been created. The remaining -# commands are for serving the webpage to view the HTML manuscript locally. -# This is required to view local images in the HTML output. - -# Configure the webpage directory -manubot webpage - -# You can now open the manuscript webpage/index.html in a web browser. -# Alternatively, open a local webserver at http://localhost:8000/ with the -# following commands. -cd webpage -python -m http.server -``` - -Sometimes it's helpful to monitor the content directory and automatically rebuild the manuscript when a change is detected. -The following command, while running, will trigger both the `build.sh` script and `manubot webpage` command upon content changes: - -```sh -bash build/autobuild.sh -``` - -### Continuous Integration - -Whenever a pull request is opened, CI (continuous integration) will test whether the changes break the build process to generate a formatted manuscript. -The build process aims to detect common errors, such as invalid citations. -If your pull request build fails, see the CI logs for the cause of failure and revise your pull request accordingly. - -When a commit to the `main` branch occurs (for example, when a pull request is merged), CI builds the manuscript and writes the results to the [`gh-pages`](https://github.com/plantbreeding/BrAPI-Manuscript2/tree/gh-pages) and [`output`](https://github.com/plantbreeding/BrAPI-Manuscript2/tree/output) branches. -The `gh-pages` branch uses [GitHub Pages](https://pages.github.com/) to host the following URLs: - -+ **HTML manuscript** at https://plantbreeding.github.io/BrAPI-Manuscript2/ -+ **PDF manuscript** at https://plantbreeding.github.io/BrAPI-Manuscript2/manuscript.pdf - -For continuous integration configuration details, see [`.github/workflows/manubot.yaml`](.github/workflows/manubot.yaml). - -## License - - - -[![License: CC BY 4.0](https://img.shields.io/badge/License%20All-CC%20BY%204.0-lightgrey.svg)](http://creativecommons.org/licenses/by/4.0/) -[![License: CC0 1.0](https://img.shields.io/badge/License%20Parts-CC0%201.0-lightgrey.svg)](https://creativecommons.org/publicdomain/zero/1.0/) - -Except when noted otherwise, the entirety of this repository is licensed under a CC BY 4.0 License ([`LICENSE.md`](LICENSE.md)), which allows reuse with attribution. -Please attribute by linking to https://github.com/plantbreeding/BrAPI-Manuscript2. - -Since CC BY is not ideal for code and data, certain repository components are also released under the CC0 1.0 public domain dedication ([`LICENSE-CC0.md`](LICENSE-CC0.md)). -All files matched by the following glob patterns are dual licensed under CC BY 4.0 and CC0 1.0: - -+ `*.sh` -+ `*.py` -+ `*.yml` / `*.yaml` -+ `*.json` -+ `*.bib` -+ `*.tsv` -+ `.gitignore` - -All other files are only available under CC BY 4.0, including: - -+ `*.md` -+ `*.html` -+ `*.pdf` -+ `*.docx` - -Please open [an issue](https://github.com/plantbreeding/BrAPI-Manuscript2/issues) for any question related to licensing. ++ [Manuscript Content Folder](content) ++ [**HTML manuscript**](https://plantbreeding.github.io/BrAPI-Manuscript2/) ++ [**PDF manuscript**](https://plantbreeding.github.io/BrAPI-Manuscript2/manuscript.pdf) ++ [Manubot README](Manubot-README.md) ++ [Manubot Usage Instructions](USAGE.md)