Skip to main content

zmerge ☂️

PyPI Test Docs

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 search index and one link check across all projects.
  • Links that work everywhere. Link between projects with their published URLs; zmerge turns them into validated relative links.
  • Per-project settings. zmerge merges the markdown extensions, plugins, mkdocstrings options and snippets of every project.
  • Local or git, TOML or YAML. Include projects from local paths or git repositories, configured with a zensical.toml or an mkdocs.yml.
  • Fast. Hardlinks instead of copies, incremental re-assembly in milliseconds and live previews with zmerge serve.

Installation

uv tool install zmerge --with mkdocstrings-python  # mkdocstrings-python only if you render API docs

Quick start

Include projects in the nav of an umbrella project's zensical.toml, as 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" },
  { Typer = "!include git+https://github.com/fastapi/typer.git" },
]

[project.markdown_extensions.admonition]
[project.markdown_extensions.toc]
permalink = true

Build or preview the merged site:

zmerge build --strict
zmerge serve

zmerge generates .zmerge/ and .zmerge.toml next to the umbrella zensical.toml. Don't edit or commit them:

printf '.zmerge/\n.zmerge.toml\n' >> .gitignore

Read the documentation for the configuration, links between projects and limitations. The docs are built with zmerge themselves: their example merges lev and Typer from GitHub, see zensical.toml.

Development

uv sync
uv run pytest
uv run prek run --all-files
uv run zmerge serve

Metadata

Release files for zmerge 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zmerge 0.2.0
File Size Uploaded Provenance
zmerge-0.2.0.tar.gz 29.5 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for zmerge 0.2.0
File Interpreter ABI Platform
zmerge-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 63.2 kB

Release files / zmerge-0.2.0.tar.gz

Download URL zmerge-0.2.0.tar.gz
Size 29.5 kB
Tags Source
SHA-256 checksum
How to use checksums
2e9e703ce3f652fadba5d2466f7e10db65844e274afec3bd38dc8e58063eaf8c
BLAKE2b-256 checksum
How to use checksums
a000f4c59d68e89a22acc1b27653be5590ff6b783339e02cb81cd625c9a23423
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 24, 2026.

Transparency log

Release files / zmerge-0.2.0-py3-none-any.whl

Download URL zmerge-0.2.0-py3-none-any.whl
Size 33.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0115ba01f45f7bf0c2ebb34f8921ac83d82af72fae62a7825ffffe1f2fc607b2
BLAKE2b-256 checksum
How to use checksums
4f59c21a450161715fd62494edc5858a2c0c45fa1931506d4b35bca37326d88e
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 24, 2026.

Transparency log

Security for zmerge 0.2.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.

Select from 2 files

Attestation for zmerge-0.2.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 24, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page