docs: bump mike to v2.0.0 (#1318)

* bump mike

* bump some docs

* update some settings and serve script to use mike
This commit is contained in:
Clement Tsang 2023-11-16 03:17:21 -05:00 committed by GitHub
parent 04713bf81d
commit 036366274e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 12 additions and 17 deletions

View File

@ -31,14 +31,14 @@ There are a few areas where documentation changes are often needed:
<h3>Help menu</h3> <h3>Help menu</h3>
For changes to the help menu, try to refer to the existing code within `src/constants.rs` on how the help menu is generated. For changes to the help menu, try to refer to the existing code within [`src/constants.rs`](https://github.com/ClementTsang/bottom/blob/master/src/constants.rs) on how the help menu is generated.
<h3>Extended documentation</h3> <h3>Extended documentation</h3>
For changes to the extended documentation, you'll probably want Python 3.11 (older versions should be fine though), For changes to the extended documentation, you'll probably want at least Python 3.11 (older versions should be fine
[MkDocs](https://www.mkdocs.org/), [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/), though), [MkDocs](https://www.mkdocs.org/), [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/),
`mdx_truly_sane_lists`, and optionally [Mike](https://github.com/jimporter/mike) installed to provide live reloading `mdx_truly_sane_lists`, and optionally [Mike](https://github.com/jimporter/mike) installed. These can help with
and preview for your changes. They aren't needed, but it'll help with validating your changes. validating your changes locally.
You can do so through `pip` or your system's package managers. If you use `pip`, you can use venv to cleanly install You can do so through `pip` or your system's package managers. If you use `pip`, you can use venv to cleanly install
the documentation dependencies: the documentation dependencies:
@ -47,15 +47,8 @@ There are a few areas where documentation changes are often needed:
# Change directories to the documentation. # Change directories to the documentation.
cd docs/ cd docs/
# Create and activate venv. # Create venv, install the dependencies, and serve the page.
python -m venv venv ./serve.sh
source venv/bin/activate
# Install requirements
pip install -r requirements.txt
# Run mkdocs
venv/bin/mkdocs serve
``` ```
This will serve a local version of the docs that you can open on your browser. It will update as you make changes. This will serve a local version of the docs that you can open on your browser. It will update as you make changes.

View File

@ -113,6 +113,8 @@ markdown_extensions:
plugins: plugins:
- tags - tags
- search - search
- mike:
canonical_version: stable
extra: extra:
# Versioning # Versioning

View File

@ -2,5 +2,5 @@ mkdocs == 1.5.3
mkdocs-material == 9.4.8 mkdocs-material == 9.4.8
mkdocs-material-extensions == 1.3 mkdocs-material-extensions == 1.3
mdx_truly_sane_lists == 1.3 mdx_truly_sane_lists == 1.3
mike == 1.1.2 mike == 2.0.0

View File

@ -11,10 +11,10 @@ if [ ! -d $VENV_PATH ]; then
source ./venv/bin/activate; source ./venv/bin/activate;
pip install --upgrade pip; pip install --upgrade pip;
pip install -r requirements.txt; pip install -r requirements.txt;
./venv/bin/mkdocs serve; ./venv/bin/mike serve;
else else
echo "venv already found."; echo "venv already found.";
source ./venv/bin/activate; source ./venv/bin/activate;
./venv/bin/mkdocs serve; ./venv/bin/mike serve;
fi; fi;