Point it at a repository. The docs tree becomes a wiki, live from the source.
What it does
- A DOCUNEXUS.md in the repo declares the section order and grouping.
- Live from the source at any branch, tag or commit.
- Read-only, so git stays the source of truth.
- A provenance banner shows exactly which commit you are reading.
- Private repositories, with credentials held per person.
A repository, read as documentation
A DOCUNEXUS.md in the repo root names each section of the left
rail and sets its order.
The header shows the repository and the short commit you are reading. The switcher moves the whole doc set to another branch or tag, so you can read the documentation as it stood at any release.
Git stays the source of truth
Docs that live beside the code are reviewed and versioned with it. A wiki copy starts drifting the day it is made.
Git Docs never writes back. It gives those files navigation, search across every space, and a place beside the rest of your knowledge base.
What it needs
A git repository reachable over HTTPS. GitHub, GitLab, or anything else that speaks git.
A credential for a private repository. A read-only, repo-scoped token is enough, and is what we recommend.
Nothing in the repository itself. DOCUNEXUS.md is optional;
without it, a sensible tree is built from what is there.