**Note: This is a modified version of backstage/mkdocs-monorepo-plugin with support for wildcard includes.
Note: This plugin is in beta. Whilst it is not expected to significantly change in functionality, it may not yet be fully compatible with other Mkdocs configuration and thus may break with some advanced configurations. Once these have been resolved and all bugs have been ironed out, we will move this to a stable release.
✚ This plugin enables you to build multiple sets of documentation in a single Mkdocs. It is designed to address writing documentation in Spotify's largest and most business-critical codebases (typically monoliths or monorepos).
✏️ Blog Post | 🐍 Python Package | ✚ Demo | 📕 Docs
-
Support for multiple
docs/
folders in Mkdocs. Having a singledocs/
folder in a large codebase is hard to maintain. Who owns which documentation? What code is it associated with? Bringing docs closer to the associated code enables you to update them better, as well as leverage folder-based features such as GitHub Codeowners. -
Support for multiple navigations. In Spotify, large repositories typically are split up by multiple owners. These are split by folders. By introducing multiple
mkdocs.yml
files along with multipledocs/
folder, each team can take ownership of their own navigation. This plugin then intelligently merges of the documentation together into a single repository. -
Support across multiple repositories. Using Git Submodules it is possible to merge documentation across multiple repositories into a single codebase dynamically.
-
The same great Mkdocs developer experience. It is possible to run
mkdocs serve
in the root to merge all of your documentation together, or in a subfolder to build specific documentation. Autoreload still works as usual. No more using symlinks!
It's easy to get started using PyPI and pip
using Python:
$ pip install mkdocs-monorepo-plugin
Take a look in our sample project for an example implementation, or see what it looks like after running mkdocs build
.
In general, this plugin introduces the !include
syntax in your Mkdocs navigation structure and then merges them together.
# /mkdocs.yml
site_name: Cats API
nav:
- Intro: 'index.md'
- Authentication: 'authentication.md'
- API:
- v1: '!include ./v1/mkdocs.yml'
- v2: '!include ./v2/mkdocs.yml'
plugins:
- monorepo
# /src/v1/mkdocs.yml
site_name: versions/v1
nav:
- Reference: "reference.md"
- Changelog: "changelog.md"
# /src/v2/mkdocs.yml
site_name: versions/v2
nav:
- Migrating to v2: "migrating.md"
- Reference: "reference.md"
- Changelog: "changelog.md"
$ tree .
├── docs
│ ├── authentication.md
│ └── index.md
├── mkdocs.yml
├── v1
│ ├── docs
│ │ ├── changelog.md
│ │ └── reference.md
│ └── mkdocs.yml
└── v2
├── docs
│ ├── changelog.md
│ ├── migrating.md
│ └── reference.md
└── mkdocs.yml
5 directories, 10 files
$ mkdocs build
$ tree ./site
├── 404.html
├── authentication
│ └── index.html
├── css
│ ├── base.css
│ ├── bootstrap-custom.min.css
│ └── font-awesome.min.css
├── fonts
│ ├── fontawesome-webfont.eot
│ ├── fontawesome-webfont.svg
│ ├── fontawesome-webfont.ttf
│ ├── fontawesome-webfont.woff
│ ├── fontawesome-webfont.woff2
│ ├── glyphicons-halflings-regular.eot
│ ├── glyphicons-halflings-regular.svg
│ ├── glyphicons-halflings-regular.ttf
│ ├── glyphicons-halflings-regular.woff
│ └── glyphicons-halflings-regular.woff2
├── img
│ ├── favicon.ico
│ └── grid.png
├── index.html
├── js
│ ├── base.js
│ ├── bootstrap-3.0.3.min.js
│ └── jquery-1.10.2.min.js
├── sitemap.xml
├── sitemap.xml.gz
└── versions
├── v1
│ ├── changelog
│ │ └── index.html
│ └── reference
│ └── index.html
└── v2
├── changelog
│ └── index.html
├── migrating
│ └── index.html
└── reference
└── index.html
13 directories, 28 files
- Update the CHANGELOG.md.
- Bump up the version number in
setup.py
which triggers the release workflow on GitHub Actions to publish a new version in PyPI.
- Python 3 — 3.6, 3.7
- Mkdocs 1.0.4 and above.
Check out our CHANGELOG.md for details.
Copyright 2020-2021 © The Backstage Authors. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: https://www.linuxfoundation.org/trademark-usage
Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0
Check out our CONTRIBUTING for more details.