Revert idstack.org landing to the original dark/indigo design - #56
Conversation
Bring back the original near-black (#0a0a0f) landing page with the indigo->purple gradient signature, but keep today's accurate content. A verbatim revert was avoided on purpose: the old black HTML was frozen at v2.5.0.0 and would have reintroduced the bare-clone install string that dea7ebc fixed. - docs/index.html: re-skin to the dark palette + gradient accents (hero headline, section eyebrows, CTA, install pill). Dark-only - removed the light/dark toggle, the theme bootstrap, and the Google Fonts dependency (back to the original system-font stack). All copy unchanged: v3.2.0.0, plugin-marketplace install, 8-skill + 2-utility pipeline, Output section. - Fix stale JSON-LD: softwareVersion 3.1.0 -> 3.2.0, dateModified -> 2026-05-14. Add the missing id="output" section anchor. - docs/og-template.html + og-image.png: re-skin the share card dark and regenerate the PNG at 1200x630. - DESIGN.md: record the landing as an intentional separate dark surface (scoped exception to the no-gradient anti-pattern). Reports keep the scholarly ivory "Proof" identity - their tokens are untouched. - test/smoke-test.sh: add 11 landing gate checks (dark bg, no toggle, no Google Fonts, marketplace install present, no legacy install string, current version, Output section). Suite is 268/268. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Code Review
This pull request decouples the idstack marketing landing page from the report token system, reverting it to a dark-only indigo/purple aesthetic and removing the theme toggle functionality. Corresponding updates are made to DESIGN.md, docs/og-template.html, and test/smoke-test.sh to reflect and enforce these changes. Feedback on the changes includes addressing a documentation contradiction in DESIGN.md regarding the theme toggle, resolving potential text visibility issues in older browsers by adding fallback colors where gradient text is used, and fixing a minor border color mismatch in the footer signup form.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
…border fixes Resolves all five Gemini Code Assist comments on PR #56: - DESIGN.md: drop the stale `data-theme="dark"` toggle (landing page) reference. The landing page is dark-only; the toggle is gone and the smoke test already guards against it returning. Removes the in-paragraph contradiction with the closing "dark-only (not a toggle)" sentence. - docs/index.html .hero h1: replace bare `color: transparent` with a `color: var(--accent-start)` solid fallback (matches the .eyebrow pattern), so the gradient title stays visible where `background-clip: text` is unsupported. `-webkit-text-fill-color` keeps the gradient in Blink/WebKit. - docs/og-template.html .brand + .hero-title: same fallback — add `color: #6366f1` and `-webkit-text-fill-color: transparent` (og-template uses hardcoded hex, no --accent-start var). - docs/index.html .footer-signup button: border `var(--accent-start)` → `var(--rule)`, giving the input+button group one continuous border (matches the var(--rule) border used on 9 other elements on the page). Adds smoke-test regression guards: no bare `color: transparent` in the landing page or OG template, and the OG template must use `-webkit-text-fill-color`. 272/272 smoke checks pass. Hero gradient and footer group verified rendering correctly in Chromium. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
What
Brings back the original near-black (
#0a0a0f) landing page with the indigo→purple gradient signature, re-skinned onto today's content so nothing is stale.The page that ran April–May 9 (best snapshot
46b8665, v2.5.0.0) was replaced by the scholarly ivory redesign (501eca4). This restores the black look but does not do a verbatim revert — that old HTML would have reintroduced the bare-clone install string (~/.claude/plugins/idstack) thatdea7ebcfixed, the "11 specialists" framing, and would have dropped the Output section.Changes
docs/index.html— dark palette (#0a0a0fbg) + indigo→purple gradient on the hero headline, section eyebrows, CTA, and install pill. Dark-only: removed the light/dark toggle, the theme bootstrap, and the Google Fonts dependency (back to the original system-font stack). All copy unchanged — v3.2.0.0, plugin-marketplace install, 8-skill + 2-utility pipeline, Output section.softwareVersion3.1.0 → 3.2.0,dateModified→ 2026-05-14) and added the missingid="output"anchor.docs/og-template.html+og-image.png— re-skinned the share card dark and regenerated the PNG at 1200×630.DESIGN.md— records the landing as an intentional separate dark surface (scoped exception to the no-gradient anti-pattern). Reports keep the scholarly ivory "Proof" identity; their tokens are untouched.test/smoke-test.sh— 11 new landing gate checks (dark bg, no toggle, no Google Fonts, marketplace install present, no legacy install string, current version, Output section).Scope
Landing page only. The per-course HTML reports,
templates/assets/idstack.css, and the report design system are unchanged.Verification
./test/smoke-test.sh→ 268/268 passed, 0 failed.data-theme/theme-toggle/fonts.googleapis/ legacy install string; dark bg + gradient + version fixes confirmed present; report tokens (#faf8f3,#7a1f1f) confirmed retained in DESIGN.md.Deploy is automatic on merge:
.github/workflows/static.ymlredeploys GitHub Pages fromdocs/.🤖 Generated with Claude Code