mirror of
https://github.com/harvard-edge/cs249r_book.git
synced 2026-07-24 08:47:40 -05:00
Vijay Janapa ReddiandClaude Opus 4.7
6fdf81dd49
Two breakage points with the same flavor — the navbar configuration disagreed with the responsive CSS, and the deploy script discarded the asset bundle the about/community/newsletter pages depend on. - navbar-common.yml: collapse-below "lg" → "xl". With 6 left dropdowns and 4 right tools, the full navbar needs ~1100 px. At 992–1199 px the dropdowns wrapped into a vertical stack and "Machine Learning Systems" broke across three lines. _mobile.scss was already written against an "xl" assumption (its 769–1199 px block targets a collapsed navbar that never appeared); the YAML now matches. - _mobile.scss: bump the abbreviated-title media query from 991 px to 1199 px so "ML Systems" appears the moment the navbar collapses, not 200 px later. - site-publish-live.yml: stop skipping site_libs/ when copying the landing build to root. The about/community/newsletter HTML reference ../site_libs/… which resolves to /site_libs/ at runtime; skipping it shipped those subsites with no Bootstrap or Quarto CSS at all (raw <ul> navbar, 3000 px of empty whitespace before the hero, dark mode unstyled). Also rm -rf each non-subsite item before re-copying so a removed top-level file doesn't linger on gh-pages. Verified locally with Playwright at 425/768/991/992/1100/1199/1280/ 1400/1920 px in light + dark mode against a fresh tinytorch render. Not addressed here: the right-TOC's position:sticky lets go on big-picture.html because Quarto closes <main> mid-article (a few content-visible blocks end up after </main>). That's a per-page content-structure fix, not a shared-chrome change — separate commit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>