This repository collects the documentation from multiple repositories into one deployment, enabling users of very large codebases to maintain their docs close to the code, but navigate across all of their docs in one deployment.

This is an example of using mkdocs-monorepo-plugin to display the docs of several repositories in one mkdocs deployment.

1. Install requirements with pip install -r requirements.txt
2. Run just update-docs to install the docs from the repos in repos.yml on your local machine
3. Run just build to rebuild the docs
4. Run just docs to serve the docs
5. View the docs at localhost:8000

Example result:

• backstage/mkdocs-monorepo-plugin
• mkdocs-monorepo-plugin demo site: Cats API (sample project source code)

Requirements:

1. Add and install the requirements -- mkdocs, mkdocs-material (for the theme) and mkdocs-monorepo-plugin (to support multiple repos)

Example pyproject.toml:

dependencies = ["django>=3.2", "mkdocs", "mkdocs-material", "mkdocs-monorepo-plugin"]

Then run pip install . in your virtual environment to install those packages.

2. Add a mkdoc.yml file at the root level of the repo.

Example mkdoc.yml in django-email-relay:

site_name: django-email-relay
repo_name: "williln/django-email-relay"
repo_url: "https://github.com/williln/django-email-relay"

nav:
  - Home: "index.md"
  - Configuration: "configuration/index.md"
  - Contributing: "contributing/index.md"
  - Just: "development/just.md"
  - Installation: "installation/index.md"

The important section is the nav element. See Adding Pages in the MkDocs docs.

📌 For each repo you add, you will need to set up the navigation via this mkdocs.yml file.

3. Commit the result to that repo.

4. Come back to this repo, central-docs. Add the repo to repos.yml:

repos:
  - name: django-email-relay
    url: https://github.com/williln/django-email-relay.git
    docs_path: docs/

5. Run locally

Run mkdocs serve in this repo to preview your changes.

TBD.

TBD. The plan is use GitHub webhooks to trigger a rebuild of these docs whenever any of the docs/ directories in repos.yaml has an update to its main branch. The docs would also rebuild on a push to this main branch (example: when a new repository is added).