Repository navigation
docs: give every site page the same menu and land jumps below the header - #136
Conversation
The header menu differed per page (the Setup Guide page showed only four items), so every page with the site header now shares one menu and footer, with "Setup Guide" capitalised. Menu jumps stopped under the sticky header — on phones the home-page section labels were hidden, and the Support headings fully. A scroll offset now clears it. Five home-page screenshots also declared the wrong image size, so the page shrank ~200px as they loaded and cross-page jumps (e.g. FAQ) overshot; their dimensions now match the files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1e21a65689
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <a href="index.html#privacy">Privacy</a> | ||
| <a href="index.html#faq">FAQ</a> |
There was a problem hiding this comment.
Make the expanded mobile menu scrollable
On short mobile viewports, such as a phone in landscape at the max-width: 940px breakpoint, expanding this menu to nine rows makes the dropdown roughly 475px tall below the 66px sticky header. Since .nav.open .nav-links has neither a viewport-relative maximum height nor vertical scrolling, the final entries remain below the viewport even while the page scrolls. This also affects the newly expanded menus in try.html and support.html; constrain the dropdown to the available viewport height and enable vertical overflow.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 17f58f7. The open menu is now capped at the height below the header (100dvh - 66px, with a 100vh fallback) and scrolls with overflow-y: auto. overscroll-behavior: contain stops the scroll from carrying over to the page. Checked in headless Chromium: at 844×390 the menu is 323px tall with 459px of content, and the last item (Support) scrolls into view. At 390×844 the menu shows in full, as before.
With nine items, the open menu is ~460px tall, so on a phone in landscape its last entries sat below the viewport with no way to reach them. Cap it at the space under the header and scroll it instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Why
What changed
index.html#…. The current page is marked witharia-current.site.cssgives link targets a scroll margin so jumps stop below the 66px sticky header. Home-page sections already have top padding, so they only need a 24px margin at phone width. Unpadded targets, such as the Support cards, get the full 86px.width/heightof fiveindex.htmlscreenshots (07, 08 and 10–12) now match the real files. Before, the page shrank by about 200px as those images loaded. That made cross-page jumps such as Setup Guide → FAQ overshoot their section.← Homebutton is hidden below 1080px wide, so the longer menu doesn't overflow between 940 and 1060px. The logo still links home.Verification
🤖 Generated with Claude Code