How to edit the Handbook#
Conda Environment Setup#
To edit these docs you need to clone the
catalyst-handbook repo and set up a conda environment:
git clone email@example.com:catalyst-cooperative/catalystcoop-handbook.git
We use the conda package manager to specify and update our development environment. We recommend using miniconda rather than the large pre-defined collection of scientific packages bundled together in the Anaconda Python distribution. You may also want to consider using mamba – a faster drop-in replacement for conda written in C++.
conda update conda conda env create --name handbook --file environment.yml conda activate handbook
Git Pre-commit Hooks#
Git hooks let you automatically run scripts at various points as you manage your source code. “Pre-commit” hook scripts are run when you try to make a new commit. These scripts can review your code and identify bugs, formatting errors, bad coding habits, and other issues before the code gets checked in. This gives you the opportunity to fix those issues before publishing them.
To make sure they are run before you commit any code, you need to enable the pre-commit hooks scripts with this command:
The scripts that run are configured in the .pre-commit-config.yaml file.
How to make changes#
To make changes to the handbook, edit the relevant markdown documents in the
docs/ directory. Once the changes are made
you can build the docs by running:
This command will build the docs and write the html files to
docs/_build/. You can view the docs locally by opening the
Once the docs are built locally, you can push your changes and open a PR for review. There is a GitHub Action that will build and deploy the changes
to Read the Docs.
If you don’t want to make edits with a CLI and code editor, you can use the GitHub UI:
Click the “Edit” button for the document you want to change:
Make your changes.
Select “Create a new branch for this comment and start a pull request”, add a commit message and select “Commit changes”:
Tag someone to review your changes.
The changes must be reviewed and approved by someone else to be merged into the