Skip to content

docs(merge-queue): restructure metrics page heading hierarchy#68

Open
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/on-this-page-hierarchy
Open

docs(merge-queue): restructure metrics page heading hierarchy#68
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/on-this-page-hierarchy

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Summary

  • Slack feedback flagged /merge-queue/administration/metrics as "too flat" — the right-rail TOC rendered every section at the same depth.
  • Root cause: the whole page started at ### with zero ## anchors. Mintlify nests ### under their parent ##; with no parents, the TOC was a flat list.
  • Mintlify has no TOC depth setting (verified against their settings schema), so the fix is content-side: cap headings at ### and use bold paragraph leads for sub-section emphasis within an ###.
  • This is a canary page — if the structure feels right in review, follow-up PRs will sweep the rest of merge-queue/ with the same rule.

What changed

  • Top-level sections promoted ### → ## (7 sections).
  • Real subsections promoted #### → ### (13 subsections).
  • Sub-section emphasis was previously a mix of #### and bold-as-headers — both replaced with bold paragraph leads in three patterns:
    • **Sub-topic.** Body continues... under Understanding the Data and Requirements.
    • **Label:** lead-ins for tables (Query parameters) and code blocks (Queue health alerts, Failure analysis, Duration analysis, Sample output).
    • **1. Step**, **2. ...** for the Datadog Agent procedure.

Heading shape

Before After
h2 0 7
h3 7 13
h4 13 0
h5 2 0
bold-as-pseudo-header 12 0

Anchor slugs unchanged — internal links (parallel-queues, reference/merge) and changelog inbound links (#filter-metrics-by-impacted-targets, #prometheus-metrics-endpoint, #drill-down-into-metrics) all still resolve.

Test plan

  • Pull and run `mint dev`; confirm right-rail "On this page" TOC shows 7 top-level entries with h3 children nested under them, no h4s.
  • Click each inbound anchor link (parallel-queues page, reference/merge page, and the 3 referenced changelog entries) and confirm they scroll to the correct heading.
  • Visual scan: bold paragraph leads read as topic sentences, not orphan labels.

🤖 Generated with Claude Code

The metrics page was flagged in Slack as "too flat" — every section
rendered at the same depth in the right-rail TOC because the whole
page started at ### with no ## anchors. Mintlify exposes no TOC
depth setting, so the fix lives in the source.

Three conversion patterns:
- ### → ## for top-level sections (7)
- #### → ### for real subsections (13)
- #### → **Sub-topic.** paragraph leads for sub-section emphasis
  within an h3 (Understanding the Data, Requirements, Datadog steps,
  example-query labels, table/code block lead-ins)

Heading shape: was 7×h3 + 13×h4 + 2×h5; now 7×h2 + 13×h3 + 0×h4+.
No anchor slugs changed — inbound links remain valid.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 22, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview May 22, 2026, 11:08 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant