Skip to content

feat(ui): redesign home and results as decision-oriented workflow - #62

Merged
chake111 merged 1 commit into
mainfrom
codex/identify-legacy-issues-for-project
Apr 20, 2026
Merged

chake111 merged 1 commit into
mainfrom
codex/identify-legacy-issues-for-project

Conversation

@chake111

Copy link
Copy Markdown
Owner

Motivation

  • Make the home page a focused decision-entry funnel and turn the results page into a decision-support workspace so users can quickly choose and act on recommended AI tools.
  • Reduce immediate technical friction by addressing the specific legacy debts that block the UI/product upgrades (overloaded results component, duplicated state UIs, inconsistent input placeholders, scattered CTA/tag styles).

Description

  • Reworked home experience: strengthened hero hierarchy, clearer trust framing, unified CTA styling and a decision-oriented HomeResultsPreview (files changed: ui/app/[locale]/page.tsx, ui/components/home/home-hero.tsx, ui/components/home/home-results-preview.tsx).
  • Results presentation refactor: extracted ToolDecisionCard and replaced the inline card rendering in ResultsList so the list becomes a container and cards become a clear, reusable decision component (added ui/components/results/tool-decision-card.tsx, modified ui/components/results/results-list.tsx).
  • Unified state UIs: added StatePanel / LoadingStatePanel to consolidate loading/empty/no-match states and replaced duplicated blocks (added ui/components/ui/state-panel.tsx).
  • Style and small UX fixes: introduced lightweight style tokens/classes (.app-tag, .app-cta-primary, .app-cta-secondary) and fixed placeholder i18n by adding rotatingPrefix to SearchInput (modified ui/app/globals.css, ui/components/search-input.tsx).
  • Copy updates: updated zh/en messages to a more concise, decision-focused tone and added new labels for capabilities/next actions (modified ui/messages/zh.json, ui/messages/en.json).

Testing

  • Ran type checking with npm run typecheck (tsc --noEmit) and it passed. ✅
  • Ran lint with npm run lint and it reported a repository-level ESLint configuration issue (ESLint v9 expects eslint.config.*), so lint did not pass in this environment. ⚠️
  • Ran production build with npm run build and it failed due to next/font attempting to fetch Google Fonts (Geist / Geist Mono) which is blocked in the current environment; this is an environment/network issue rather than a functional regression. ⚠️

Codex Task

@vercel

vercel Bot commented Apr 20, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
ai-tool-picker Ready Ready Preview, Comment Apr 20, 2026 1:42pm

@chake111
chake111 merged commit 0091baa into main Apr 20, 2026
2 of 3 checks passed

This branch was successfully deployed

1 active deployment
Preview af9d5305 Deployed Apr 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant