📖 [Docs]: Documentation repositories have one documentation root

[Marius Storhaug (MariusStorhaug)]

The Repository Standard now says where documentation content belongs in a repository whose product is content. Previously it answered which surface owns the docs for modules, libraries, services, CLIs, applications, Actions, and reusable workflows — but for a documentation repository it stopped at "the published site is the product", leaving the placement of the content itself unstated.

New: A documentation repository has one documentation root

Content lives in one folder, never spread across the repository root. docs/ is the default; a generator's source root such as src/docs/ applies when the site tooling needs one. The repository root stays reserved for the README, the tooling, and the governance files.

The practical effect is that a reader can tell content from machinery by looking at the root listing, without opening a folder:

.
├── README.md          ← start page
├── scripts/           ← tooling
└── docs/              ← the content

Technical Details

One paragraph added to Product documentation defaults in src/docs/Ways-of-Working/Repository-Standard.md, after the repository-type table. The table answers which surface owns the docs per type; the paragraph answers where content sits in the repository, which applies to every row.

Both roots are named deliberately. This repository keeps its own content under src/docs/ because Zensical needs a source root, so naming only docs/ would have made the standard disagree with the repository that publishes it.

No new section, per Documentation Model — one fact in one place, in the section that already owns the topic.

The gap surfaced in practice. In Storhaug-ting/Kilden, a repository of external source material, each source was given a folder directly in the repository root. With one source it read fine; with twelve on the way the root became a mix of tooling, governance files, and content. It took a correction from the repository owner to move the material under docs/ — Storhaug-ting/Kilden#4 — which is the correction this paragraph is meant to make unnecessary next time.

Implementation plan progress: the single task in #127 is complete.

Related issues

• Fixes Define where documentation content lives in a documentation repository #127