Skip to content

GAIA 1.7.0 site updates: /gaia-react-perf section + global anchor-scroll fix#53

Draft
stevensacks wants to merge 1 commit into
mainfrom
chore/gaia-1.7.0-site-updates
Draft

GAIA 1.7.0 site updates: /gaia-react-perf section + global anchor-scroll fix#53
stevensacks wants to merge 1 commit into
mainfrom
chore/gaia-1.7.0-site-updates

Conversation

@stevensacks

Copy link
Copy Markdown
Contributor

Summary

Prep branch for the GAIA 1.7.0 site updates: a new /gaia-react-perf feature section and a global anchor-scroll fix, plus structured-data and housekeeping changes.

Warning

Gated: do not merge until GAIA tags 1.7.0. Version lockstep and the changelog are handled by GAIA's release flow, not this branch. Opened as a draft to prevent a premature merge; mark ready once 1.7.0 is tagged.

New /gaia-react-perf feature section

  • Adds the measure-only React render-performance diagnostic as the 3rd section on Features (after Trust, before Load on demand).
  • Real ReducedSummary specimen (3 findings) + four meta cards. Headline: "App performance, optimized".
  • Marketing prose is plain-English with no internal coinage ("defeated memo", "blast radius times cost" removed). Specimen artifact fields (memo tag, memo-defeated count, react-doctor cross-refs) kept as real-output proof.
  • Correct attribution: GAIA diagnoses, Claude applies the fix you approve, then re-runs to confirm. Not "you apply the fix" (verified against the gaia gaia-react-perf skill).
  • Specimen "over budget" value right-aligned with the findings column.

Global anchor-scroll fix

  • Section headings landed ~6rem below the sticky header because scroll-mt-20 stacked on each section's py-20 top padding.
  • Dropped to scroll-mt-16 across all anchor-target sections so headings land just under the header. Verified empirically (heading sits ~79px below the 65px header on desktop, clears on mobile).

Structured data + housekeeping

  • index.html featureList + features/index.html ItemList position 7 and a /gaia-react-perf FAQ entry, de-jargoned to match the section.
  • Corrected stale "$5 cost cap per run" JSON-LD to the verified turn-limit framing.
  • Lint-rule count 1,314 → 1,450 (verified vs gaia README).

Verification

  • pnpm lint-all (tsc + eslint + prettier) ✅
  • pnpm build + prerender ✅ — no React #418 hydration errors (the net::ERR_FAILED prerender lines are pre-existing/benign).
  • JSON-LD validated as parseable; dist/features/index.html confirmed jargon-free.

🤖 Generated with Claude Code

Add the /gaia-react-perf feature section to the Features page (3rd section,
after Trust, before Load on demand): a measure-only render-performance
diagnostic with a real ReducedSummary specimen and four meta cards. Marketing
copy stays plain-English with no internal coinage (no "defeated memo" or
"blast radius times cost"), and attributes the workflow correctly: GAIA
diagnoses, Claude applies the fix you approve, then re-runs to confirm. Headline
is "App performance, optimized". Right-align the specimen's over-budget value
with the findings column.

Structured data: add featureList (index.html), ItemList position 7, and a
/gaia-react-perf FAQ entry (features/index.html), de-jargoned to match the
section. Correct the stale "$5 cost cap per run" JSON-LD to the turn-limit
framing.

Fix the global anchor-scroll gap: section headings landed ~6rem below the
sticky header because scroll-mt-20 stacked on each section's py-20 top padding.
Drop to scroll-mt-16 across all anchor-target sections so headings land just
under the header.

Bump lint-rule count 1,314 to 1,450 (verified vs gaia README).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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