vexy-mkdocs-tools
Documentation: https://vexy.dev/vexy-mkdocs-tools/
Fire-based CLI that bundles ProperDocs + MaterialX and the standard vexy- plugin set, so a site builds in one shot:
uvx vexy-mkdocs-tools build
Why
Every FontLab/Vexy MkDocs-style site repeats the same dependency list and the same wrapper script (clean docs/ but keep CNAME, optionally Flowmark-format src_docs/md/ first, then properdocs build, then write .nojekyll). This package owns the dependency set and the wrapper, so site repos shrink to "Markdown + mkdocs.yml".
Install
uv pip install vexy-mkdocs-tools # site builds
uv pip install "vexy-mkdocs-tools[flowmark]" # also Flowmark formatting
Or ad-hoc without installing:
uvx vexy-mkdocs-tools build
uvx --with flowmark vexy-mkdocs-tools build
Commands
| Command | What it does |
|---|---|
vmt build |
Flowmark-format src_docs/md/ (if available) → wipe docs/ (preserving CNAME) → properdocs build → write .nojekyll |
vmt build --no-format |
Skip the Flowmark step |
vmt serve |
properdocs serve with the same config |
vmt clean |
Wipe docs/ (preserving CNAME) without rebuilding |
vmt format |
Run Flowmark in place over src_docs/md/ |
vmt version |
Print installed version |
vexy-mkdocs-tools and vmt are aliases.
Site layout assumed
<repo>/
├── mkdocs/mkdocs.yml # config (--config to override)
├── src_docs/md/ # Markdown source (--src to override)
└── docs/ # build output (--docs to override)
The CLI walks up from cwd until it finds a directory containing both mkdocs/mkdocs.yml and src_docs/. Pass --root to skip the walk.
Bundled dependencies
ProperDocs 1.6.7+, MaterialX 10.1.4+, plus pymdown-extensions, mkdocs-awesome-nav, mkdocs-include-markdown-plugin, mkdocs-llmstxt, mkdocs-copy-to-llm, mkdocs-rss-plugin. The [flowmark] extra adds flowmark.
Develop
uv sync --extra dev
uv run python -m pytest -q
uvx ruff check src tests
./build.sh # docs (src_docs/ → docs/) + wheel/sdist + twine check
./publish.sh # gitnextver tag → build → uv publish (needs UV_PUBLISH_TOKEN)
Releases are tag-driven — push a vX.Y.Z tag and the release workflow ships to PyPI.
Docs
Full documentation, including the site-layout contract and the materialx theme note: https://vexy.dev/vexy-mkdocs-tools/.
License
Apache-2.0.
Metadata
Release files for vexy-mkdocs-tools 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vexy_mkdocs_tools-0.1.2.tar.gz | 13.0 kB | Without provenance | Details for vexy_mkdocs_tools-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vexy_mkdocs_tools-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for vexy_mkdocs_tools-0.1.2-py3-none-any.whl |
Total release size: 23.5 kB
Release files / vexy_mkdocs_tools-0.1.2.tar.gz
| Download URL | vexy_mkdocs_tools-0.1.2.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ed28d7af5eb7cdfa4222a92495cf0f39720bd591fb1741290459527585eef68
|
|
BLAKE2b-256 checksum How to use checksums |
4fe72786fe12add004024ff92f250cff0824dc65596b812e28997964abd2c0e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / vexy_mkdocs_tools-0.1.2-py3-none-any.whl
| Download URL | vexy_mkdocs_tools-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bda69656f131e35944c73d605bcdc856e5a7b4acbdb4689f4a5640935dfbe0ae
|
|
BLAKE2b-256 checksum How to use checksums |
e9fafabf09145692359259e853030998fc8b9f6ebe8ec1f55ae218e6e4bc6b0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for vexy-mkdocs-tools 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.