This repo contains the documentation source for: https://docs.foundries.io
Currently the docs are written in reStucturedText with Sphinx serving as the site generator.
Before beginning any work, review the contributing section.
To build the documentation, python3 and pip3
are required.
All required python modules are listed in requirements.txt
.
Install them with pip install -r requirements.txt
.
To avoid messing with your system-wide package storage, use virtualenv
.
This will set up the necessary environment for sphinx packages and place them here:
$ sudo apt-get install python3 python3-virtualenv
$ virtualenv -p /usr/bin/python3 venv
$ . ./venv/bin/activate
$ pip install -r requirements.txt
To build the html from rst files, from the top directory run:
$ make html
You can then open build/html/index.html
in your browser to view the
documentation.
While optional, before you begin working:
- Check Jira
See if someone is working on it. If there is no open issue, should there be? If the fix is going to take more than 30 minutes, consider opening one.
- Check the default branch to see the if the issue is still relevant.
The published pages reflect the documentation as of the latest release. The change may exist and will show up in the next release.
Try to use a fork rather than working on a foundriesio/docs
branch.
If on a direct branch, include your username.
Branch names should be descriptive and in the imperative (what you will do):
# If working on a branch of foundriesio/docs:
`git checkout -b kprosise/update-contributing-doc
# or for a fork:
git checkout -b spell-check-everything
For new pages, templates for most sections are in templates/
Use spelling and grammar checks and ask a technical writer if you have questions. Consult the style guide.
You can also "lint" the document. Install vale, and from this directory run:
vale sync
vale <PATH/FILE>
❗ make sure you are using Vale 2.16.0 or greater
Before pushing, check locally:
- links;
make linkcheck
- html;
make html
- lint:
vale <path_to_file(s)>
When opening a PR, tag a technical writer. They will merge it once reviews are in and suggestions considered. The PR template has additional steps.