feat(web): mobile-friendly + responsive sqlritedb.com (SQLR-37)#119
Merged
Conversation
Mobile-first pass over the marketing site so SEO + Core Web Vitals
ranking signals don't leak before the rest of the SEO ticket sequence
lands. Renders cleanly with no horizontal scroll at 375 / 390 / 768 /
1024px+ breakpoints; tap targets on primary controls are >= 44px.
- nav.tsx: client-side hamburger + full-width drawer below 760px;
body-scroll lock and Esc-to-close while open.
- docs/page.tsx: sticky <details> "On this page" panel surfaces the
full TOC on phones (desktop sidebar + right TOC unchanged).
- layout.tsx: viewport export with device-width / dark themeColor so
iOS Safari + Chrome mobile chrome stop flashing white.
- globals.css: 900 / 640 / 380px responsive layer — wrap padding,
hero / CTA / sec-head spacing, terminal / install-bar / SDK / bench /
footer / desktop showcase tuning, architecture row stacking, SQL
table -> stacked cards under 640px, SDK tab bar -> horizontal scroll,
hamburger + mobile-menu + docs-mobile-menu styles. Global guard
switched to html { overflow-x: clip } to preserve position: sticky.
- README.md: documents the responsive layers + section-local
breakpoint convention for new sections.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mobile-first responsive pass on the marketing + docs site at
web/. Lands before the rest of the SEO ticket sequence so Google's mobile-first indexing and mobile Core Web Vitals don't penalize the upstream work.<details>"On this page" drawer surfacing the full TOC on phones (desktop sidebar + on-page TOC unchanged).width=device-width+ darkthemeColor: #0b0c0eso iOS Safari / Chrome mobile chrome don't flash white.globals.cssgets a 900 / 640 / 380px responsive layer: wrap padding, hero / CTA / sec-head spacing, architecture row stacking, SQL surface table reflowing to stacked cards under 640px, SDK tab bar going horizontal-scroll, bench bars / debt cards collapsing, footer single-column, terminal / install-bar / desktop-showcase tuned for narrow viewports.html { overflow-x: clip }(nothidden) soposition: stickykeeps working for the nav and docs sidebar..btn, hamburger, install-bar copy, mobile menu links, docs section toggle.web/README.mddocuments the responsive layers and the convention for adding new sections.Acceptance criteria
npm run typecheck,npm run lint,npm run buildall pass locally.Test plan
npm run dev; sweep Chrome DevTools device mode at 375 / 390 / 768 / 1024 px on/and/docs.<details>drawer scrolls internally and links jump correctly.Closes SQLR-37.