feat(dashboard): shadcn/ui redesign — landing page, dashboard spacing, chat components#339
Conversation
Co-Authored-By: Duyet Le <me@duyet.net> Co-Authored-By: duyetbot <bot@duyet.net>
Split hero with code demo, numbered workflow, feature grid, CTA band, rich footer. Consistent max-w-6xl px-6 container across sections. Drops the Anthropic-brand experiment (Poppins/Lora, warm palette). Co-Authored-By: Duyet Le <me@duyet.net> Co-Authored-By: duyetbot <bot@duyet.net>
…ormalization New Message/Bubble primitives (shadcn June 2026 chat component API), conversation view rebuilt on them; dashboard pages normalized to consistent px-6/gap-6 shells and bg-card/border-border surfaces. Co-Authored-By: Duyet Le <me@duyet.net> Co-Authored-By: duyetbot <bot@duyet.net>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (28)
✨ 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 |
PR #339 (shadcn redesign) dropped three content blocks from the landing page that existed nowhere else: the five-primitives grid, the memory-vs-AgentState comparison table, and the API-surface endpoint table. Recover and restyle them for the new shadcn token system instead of letting them stay lost in history. - Landing page: add a "Five primitives" section (state, lease, claim, token, conversation) restyled with bg-card/border-border/hover:bg-muted, since the current feature grid had silently stopped mentioning three of the five core primitives. - New /compare page: houses the memory-vs-AgentState comparison table, linked from header nav, footer, and the new primitives section. - docs.astro: add an "API surface" reference section reusing the existing endpoint-list pattern and methodColor() helper already in that file, matching its (pre-#339) token conventions. Closes #354 Co-Authored-By: Duyet Le <me@duyet.net> Co-Authored-By: duyetbot <bot@duyet.net>
…ce (#356) * feat(dashboard): restore primitives grid, comparison table, API surface PR #339 (shadcn redesign) dropped three content blocks from the landing page that existed nowhere else: the five-primitives grid, the memory-vs-AgentState comparison table, and the API-surface endpoint table. Recover and restyle them for the new shadcn token system instead of letting them stay lost in history. - Landing page: add a "Five primitives" section (state, lease, claim, token, conversation) restyled with bg-card/border-border/hover:bg-muted, since the current feature grid had silently stopped mentioning three of the five core primitives. - New /compare page: houses the memory-vs-AgentState comparison table, linked from header nav, footer, and the new primitives section. - docs.astro: add an "API surface" reference section reusing the existing endpoint-list pattern and methodColor() helper already in that file, matching its (pre-#339) token conventions. Closes #354 Co-Authored-By: Duyet Le <me@duyet.net> Co-Authored-By: duyetbot <bot@duyet.net> * fix(dashboard): use API_BASE_URL for docs API-surface base URL Rebase fixup after #355 landed src/lib/site.ts (single source of truth for the site origin, replacing hardcoded https://agentstate.app). The new "API surface" section added by this branch had one hardcoded URL in its footer note; switch it to API_BASE_URL to match every other occurrence in docs.astro. Co-Authored-By: Duyet Le <me@duyet.net> Co-Authored-By: duyetbot <bot@duyet.net> --------- Co-authored-by: duyetbot <bot@duyet.net>
Summary
Full visual redesign moving the dashboard to a clean shadcn/ui design language and removing the Anthropic-brand experiment.
bg-background,bg-card,bg-muted,text-muted-foreground,border-border,bg-primary, …) mapped onto the existing token system via@theme inline, so light/dark theming keeps working and registry components drop in cleanly.max-w-6xl px-6container; Anthropic brand CSS/fonts (Poppins/Lora) removed.Message/Bubbleprimitives following the shadcn June 2026 chat-components API; user messages as end-aligned bubbles, assistant as full-width markdown, system/tool as labeled markers.px-6 py-6 gap-6),bg-card border-border rounded-xlcards, consistent page headers across all routes.Verification
bunx astro check: 0 errorsRelated
Filed 24 audit issues ([dashboard]/[sdk]/[docs] prefixes) as follow-up backlog; API audit issues to follow.
https://claude.ai/code/session_017PYqoyRqbiJDp6rbABqshW