feat(site): make quickstart the first-success path#43
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the home page to promote the new Quickstart guide, replacing the primary "Download starter" call-to-action with a "Start in 5 minutes" link to /quickstart and shifting the download link to the secondary action. Feedback on these changes suggests using the Zap icon instead of Terminal for the Quickstart card to avoid duplication with the Cockpit card, and updating the button copy to "Start in 2 minutes" to maintain consistency with the Quickstart page's own time estimates.
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.
| href: "/quickstart", | ||
| title: "Quickstart", | ||
| desc: "Install the MCP server, configure your tool, and write your first vault entry.", | ||
| icon: Terminal, |
There was a problem hiding this comment.
The Terminal icon is already used for the Cockpit route card in the same grid (line 195). To avoid visual repetition and improve clarity, consider using a distinct icon such as Zap for the Quickstart route.
Note: Remember to add Zap to the lucide-react imports at the top of the file.
| icon: Terminal, | |
| icon: Zap, |
| className="inline-flex min-h-12 w-full items-center justify-center gap-2 rounded-md bg-slate-950 px-5 py-3 text-sm font-semibold text-white shadow-[0_12px_32px_rgba(15,23,42,0.25)] transition-micro hover:bg-slate-800" | ||
| > | ||
| Download starter | ||
| Start in 5 minutes |
There was a problem hiding this comment.
There is a discrepancy in the estimated time for the quickstart process. The button here says "Start in 5 minutes", whereas the Quickstart page (site/src/app/quickstart/page.tsx) repeatedly references 2 minutes (e.g., "Two minutes to compound intelligence", "Install Starlight Intelligence in 2 minutes").
To maintain consistency in user expectations and brand messaging, consider aligning this to 2 minutes.
| Start in 5 minutes | |
| Start in 2 minutes |
| className="inline-flex min-h-12 items-center justify-center gap-2 rounded-md bg-slate-950 px-5 py-3 text-sm font-semibold text-white shadow-[0_12px_32px_rgba(15,23,42,0.25)] transition-micro hover:bg-slate-800" | ||
| > | ||
| Download starter | ||
| Start in 5 minutes |
There was a problem hiding this comment.
Aligning this button copy with the Quickstart page's 2-minute estimate for consistency.
| Start in 5 minutes | |
| Start in 2 minutes |
1 participant
Why
The homepage already proves the Starlight system with a real release-room console, but its primary action skipped the existing first-success path. This makes
/quickstartthe clear next step without redesigning the proof surface.Changes
/quickstartVerification
node_modules/.bin/eslint src/app/page.tsx— passnode_modules/.bin/tsc --noEmit— passgit diff --check— pass/quickstartand/downloadroute files existResource gate
Local production build was intentionally held because Yogabook remains in CRITICAL storage mode (<50 GiB). The draft preview/build is the cloud boundary; do not mark ready until it and visual QA pass.
Scope
One source file. No dependencies, media, lockfile, private telemetry, DNS, or production mutation.