Repository navigation
One docs, not two: the site is served at /docs/, so the section cannot be too - #13
Merged
Merged
Conversation
…t be too
Every page came out at /docs/docs/… — the content sat in a `docs` section and
the site is published at /docs/, so the segment appeared twice:
before /docs/docs/working-with-a-file/reading/
after /docs/working-with-a-file/reading/
⚠ The links were NOT broken, and I nearly said they were. Hugo prefixes the
base path onto an absolute link in Markdown, so `](/docs/api/)` was emitted as
`href="/docs/docs/api/"` — self-consistent with the doubled shape. A probe of
/docs/working-with-a-file/reading/ returned 404 and I read that as "the links
are broken"; it only meant that was never a URL the site used.
What settled it was a link checker over the built tree: 848 internal links in
the shipped build, 0 broken. The tool is `linkcheck`, and it stopped a wrong
claim rather than finding a defect — which is the useful half of a control
reproducing a known positive and refusing to.
So this is a URL-shape change, not a repair. The content moves up one level;
Hextra takes its documentation layout from a section called `docs`, so with the
content at the root the type is cascaded instead. The separate hero home goes:
this site IS the documentation, and the organisation's landing page is a
different repository.
796 internal links, 0 broken, 15 pages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every page came out at
/docs/docs/…. The content sat in adocssection andthe site is published at
/docs/, so the segment appeared twice:⚠ The links were not broken, and I nearly said they were
Hugo prefixes the base path onto an absolute link written in Markdown, so
](/docs/api/)was emitted ashref="/docs/docs/api/"— self-consistentwith the doubled shape. A probe of
/docs/working-with-a-file/reading/returned 404 and I read that as "all nineteen internal links are broken". It
only meant that was never a URL the site used.
What settled it was a link checker over the built tree: 848 internal links in
the shipped build, 0 broken. So this is a URL-shape change, not a repair.
That tool stopped a wrong claim rather than finding a defect — which is the
other half of why a control has to be run against a known positive, and has to
be believed when it refuses to reproduce one.
The change
The content moves up one level. Hextra takes its documentation layout from a
section called
docs, so with the content at the root the type is cascadedinstead. The separate hero home goes: this site is the documentation, and the
organisation's landing page is a different repository.
796 internal links, 0 broken, 15 pages.
🤖 Generated with Claude Code