Skip to content

feat: restyle the site as the S2 terminal on the Whatsaaaa design system - #2

Merged
whatsaaaa merged 5 commits into
mainfrom
fm/landing-ds-restyle
Nov 13, 2026
Merged

whatsaaaa merged 5 commits into
mainfrom
fm/landing-ds-restyle

Conversation

@whatsaaaa

@whatsaaaa whatsaaaa commented Nov 13, 2026 •

Copy link
Copy Markdown
Owner

Intent

Apply the Whatsaaaa design system to this personal website, following the "S2 Terminal" direction picked while the design system was planned: the site as a terminal session, with a tab bar, a two-pane home page (whoami with the ghost, handle, tagline, bio and stack; ls ~/projects), and a status line with real key shortcuts, the keys on/off switch and the theme name.

Decisions made for it:

  • Use the mockup's text: the GitHub profile bio, the tagline "Building things end to end.", the stack list and the line about the handle.
  • List form-builder, design-system and dotfiles as active and building-blocks as experimental; the private sample apps repository stays off the site.
  • Keep the ideas section, with real ideas: component libraries for React and Vue built on the design system.
  • No extra touches beyond the ghost easter egg and the shortcuts for now.
  • After a preview: make the theme name in the status line a theme switch at every width, so phone visitors can switch themes, as the Vue sample app does.

What Changed

  • Rebuilds every page (home, projects, ideas, detail pages and 404) on @whatsaaaa/design-system as a terminal session. Each page has a tab bar with the ghost and its easter egg, the section tabs and a github ↗ link. The home page has two panes: whoami (handle with a block cursor, tagline, bio, stack) and ls ~/projects. The status line has the p/i/g/t shortcuts and a keys on/off switch. The old ProjectCard/StatusBadge components and most of the hand-rolled CSS are replaced by new TabBar, StatusLine, Listing, Entry, State, Ghost, PromptLink and Document components.
  • The theme name in the status line is now a button that switches the theme at every width, so it also works on phones. A remembered theme and keys setting is applied before the first paint, the browser theme-color follows the active theme, and the 404 page shows the missing path and is marked noindex.
  • Swaps the placeholder content for real entries: projects form-builder, design-system and dotfiles (active) and building-blocks (experimental), plus two ideas for React and Vue component libraries. Also adds a favicon set, an apple-touch icon and a 1280x640 social card (og:image, summary_large_image), and loosens the Node engine range to ^22.23.4 || >=24.12.0.

🤖 Generated with Claude Code

Risk Assessment

✅ Low: A well-bounded restyle of a static Astro site onto the published design system; both fix rounds (theme-color sync, focus hand-off, 320px reflow, status-path container query) were traced against the current code and the built output and hold, and no new defects, intent contradictions, or privacy/security paths were found.

Testing

I built the site for production and served it with astro preview, then drove it end to end in headless Chrome for Testing. All of it passed: - Every page renders in the S2 terminal frame with the agreed content. - The keyboard shortcuts and the remembered keys switch work. - On a 390px touch phone, tapping the theme name switches the theme. The choice is remembered and the browser-bar color follows it. - Keyboard focus stays on the visible theme name after t, Enter or Space. - A 328-combination sweep from 320 to 400px (both themes, keys on and off) found no clipped functional item, no overflow inside the frame's overflow-hidden parts, and no partial glyph in the path. The screenshots and status-line strips show the same. - No console errors. I removed dist/ and stopped the preview server and the browser.

  • Live validation: ✅ go - 10 of 10 scenarios driven live against the product
Scenario Result Live Evidence
Visitor opens the home page on desktop and sees the S2 terminal: tab bar (ghost + whatsaaaa, 1 home/2 projects/3 ideas, github ↗), whoami pane (ghost, handle with block cursor, tagline, bio, handle li… ✅ pass live 01-home-desktop-dark.png, 07b-home-desktop-light.png
Projects list shows design-system, form-builder, dotfiles as active and building-blocks as experimental with the agreed description, and no sample-apps repo ✅ pass live 01-home-desktop-dark.png, 12-projects-list-desktop-dark.png (total 4)
Ideas tab lists two real ideas (React and Vue component libraries) and an idea page opens ✅ pass live 14-ideas-list-desktop-dark.png, 15-idea-vue-desktop-dark.png
Project detail page and 404 render in the terminal frame with correct current tab, status path, and 404 status/noindex ✅ pass live 13-project-design-system-desktop-dark.png, 16-404-desktop-dark.png, curl 404 status
Keyboard user presses p, i, g, 1-3 to navigate and t to switch the theme; the theme is remembered on the next page; / opens no command search ✅ pass live 02-theme-shortcut-transcript.txt, 03-shortcuts-and-keys-switch-transcript.txt
Visitor turns the keys switch off: hints and tab numbers hide, keys do nothing, the choice survives a reload, and turning it on restores the keys ✅ pass live 03-shortcuts-and-keys-switch-transcript.txt, 10-home-320-light-keys-off.png
Phone visitor (390px touch) taps the theme name in the status line: the theme switches, is remembered across pages, and the browser-bar theme-color follows the chosen theme (system dark and system lig… ✅ pass live 04-phone-390-dark-before-tap.png, 05-phone-390-after-tap-light.png, 05-phone-tap-theme-name-transcript.txt
Keyboard user focuses the theme name and presses t, Enter or Space (keys on and off): focus moves to the newly shown theme name instead of falling to body ✅ pass live 06-theme-focus-handoff-transcript.txt, 07-desktop-statusline-focus-after-t-light.png
Adversarial reflow at 320-400px in 2px steps, both themes, keys on/off: no functional status-line item clipped, no overflow in the window/tab bar/status line/panes, path either readable with full padd… ✅ pass live 08-reflow-sweep-320-400-transcript.txt (328 combinations, 0 issues), 09-statusline-sweep-.png, 10-home-320-.png
Visitor presses the ghost three times and it shouts the handle in a speech bubble ✅ pass live 11-ghost-easter-egg-shout.png, 11-ghost-easter-egg-transcript.txt

Home, desktop 1440px, dark (rose-pine)

Home, desktop, light after pressing t (focus ring on rose-pine-dawn)

Status line close-up: focus moved to rose-pine-dawn after t

Phone 390px, dark, before tapping the theme name (full page)

Phone 390px after tapping the theme name: Dawn theme

Evidence: Phone tap transcript (theme, storage, theme-color, both system schemes)
## Phone 390x844 (mobile, touch), system dark, tap the theme name in the status line
    uid=g5:5_0 button "Switch theme, now rose-pine-dawn" focusable focused
result: "{\"theme\":\"light\",\"stored\":\"light\",\"bg\":\"rgb(250, 244, 237)\",\"visibleName\":[\"Switch theme, now rose-pine-dawn\"],\"metas\":[\"#faf4ed\",\"#faf4ed\"]}"
help[1]:
  Run `chrome-devtools-axi snapshot` to see current page state
## Phone 390, system LIGHT: tap theme name, reload, theme-color
initial: {"theme":"(system)","activeThemeColor":["#faf4ed"],"bg":"rgb(250, 244, 237)","name":["rose-pine-dawn"]}
after tap: {"theme":"dark","activeThemeColor":["#191724"],"bg":"rgb(25, 23, 36)","name":["rose-pine"]}
next page load: {"theme":"dark","activeThemeColor":["#191724"],"bg":"rgb(25, 23, 36)","name":["rose-pine"]}
tap again: {"theme":"light","activeThemeColor":["#faf4ed"],"bg":"rgb(250, 244, 237)","name":["rose-pine-dawn"]}
Evidence: t shortcut and theme persistence transcript
initial (system dark): {"theme":"(system)","stored":{},"metaContents":["#191724","#faf4ed"],"bg":"rgb(25, 23, 36)","visibleThemeName":["rose-pine"]}
after t: {"theme":"light","stored":{"ws-theme":"light"},"metaContents":["#faf4ed","#faf4ed"],"bg":"rgb(250, 244, 237)","visibleThemeName":["rose-pine-dawn"]}
after navigating to /projects/ (remembered): {"theme":"light","stored":{"ws-theme":"light"},"metaContents":["#faf4ed","#faf4ed"],"bg":"rgb(250, 244, 237)","visibleThemeName":["rose-pine-dawn"]}
after t again: {"theme":"dark","stored":{"ws-theme":"dark"},"metaContents":["#191724","#191724"],"bg":"rgb(25, 23, 36)","visibleThemeName":["rose-pine"]}
Evidence: Navigation shortcuts and keys switch transcript
home + p -> /projects/
projects + i -> /ideas/
ideas + 1 -> /
home + 2 -> /projects/
projects + 3 -> /ideas/
ideas + g clicks -> https://github.com/whatsaaaa
/ on home -> path / dom changed: false dialogs: 0
keys on: {"ariaChecked":"true","label":"keys on","htmlKeys":"on","stored":null,"hintsVisible":4,"tabNumbers":"counter(ws-tab) / \"\"","keyshortcuts":4}
after clicking switch: {"ariaChecked":"false","label":"keys off","htmlKeys":"off","stored":"off","hintsVisible":0,"tabNumbers":"none","keyshortcuts":0}
keys off + p -> path /
keys off + t -> theme (system)
reload on /ideas/ (remembered): {"ariaChecked":"false","label":"keys off","htmlKeys":"off","stored":"off","hintsVisible":0,"tabNumbers":"none","keyshortcuts":0}
keys off + 1 -> path /ideas/
switch back on: {"ariaChecked":"true","label":"keys on","htmlKeys":"on","stored":null,"hintsVisible":4,"tabNumbers":"counter(ws-tab) / \"\"","keyshortcuts":4}
keys on + 1 -> path /
Evidence: Theme focus hand-off transcript (t, Enter, Space, keys off)
after 19 Tabs: {"focused":"Switch theme, now rose-pine","focusVisible":true,"theme":"(system)"}
press t while theme name focused (keys on): {"focused":"Switch theme, now rose-pine-dawn","focusVisible":true,"theme":"light"}
press t again: {"focused":"Switch theme, now rose-pine","focusVisible":true,"theme":"dark"}
press Enter on theme name: {"focused":"Switch theme, now rose-pine-dawn","focusVisible":true,"theme":"light"}
press Space on theme name: {"focused":"Switch theme, now rose-pine","focusVisible":true,"theme":"dark"}
keys switched off, Tab -> {"focused":"BODY","focusVisible":false,"theme":"dark"}
keys off, press t on theme name -> {"focused":"BODY","focusVisible":false,"theme":"dark"}
keys off, press Enter on theme name -> {"focused":"BODY","focusVisible":false,"theme":"dark"}
--- keys remembered off
after 19 Tabs: {"focused":"Switch theme, now rose-pine","focusVisible":true,"theme":"(system)","keys":"off"}
keys off, press t on theme name (expect no change): {"focused":"Switch theme, now rose-pine","focusVisible":true,"theme":"(system)","keys":"off"}
keys off, press Enter on theme name: {"focused":"Switch theme, now rose-pine-dawn","focusVisible":true,"theme":"light","keys":"off"}
keys off, press Enter again: {"focused":"Switch theme, now rose-pine","focusVisible":true,"theme":"dark","keys":"off"}
Evidence: 320-400px reflow sweep, 328 combinations, 0 issues
/ theme=dark keys=on (applied: dark/on) 41/41 ok
  path: 320:ellip 322:ellip 324:ellip 326:ellip 328:ellip 330:ellip 332:ellip 334:full 336:full 338:full 340:full 342:full 344:full 346:full 348:full 350:full 352:full 354:full 356:full 358:full 360:full 362:full 364:full 366:full 368:full 370:full 372:full 374:full 376:full 378:full 380:full 382:full 384:full 386:full 388:full 390:full 392:full 394:full 396:full 398:full 400:full
  320: ellipsized 51.9px (min 14.4) | h1 32px   400: full "whatsaaaa" | h1 40px
/ theme=dark keys=off (applied: dark/off) 41/41 ok
  path: 320:ellip 322:ellip 324:ellip 326:ellip 328:ellip 330:ellip 332:ellip 334:ellip 336:ellip 338:ellip 340:full 342:full 344:full 346:full 348:full 350:full 352:full 354:full 356:full 358:full 360:full 362:full 364:full 366:full 368:full 370:full 372:full 374:full 376:full 378:full 380:full 382:full 384:full 386:full 388:full 390:full 392:full 394:full 396:full 398:full 400:full
  320: ellipsized 44.7px (min 14.4) | h1 32px   400: full "whatsaaaa" | h1 40px
/ theme=light keys=on (applied: light/on) 41/41 ok
  path: 320:absent 322:absent 324:absent 326:absent 328:ellip 330:ellip 332:ellip 334:ellip 336:ellip 338:ellip 340:ellip 342:ellip 344:ellip 346:ellip 348:ellip 350:ellip 352:ellip 354:ellip 356:ellip 358:ellip 360:ellip 362:ellip 364:ellip 366:ellip 368:ellip 370:full 372:full 374:full 376:full 378:full 380:full 382:full 384:full 386:full 388:full 390:full 392:full 394:full 396:full 398:full 400:full
  320: absent | h1 32px   400: full "whatsaaaa" | h1 40px
/ theme=light keys=off (applied: light/off) 41/41 ok
  path: 320:absent 322:absent 324:absent 326:absent 328:absent 330:absent 332:absent 334:ellip 336:ellip 338:ellip 340:ellip 342:ellip 344:ellip 346:ellip 348:ellip 350:ellip 352:ellip 354:ellip 356:ellip 358:ellip 360:ellip 362:ellip 364:ellip 366:ellip 368:ellip 370:ellip 372:ellip 374:ellip 376:full 378:full 380:full 382:full 384:full 386:full 388:full 390:full 392:full 394:full 396:full 398:full 400:full
  320: absent | h1 32px   400: full "whatsaaaa" | h1 40px
/ideas/react-component-library/ theme=dark keys=on (applied: dark/on) 41/41 ok
  path: 320:ellip 322:ellip 324:ellip 326:ellip 328:ellip 330:ellip 332:ellip 334:ellip 336:ellip 338:ellip 340:ellip 342:ellip 344:ellip 346:ellip 348:ellip 350:ellip 352:ellip 354:ellip 356:ellip 358:ellip 360:ellip 362:ellip 364:ellip 366:ellip 368:ellip 370:ellip 372:ellip 374:ellip 376:ellip 378:ellip 380:ellip 382:ellip 384:ellip 386:ellip 388:ellip 390:ellip 392:ellip 394:ellip 396:ellip 398:ellip 400:ellip
  320: ellipsized 51.9px (min 14.4) |    400: ellipsized 131.9px (min 14.4) | 
/ideas/react-component-library/ theme=dark keys=off (applied: dark/off) 41/41 ok
  path: 320:ellip 322:ellip 324:ellip 326:ellip 328:ellip 330:ellip 332:ellip 334:ellip 336:ellip 338:ellip 340:ellip 342:ellip 344:ellip 346:ellip 348:ellip 350:ellip 352:ellip 354:ellip 356:ellip 358:ellip 360:ellip 362:ellip 364:ellip 366:ellip 368:ellip 370:ellip 372:ellip 374:ellip 376:ellip 378:ellip 380:ellip 382:ellip 384:ellip 386:ellip 388:ellip 390:ellip 392:ellip 394:ellip 396:ellip 398:ellip 400:ellip
  320: ellipsized 44.7px (min 14.4) |    400: ellipsized 124.7px (min 14.4) | 
/ideas/react-component-library/ theme=light keys=on (applied: light/on) 41/41 ok
  path: 320:absent 322:absent 324:absent 326:absent 328:ellip 330:ellip 332:ellip 334:ellip 336:ellip 338:ellip 340:ellip 342:ellip 344:ellip 346:ellip 348:ellip 350:ellip 352:ellip 354:ellip 356:ellip 358:ellip 360:ellip 362:ellip 364:ellip 366:ellip 368:ellip 370:ellip 372:ellip 374:ellip 376:ellip 378:ellip 380:ellip 382:ellip 384:ellip 386:ellip 388:ellip 390:ellip 392:ellip 394:ellip 396:ellip 398:ellip 400:ellip
  320: absent |    400: ellipsized 95.9px (min 14.4) | 
/ideas/react-component-library/ theme=light keys=off (applied: light/off) 41/41 ok
  path: 320:absent 322:absent 324:absent 326:absent 328:absent 330:absent 332:absent 334:ellip 336:ellip 338:ellip 340:ellip 342:ellip 344:ellip 346:ellip 348:ellip 350:ellip 352:ellip 354:ellip 356:ellip 358:ellip 360:ellip 362:ellip 364:ellip 366:ellip 368:ellip 370:ellip 372:ellip 374:ellip 376:ellip 378:ellip 380:ellip 382:ellip 384:ellip 386:ellip 388:ellip 390:ellip 392:ellip 394:ellip 396:ellip 398:ellip 400:ellip
  320: absent |    400: ellipsized 88.7px (min 14.4) | 
TOTAL 328 widths checked, 0 with issues

Status line at 320-400px, light, keys off (path absent or readable)

Status line at 320-400px, light, keys on

Status line at 320-400px, dark, keys on

Status line at 320-400px, dark, keys off

Home at 320px, light, keys off (whoami fits, path collapsed)

Home at 320px, dark, keys on

Ghost easter egg shout bubble

Projects list, desktop dark

design-system project page, desktop dark

Ideas list with two real ideas, desktop dark

Vue component library idea page, desktop dark

404 page, desktop dark

Pipeline

Updates from git push no-mistakes

✅ **Intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 2 issues found → auto-fixed (2) ✅
  • ⚠️ src/layouts/Base.astro:57 - The browser-bar color ignores the theme the visitor picks. The two theme-color meta tags are chosen only by prefers-color-scheme, but this change adds a theme switch (the t key, and now the theme-name buttons at every width) that sets data-theme on <html> and remembers the choice. Example: an Android phone with a dark system theme opens the site, taps rose-pine in the status line, and the page turns Dawn (#faf4ed) while Chrome's address bar stays #191724. The mismatch then returns on every later page load, because themeInitScript reapplies data-theme=light but nothing updates theme-color. Phone visitors are exactly who the last intent decision ("so phone visitors can switch themes") is for. The defect is mechanical, but the fix needs a decision on where it lives, which is why this is ask-user. Option 1 is in @whatsaaaa/design-system (setTheme/themeInitScript), the shared boundary every consumer uses, including the Vue sample app. Option 2 is a local fix in this site: a head script after the meta tags plus the click handler at Base.astro:107-119, both setting the meta content from getTheme().
  • ℹ️ src/layouts/Base.astro:109 - The focus hand-off only runs when the clicked control was itself the focused one, so it misses the t key path. Sequence: on a wide screen with keys on, a keyboard user Tabs to the rose-pine theme-name button and presses t. enableShortcuts clicks the hint button [data-ws-key=t], so focused is false (activeElement is the theme-name button, not control). The theme switches, the focused rose-pine button gets display:none, and focus falls to <body> instead of moving to rose-pine-dawn. This breaks the invariant the comment at lines 111-112 promises. Fix: capture const active = document.activeElement before toggleTheme(), then move focus when active matches [data-theme-name] and has no client rects. That covers both the click path and the shortcut path.

🔧 Fix applied.
3 issues (2 warnings, 1 info) still open:

  • ⚠️ src/layouts/Base.astro:57 - The browser-bar color ignores the theme the visitor picks. The two theme-color meta tags are chosen only by prefers-color-scheme, but this change adds a theme switch (the t key, and now the theme-name buttons at every width) that sets data-theme on <html> and remembers the choice. Example: an Android phone with a dark system theme opens the site, taps rose-pine in the status line, and the page turns Dawn (#faf4ed) while Chrome's address bar stays #191724. The mismatch then returns on every later page load, because themeInitScript reapplies data-theme=light but nothing updates theme-color. Phone visitors are exactly who the last intent decision ("so phone visitors can switch themes") is for. The defect is mechanical, but the fix needs a decision on where it lives, which is why this is ask-user. Option 1 is in @whatsaaaa/design-system (setTheme/themeInitScript), the shared boundary every consumer uses, including the Vue sample app. Option 2 is a local fix in this site: a head script after the meta tags plus the click handler at Base.astro:107-119, both setting the meta content from getTheme().
  • ℹ️ src/layouts/Base.astro:109 - The focus hand-off only runs when the clicked control was itself the focused one, so it misses the t key path. Sequence: on a wide screen with keys on, a keyboard user Tabs to the rose-pine theme-name button and presses t. enableShortcuts clicks the hint button [data-ws-key=t], so focused is false (activeElement is the theme-name button, not control). The theme switches, the focused rose-pine button gets display:none, and focus falls to <body> instead of moving to rose-pine-dawn. This breaks the invariant the comment at lines 111-112 promises. Fix: capture const active = document.activeElement before toggleTheme(), then move focus when active matches [data-theme-name] and has no client rects. That covers both the click path and the shortcut path.
  • ⚠️ src/layouts/Base.astro:148 - Simplification: fix round 1 added a focusout listener on every theme-name button (Base.astro:148-153). When the system theme flips while a theme-name button has focus, it moves focus to the visible one. Nothing required it. The finding it came from (focus-lost-on-t-key) asked only to capture document.activeElement before toggleTheme() so the click path and the t-key path both hand focus over, and the round already did that at Base.astro:131-146. Nothing in the user intent asks for focus handling when the system theme changes. No defect was found in it: focusout with a null relatedTarget from clicking elsewhere or leaving the window is a no-op because the button is still visible. Recommended remedy: remove the listener (lines 148-153) and keep the minimal keepFocus(focused) click-path fix, unless the author wants this extra behavior.

🔧 Fix applied.
✅ Re-checked - no issues remain.

✅ **Test** - passed

✅ No issues found.

  • Live validation: ✅ go - 10 of 10 scenarios driven live against the product
Scenario Result Live Evidence
Visitor opens the home page on desktop and sees the S2 terminal: tab bar (ghost + whatsaaaa, 1 home/2 projects/3 ideas, github ↗), whoami pane (ghost, handle with block cursor, tagline, bio, handle li… ✅ pass live 01-home-desktop-dark.png, 07b-home-desktop-light.png
Projects list shows design-system, form-builder, dotfiles as active and building-blocks as experimental with the agreed description, and no sample-apps repo ✅ pass live 01-home-desktop-dark.png, 12-projects-list-desktop-dark.png (total 4)
Ideas tab lists two real ideas (React and Vue component libraries) and an idea page opens ✅ pass live 14-ideas-list-desktop-dark.png, 15-idea-vue-desktop-dark.png
Project detail page and 404 render in the terminal frame with correct current tab, status path, and 404 status/noindex ✅ pass live 13-project-design-system-desktop-dark.png, 16-404-desktop-dark.png, curl 404 status
Keyboard user presses p, i, g, 1-3 to navigate and t to switch the theme; the theme is remembered on the next page; / opens no command search ✅ pass live 02-theme-shortcut-transcript.txt, 03-shortcuts-and-keys-switch-transcript.txt
Visitor turns the keys switch off: hints and tab numbers hide, keys do nothing, the choice survives a reload, and turning it on restores the keys ✅ pass live 03-shortcuts-and-keys-switch-transcript.txt, 10-home-320-light-keys-off.png
Phone visitor (390px touch) taps the theme name in the status line: the theme switches, is remembered across pages, and the browser-bar theme-color follows the chosen theme (system dark and system lig… ✅ pass live 04-phone-390-dark-before-tap.png, 05-phone-390-after-tap-light.png, 05-phone-tap-theme-name-transcript.txt
Keyboard user focuses the theme name and presses t, Enter or Space (keys on and off): focus moves to the newly shown theme name instead of falling to body ✅ pass live 06-theme-focus-handoff-transcript.txt, 07-desktop-statusline-focus-after-t-light.png
Adversarial reflow at 320-400px in 2px steps, both themes, keys on/off: no functional status-line item clipped, no overflow in the window/tab bar/status line/panes, path either readable with full padd… ✅ pass live 08-reflow-sweep-320-400-transcript.txt (328 combinations, 0 issues), 09-statusline-sweep-.png, 10-home-320-.png
Visitor presses the ghost three times and it shouts the handle in a speech bubble ✅ pass live 11-ghost-easter-egg-shout.png, 11-ghost-easter-egg-transcript.txt
  • pnpm build (exit 0, 10 pages) then pnpm preview --port 4391 --host 127.0.0.1 (the preview daemon actually listened on 127.0.0.1:4393), stopped afterwards with astro preview stop
  • Headless Chrome for Testing via chrome-devtools-axi (session nm01m7b4): desktop 1440x900 screenshots of home in both themes, projects list, design-system project, ideas list, vue idea, 404 (HTTP 404 + noindex)
  • Keyboard run: p, i, 1, 2, 3, g (click intercepted, so the browser never left the site), /, the keys switch on/off/remembered, and t with keys on and off
  • Phone 390x844 mobile+touch: tapped the theme name (system dark, then system light). Checked data-theme, the stored ws-theme, the matching theme-color meta, the background, and that the choice survives to the next page
  • Focus hand-off: Tab to the theme-name button, then t, t, Enter, Space, plus Enter with keys remembered off. Checked that activeElement and :focus-visible move to the shown theme name
  • Reflow sweep: 320-400px in 2px steps in same-origin iframes, dark/light x keys on/off, on / and /ideas/react-component-library/ (328 combinations). Checked that the mode, keys switch and theme name are inside the status line and not clipped. Checked .window/.ws-tab-bar/.ws-status-line/.pane/.column/page overflow. Checked that the path is absent or shows at least one character plus the ellipsis with its full 10px padding and doesn't overlap the keys switch. Checked that the whoami cursor, h1 and tagline fit the pane
  • Visual status-line strips at all 41 widths for each theme/keys combination, plus full-page 320px home screenshots (light/keys off, dark/keys on)
  • Ghost easter egg: pressed the ghost 3-4 times, which brought up the speech bubble (screenshot)
  • Console check: no console messages
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

Build every page in the design system's terminal frame: a ws-term window
with the ghost and handle in the tab bar, numbered tabs and a status line
whose key hints all work (p, i, g, t and the tab numbers), with the keys
switch and the theme name. The home page is the two panes of the S2
mockup, whoami and ls ~/projects; lists, detail pages and the 404 share
the frame in one column.

Load @whatsaaaa/design-system 0.1.0 the documented way: its stylesheet
after the theme and keys head scripts, defineGhost() and enableShortcuts()
on the client, and <ws-ghost> rendered on the server. All site styles take
their colors, type and space from its tokens. The handle's favicons and
social card come from its asset kit, unchanged.

Replace the placeholder content with form-builder, design-system, dotfiles
and building-blocks, written from their public READMEs, and two ideas: a
React and a Vue component library on the design system.

Align the Node engines with the package's (^22.18.0 || >=24.12.0).
The t hint is hidden on a phone, so a phone visitor had no way to switch
themes. The theme name in the status line (rose-pine or rose-pine-dawn)
is now a button that switches the theme at every width, as in the Vue
sample app. When it is pressed from the keyboard the focus moves to the
name that shows next, so it is not lost.

To keep the path readable next to it on a phone, the status line's
segments are a little tighter there and the path shows only the file's
name; the current tab says where it is. The phone gutter now starts
where the tab bar's brand does.
…--frozen-lockfile` with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION. pnpm 11.27.0 by default rejects packages less than a day old, and `@whatsaaaa/design-system@0.1.0` was published today (2026-11-13T17:33Z). This PR's lockfile is the first to depend on it, so the failure comes from this change, not from the CI infrastructure. Reproduced with a fresh copy (package.json + pnpm-lock.yaml, its own store and cache dirs, CI=true): same error. A plain local install passed only because pnpm reused a check result it had already saved for this lockfile ("verified 2h ago"). Invariant: every install that reads the committed lockfile must pass pnpm's active supply-chain policies. That covers three paths: the CI job (`ci.yml`), the deploy workflow's `withastro/action` install on push to `main` (`deploy.yml`), and a fresh local install. All three read the root `pnpm-workspace.yaml`, so the fix goes in that one file. Fix: added `pnpm-workspace.yaml` with `minimumReleaseAgeExclude: ['@whatsaaaa/design-system']` and a two-line comment saying why. The exception covers only the user's own design-system package. The default one-day wait still applies to every other dependency (`pnpm config get minimumReleaseAge` is unset, so the default holds), and the lockfile is unchanged. Verification: - The fresh copy plus the new file runs `pnpm install --frozen-lockfile` with exit 0 ("Lockfile passes supply-chain policies"), and its lockfile is byte-identical afterwards. - In the worktree: `pnpm install --frozen-lockfile` ok, `pnpm format:check` clean, `pnpm lint` clean, `pnpm check` 0 errors/0 warnings/0 hints, `pnpm build` built 10 pages. - The temporary `.ci-repro` directory was removed. Alternative not taken: no code change. The failure clears on its own after 2026-11-14T17:33Z, but until then both CI and the deploy stay blocked, and it would recur on every same-day design-system release
@whatsaaaa
whatsaaaa merged commit 0633cc0 into main Nov 13, 2026
1 check passed
@whatsaaaa
whatsaaaa deleted the fm/landing-ds-restyle branch November 13, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant