feat(app-store): redesign App Store pages#289
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3ef2075c21
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Ready-to-use,{' '} | ||
| <span className="whitespace-nowrap"> | ||
| One-Click Deployment | ||
| </span> |
There was a problem hiding this comment.
The /[lang]/products/app-store page now renders fixed English marketing copy and search prompt in the hero, but this component has no lang-based translation path. On non-English routes (for example zh-cn), users will still see English text, which is a regression from the previous localized page content and makes the localized route inconsistent with its metadata/language URL.
Useful? React with 👍 / 👎.
| className="mb-12 inline-flex items-center gap-2 text-xs text-zinc-500 transition hover:text-zinc-200 lg:mb-[92px]" | ||
| > | ||
| <ArrowLeft className="h-3.5 w-3.5" /> | ||
| Back to templates |
There was a problem hiding this comment.
The detail hero uses hardcoded English UI strings (for example the back link and CTA text) even though this route is language-scoped (/[lang]/...). As a result, localized pages like zh-cn now show English labels on the primary detail surface, which regresses the previous language-aware behavior and breaks locale consistency for production users.
Useful? React with 👍 / 👎.
2 participants
Redesign the App Store listing and detail pages to match the new Figma direction, including the dark hero, real app icons/screenshots, category tabs, search, sorting, pagination, FAQ styling, home-style footer, and redesigned template detail sections.
Use real app data from
apps.jsonfor screenshots, deploy counts, related templates, and deploy actions. Keep the existing shared Header/Footer flow and reuse pricing FAQ data.Tested:
npm run lint/products/app-store/and/en/products/app-store/eaglercraft-server/