bottom/docs
Michal Bryxí e4f3b6911a
docs: Which table goes "flags" under? (#1452)
- There is currently no indication under which [table](https://toml.io/en/v1.0.0#table) do "flags" go in the config file.
- I think having that being explicitly spelled out & having an example saves quite a bit of people's time. Would for me 🙃
2024-04-30 11:13:23 -04:00
..
content docs: Which table goes "flags" under? (#1452) 2024-04-30 11:13:23 -04:00
.gitignore docs: change code font and enable privacy (#1381) 2024-01-11 03:46:28 -05:00
README.md docs: add script to serve mkdocs locally 2023-02-04 04:58:16 -05:00
mkdocs.yml other: add json schema (#1382) (#1394) 2024-02-02 02:24:23 -05:00
requirements.txt docs: bump deps as of 2024-03-23 (#1432) 2024-03-23 02:31:13 -04:00
serve.sh add last revision date (#1380) 2024-01-11 03:20:35 -05:00

README.md

Extended Documentation

This is where the extended documentation resides, hosted on GitHub Pages. We use MkDocs, Material for MkDocs, and mike.

Documentation is currently built using Python 3.11, though it should work fine with older versions.

Running locally

One way is to just run serve.sh. Alternatively, the manual steps are:

# Change directories to the documentation.
cd docs/

# Create and activate venv.
python -m venv venv
source venv/bin/activate

# Install requirements
pip install -r requirements.txt

# Run mkdocs
venv/bin/mkdocs serve

Deploying

Deploying is done via mike.

Nightly

cd docs
mike deploy nightly --push

Stable

cd docs

# Rename the previous stable version
mike retitle --push stable $OLD_STABLE_VERSION

# Set the newest version as the most recent stable version
mike deploy --push --update-aliases $RELEASE_VERSION stable

# Append a "(stable)" string to the end.
mike retitle --push $RELEASE_VERSION "$RELEASE_VERSION (stable)"