Skip to content

docs: fix broken README anchor in standards-and-conformance guide - #149

Open
OmarAlJarrah wants to merge 1 commit into
docs/astro-sitefrom
e6-readme-anchor
Open

docs: fix broken README anchor in standards-and-conformance guide#149
OmarAlJarrah wants to merge 1 commit into
docs/astro-sitefrom
e6-readme-anchor

Conversation

@OmarAlJarrah

Copy link
Copy Markdown
Member

Summary

  • The standards-and-conformance guide linked to https://github.com/dexpace/kuri#standards for readers who want the exact current conformance counts.
  • The README's actual heading for that content is "Standards and conformance", which GitHub slugifies to #standards-and-conformance (confirmed against the README's own table of contents, which links to that exact anchor). GitHub doesn't do prefix matching on fragment identifiers, so the old link landed at the top of the README instead of the intended section.
  • Fixed the link to point at #standards-and-conformance.

This targets the docs/astro-site branch (PR #81) rather than main because the guide file and the restructured README section this links to only exist on that branch so far.

Test plan

  • Doc-only change (site .mdx link text) — no Gradle build required per repo policy.
  • Confirmed the README's own table of contents on docs/astro-site links to #standards-and-conformance for the "## Standards and conformance" heading.
  • Searched the repo for other occurrences of the stale dexpace/kuri#standards anchor; none remain.

Closes #102

The guide linked to https://github.com/dexpace/kuri#standards for readers
who want the exact current conformance counts, but the README's actual
heading is "Standards and conformance", which GitHub slugifies to
#standards-and-conformance. GitHub doesn't do prefix matching on fragment
identifiers, so the old link landed at the top of the README instead of
the intended section.

Closes #102
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant