zmerge 📚
zmerge merges the documentation of multiple Zensical projects into one site with working
links, a single navigation and one global search. It fills the gap left by the
mkdocs-monorepo-plugin until Zensical ships
an official solution.
- No custom Zensical, no plugins. zmerge assembles one regular Zensical project and builds it with
zensical build. - One site. One navigation, one global search, one link check across all projects.
- Links that work everywhere. Links between projects use the projects' published URLs and are rewritten into validated relative links when merging.
- Per-project settings. Markdown extensions, plugins, mkdocstrings options and snippets of every project are merged.
- Local or git. Include projects from local paths or straight from git repositories.
- Fast. Hardlinks instead of copies, incremental re-assembly in a few milliseconds, and
zmerge servefor live previews.
Installation
uv tool install zmerge --with mkdocstrings-python # mkdocstrings-python only if you render API docs
Quick start
Include other projects in the nav of an umbrella project's zensical.toml, just like with the
mkdocs-monorepo-plugin:
[project]
site_name = "My projects"
site_url = "https://example.github.io/"
nav = [
{ Home = "index.md" },
{ lev = "!include ../lev/zensical.toml" },
{ dame = "!include git+https://github.com/KarelZe/dame-rs.git" },
]
Then build or preview the merged site:
zmerge build --strict
zmerge serve
Add .zmerge/ and .zmerge.toml to your .gitignore. See the documentation for
the configuration, linking between projects and limitations, and
examples/karelze for a complete umbrella site.
Development
uv sync
uv run pytest
uv run prek run --all-files
uv run zensical serve
Metadata
Release files for zmerge 0.1.0
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 | |
|---|---|---|---|---|
| zmerge-0.1.0.tar.gz | 25.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zmerge-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.0 kB
Release files / zmerge-0.1.0.tar.gz
| Download URL | zmerge-0.1.0.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2121518680d7d4bf8d311d4c1714b74ed4e0e236d704d5c670e27110cc5ae47
|
|
BLAKE2b-256 checksum How to use checksums |
d1267da978d302da9dbd7ac9fffc72581ad3a8103b63c3c835afb39b84f85aaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / zmerge-0.1.0-py3-none-any.whl
| Download URL | zmerge-0.1.0-py3-none-any.whl |
|---|---|
| Size | 29.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50a6a912a979b11611b1ceab7bb8783fe24a5f4428d03ad259c4aaad6060ad6e
|
|
BLAKE2b-256 checksum How to use checksums |
28d1bbb2502a1eb318a1af50204b08f5c35bd6545ef54aeec11fac4bc8e23139
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for zmerge 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for zmerge-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA 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.