Skip to content

DX-2362: Fix 163 broken internal anchor fragment links - #1866

Closed
sharadregoti wants to merge 2 commits into
mainfrom
DX-2362-fix-broken-anchor-links
Closed

DX-2362: Fix 163 broken internal anchor fragment links#1866
sharadregoti wants to merge 2 commits into
mainfrom
DX-2362-fix-broken-anchor-links

Conversation

@sharadregoti

@sharadregoti sharadregoti commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

Jira Ticket

DX-2362

Summary

Root Causes Fixed

Release note anchors (old format → new format with dots-as-hyphens)
Old slugify removed dots from version numbers (5.3.0#530-release-notes); correct format is #5-3-0-release-notes. Fixed across gateway, dashboard, helm-chart, operator, portal, and archived release note pages.

Restructured pages
api-management/logs-metrics.mdx, portal/install.mdx, and tyk-self-managed/install.mdx were reorganised; stale anchors removed or updated to current headings.

Moved content
JWT signature validation content moved to a dedicated page (jwt-signature-validation.mdx); updated links that still pointed to json-web-tokens.mdx.

Wrong anchor names
Fixed typos and outdated anchors in implement-tls, certificates, mdcb, graphql, dynamic-client-registration, dashboard-configuration, and others.

Mintlify slug nuance — double hyphens from :
Headings containing ": " generate double hyphens in anchors (e.g. Step 1: Create#step-1--create). Updated portal step links and other colon-containing headings that were using single hyphens.

Validator script fix
Updated heading_re regex to also match headings that appear inside ordered list items (the pattern N. ##### Heading used extensively in troubleshooting-debugging.mdx). This eliminates false positives for that file.

Result

  • Before: 163 broken anchor fragments in 60 files
  • After: 0 broken anchor fragments

Test Plan

  • CI anchor check passes (0 broken anchors)
  • CI full validation passes (links, images, redirects)
  • Spot-check a few updated links on the staging/preview site

🤖 Generated with Claude Code

Fixes all broken anchor fragments identified by the CI anchor checker
introduced in DX-2361 (#1865).

Root causes fixed:
- Release note anchors: old slugify removed dots from version numbers
  (e.g. 5.3.0 → #530-release-notes); updated to dot-to-hyphen format
  (#5-3-0-release-notes) across gateway, dashboard, helm-chart, operator,
  portal, and archived release note pages
- Restructured pages: logs-metrics, portal/install, and tyk-self-managed/install
  were reorganised; removed or updated stale anchors to current headings
- Moved content: JWT signature validation content moved to dedicated page;
  updated links from json-web-tokens to jwt-signature-validation
- Wrong anchor names: fixed typos and outdated anchors in implement-tls,
  certificates, mdcb, graphql, dynamic-client-registration, dashboard-config
- Mintlify slug nuance: headings with ": " generate double hyphens (--);
  fixed portal step links and other colon-containing headings
- Validator: updated heading regex to detect headings inside ordered list
  items (pattern used in troubleshooting-debugging.mdx)

Result: 0 broken anchor fragments (was 163 across 60 files)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Failed to generate code suggestions for PR

… hyphen

Corrects a wrong assumption in the previous commit: Mintlify omits ':'
from headings entirely (like '()[]/?!'), so 'Step 1: Create' generates
'step-1-create' not 'step-1--create'.

Changes:
- slugify_heading: add ':' to the removal regex alongside '()[]/?!'
- Revert portal step anchors from '--' back to single '-'
- Revert rate-limit scope anchor (': API-level' → '-api-level' not '--api-level')
- Fix custom-developer-portal anchor (only one '--' from '.', not from ':')
- Fix mutual-tls anchor: 'mTLS): Two-Way' → 'mtls-two-way' (single hyphen)
- Fix portal/install docker anchor: 'Installation: Docker' → 'installation-docker'

Result: 0 broken anchor fragments

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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