feat(home): Enhance home section with new illustrations and translations - #833
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 09edce6d80
ℹ️ 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".
| await context.queryClient.query({ | ||
| ...intlQueryOptions({ | ||
| locale: context.locale, | ||
| namespaces: HOME_NAMESPACES, | ||
| }), |
There was a problem hiding this comment.
Move the home query out of the route file
Keep this file topology-only by exposing a home route loader/query contract from the TanStack feature module instead of constructing intlQueryOptions here and importing an app-local namespace list. The current arrangement couples the host route to the screen's query and namespace implementation, contrary to the repository's route-module boundary.
AGENTS.md reference: AGENTS.md:L26-L28
Useful? React with 👍 / 👎.
| <ScreenFrame | ||
| priority | ||
| screen={{ ...SCREENS.dashboard, alt: t('alt') }} |
There was a problem hiding this comment.
Avoid eagerly fetching both themed preview images
On every home-page load, priority is forwarded by ScreenFrame to both its light and dark <img> elements, making both screenshots eager and high-priority even though CSS hides one of them. The unused theme asset therefore competes with the visible LCP image; render the variants through mutually exclusive media sources or reserve eager priority for only the active variant.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e6057bbc6e
ℹ️ 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".
| { | ||
| blurb: 'A fast, typed API with OpenAPI docs served at /api/swagger.', | ||
| category: 'API', | ||
| color: '#e36002', |
There was a problem hiding this comment.
Reduce the integration palette to 3–5 colors
The new integration cards assign 11 distinct hex brand colors across this list, before counting the semantic foreground/background colors. This exceeds the repository’s required 3–5-color palette and makes the section visually inconsistent with the documented design system; consolidate these accents into a small shared palette.
AGENTS.md reference: AGENTS.md:L64-L64
Useful? React with 👍 / 👎.
Improving Documentation
pnpm lint:fixto fix formatting issues before opening the PR.Description
What?
Why?