Docs single-sourcing: slug/id lists, the orphan set and the route-axis tables each have three owners #9
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
PCivil/folletos-digitales#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Carried over from the PR #6 review (round 5). None of this blocks anything today — every affected
statement is factually correct as written. The problem is that each fact has several owners, so the
next correction has to find all of them, and the last two rounds of that PR each had to touch three
files to fix one fact.
PR #6 de-duplicated the frozen-route list successfully: ADR-0002
owns it, and
CLAUDE.mdrule 5 anddocs/routes.mdlink to it instead of restating it. That is thepattern to apply to the three sets below.
1. Brochure slugs and topic ids are stated three times
CONTEXT.md:17-19,README.md:15,docs/routes.md:35-36— and the fourschool slugs a fourth time at
docs/routes.md:13.CONTEXT.md:25-26,README.md:16,docs/routes.md:37.This was raised in round 1 of the PR #6 review and reported closed in rounds 3 and 4, but only the
frozen-route half of that finding was actually done.
CONTEXT.mdis the natural owner (it is thedomain glossary);
README.mdanddocs/routes.mdshould link to it.2. The orphan / carve-out set is stated three times
docs/routes.md:20,docs/routes.md:27-29anddocs/adr/0002-frozen-legacy-routes.md:37-41eachstate which routes are orphaned and therefore outside the freeze. ADR-0002 already owns the frozen
list; it is the natural owner of the inverse too.
3. The mode / style axes are stated twice inside one file
docs/routes.md:31-36("Parameter values") anddocs/routes.md:56-61("Style / reading variants")give the same two axes and the same value sets, and
CONTEXT.md:34-40is a third statement.Also, while touching these files
README.md:3says/general"is currently not linked from the home page", which implies somethingelse links it. Nothing does —
docs/routes.md:12says "not linked from any page (orphaned)" and thebuild confirms zero inbound links. Match the README to that wording.
Acceptance
Each of the three facts above has exactly one owner file; every other mention is a link. The
README.md:3wording matchesdocs/routes.md:12.Relation to #2
The docs-drift CI check in #2 compares route counts against
getStaticPaths. It would not catchany of the above, since every copy is currently correct — these drift only after someone edits one
copy. Worth doing before that check gives a false sense of coverage.