Skip to content

feat(docs-next): rebuild homepage to sell the product#301

Merged
EmersonBraun merged 6 commits into
mainfrom
fix/ci-cd-for-v1
Apr 15, 2026
Merged

feat(docs-next): rebuild homepage to sell the product#301
EmersonBraun merged 6 commits into
mainfrom
fix/ci-cd-for-v1

Conversation

@EmersonBraun

Copy link
Copy Markdown
Collaborator

Summary

  • Full 7-section landing replaces the stub hero: hero + live demo, social proof bar, problem, solution, benefits, provider strip, final CTA
  • Live hero demo: auto-cycling agent conversation that types, fires tool calls, then renders real React widgets (weather card, BTC price chart, order tracker, flight list). Sells the "agents render components, not markdown" angle
  • Examples restored: interactive components (BasicChat, ToolUse, RAG, Multi-Agent, Code Assistant, Support Bot, MUI/shadcn, Markdown, Multi-Model, Agent Actions) ported from legacy Docusaurus → wired into /docs/examples/* mdx
  • Clickable package grid: each package card in the solution section links to its docs
  • Examples index links fixed: relative → absolute (/docs/examples/<slug>)
  • Live npm-downloads + GitHub-stars social-proof bar
  • Brand tokens (direction B: midnight/foam/surface) applied across landing + widgets + wrappers

Test plan

  • pnpm --filter @agentskit/docs-next dev — homepage loads, hero demo cycles through 4 scenes without flicker
  • Click tab pills in demo → scene resets + restarts cleanly, no overlap
  • Long tool-call labels wrap inside the card (no horizontal scroll)
  • Package cards navigate to correct /docs/... routes
  • /docs/examples index links land on the correct example pages
  • Each /docs/examples/<slug> page renders its live demo
  • npx tsc --noEmit passes
  • OG/Twitter metadata renders (share preview)
  • prefers-reduced-motion skips typing/streaming animations

Every workflow was broken after the Fumadocs migration and the Node 25
Docusaurus breakage. Fixing in one pass.

Problems that were live on main:

- ci.yml, coverage.yml, size.yml, release.yml all ran 'pnpm build'
  (no filter). Turbo tries to build every workspace project including
  @agentskit/docs, which is Docusaurus-on-Node-25 and crashes on
  'mdxCrossCompilerCache'. Every one of these jobs failed in CI.

- docs.yml still deployed @agentskit/docs (old Docusaurus) to GitHub
  Pages. That site is a) retired, b) doesn't build anyway. The
  replacement lives at apps/docs-next (Fumadocs) and deploys via
  Vercel's GitHub integration, not GitHub Pages.

- ci.yml duplicated bundle-size enforcement by hand-rolling a
  check_size bash function — size.yml already does this properly
  via size-limit with the .size-limit.json budget. Paths were wrong
  too (no packages/react/dist/index.js without the preceding build).

- Version drift across workflows: checkout@v4 vs v6, pnpm@v4 vs v5,
  node 20 vs 22. doctor's recommendation is Node 22+.

What this does:

1. Standardize every workflow to:
     actions/checkout@v4
     pnpm/action-setup@v4
     actions/setup-node@v4
     node-version: 22

2. Replace every 'pnpm build' with 'pnpm --filter "./packages/*" build'.
   Legacy docs is not in scope for CI until it's retired.

3. ci.yml — drop the hand-rolled size check. size.yml is the single
   source of truth for bundle-size gates.

4. docs.yml — convert from 'deploy Docusaurus to GH Pages' to
   'build @agentskit/docs-next on every relevant PR/push'. Deploy
   is Vercel's job via the repo's GitHub App integration. Workflow
   is now validation-only + path-filtered so it doesn't run for
   unrelated changes.

5. release.yml — same filter fix, same version bumps. Changesets
   action itself is unchanged.

No i18n wiring — per the i18n strategy RFC, translated content is
frozen during the Fumadocs migration, so the workflow has nothing
to do for locales.

Verified locally:
- pnpm --filter './packages/*' lint → 28/28 passing
- pnpm --filter './packages/*' build → 22/22 passing
- pnpm test → 22/22 passing, 538 tests
- pnpm exec size-limit → every package under budget
- pnpm --filter @agentskit/docs-next build → 74 routes clean

Refs #211
Vercel auto-detected Turbo and started adjusting defaults, which
ended up running 'turbo build' at the repo root — that fans out to
every workspace including @agentskit/docs (legacy Docusaurus, broken
on Node 25).

Explicit config pins framework = Next.js, builds packages first so
workspace:* resolutions work, then builds the docs site. Skips
unrelated commits via ignoreCommand to save build minutes.

Paired with this file, the Vercel dashboard should set:
  Root Directory:  apps/docs-next
  Framework:       Next.js (auto-detected from this file)
  Node.js:         22.x
- Replace minimal hero with full 7-section landing (hero + demo,
  social proof, problem, solution, benefits, provider strip, CTA)
- Add live hero demo: auto-cycling agent conversation that renders
  real React widgets (weather card, BTC price chart, order tracker,
  flight list) via tool calls — sells the "agents render components,
  not markdown" angle
- Restore interactive example components (BasicChat, ToolUse, RAG,
  Multi-Agent, etc.) ported from the legacy Docusaurus site; wire
  them into each /docs/examples mdx
- Fix /docs/examples index links (relative -> absolute)
- Make package grid clickable; each card links to its package docs
- Add live npm downloads + GitHub stars social-proof bar
- Brand tokens (direction B: midnight/foam) applied throughout
@vercel

vercel Bot commented Apr 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
agentskit-doc Ignored Ignored Preview Apr 15, 2026 9:15pm

@EmersonBraun EmersonBraun merged commit 5ed061e into main Apr 15, 2026
7 checks passed
EmersonBraun added a commit that referenced this pull request Apr 15, 2026
Main received the squash-merged #301 homepage rebuild; this branch
already contains that work plus follow-up polish (contribute hub,
animated brand, light mode, SEO, OG per-page, hero-demo scroll fix,
domain normalization). Keeping HEAD resolves every conflict since
HEAD is strictly newer.
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