Fix #id targets landing under the sticky header

[claudiacodacy]

Problem

Opening a page with a #id in the URL often leaves the target hidden under the navbar (reported by Ioan in Slack). Example: /codacy-ai/codacy-ai/#ai-features put the heading at 93px while the header is 109px tall.

Cause

• scroll-margin-top on headings was 5rem (80px), but the desktop header is ~109px because the tabs row is part of it.
• The rule only covered h1–h6, so other #id targets got no offset.

Change

• theme/stylesheets/content.css: apply scroll-margin-top to .md-typeset [id]: 5rem below 76.25em (header ~61px), 8rem from 76.25em (header ~109px). Both leave ~19px of clearance.
• theme/stylesheets/base.css: update the comment that referred to headings only.
• Still no page-wide scroll-padding-top on <html>, per the existing comment (it caused a scroll jump when opening search).

Verified

Injected the same CSS into docs.codacy.com at 1280px and 600px wide on /codacy-ai/codacy-ai/#ai-features: 19px clearance at both widths.

Not verified

• mkdocs build --strict (submodules not initialised in my worktree)
• Light vs. dark scheme separately (no colour changes)
• A non-heading #id target
• Navigation between pages

🤖 Generated with Claude Code

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

No merge-blocking security or logic issues were identified. Codacy reports the PR is up to standards. The requested behavior should still be covered by automated tests, particularly for responsive heading and non-heading anchors and focus/search behavior.

About this PR

• No automated tests are included for the responsive anchor offsets, non-heading targets, or focus/search behavior. Add coverage for these scenarios before relying on the change.

Test suggestions

• Verify heading anchor targets remain visible below the sticky header below 76.25em.
• Verify heading anchor targets remain visible below the sticky header at or above 76.25em.
• Verify non-heading elements with IDs receive the same responsive offset.
• Verify search or focus behavior is not adversely affected by page-wide scroll padding.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify heading anchor targets remain visible below the sticky header below 76.25em.
2. Verify heading anchor targets remain visible below the sticky header at or above 76.25em.
3. Verify non-heading elements with IDs receive the same responsive offset.
4. Verify search or focus behavior is not adversely affected by page-wide scroll padding.

Low confidence findings

• The PR does not report a successful strict build; verify the build in an environment with initialized submodules before merging.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}