Codex
64 lines
2.5 KiB
Markdown
64 lines
2.5 KiB
Markdown
# Roadmap
|
|
|
|
## Codex Execution Directive
|
|
|
|
- Highest-priority directive: continue driving this project toward production readiness without waiting for step-by-step confirmation.
|
|
- After each completed change, immediately proceed to the next highest-impact production issue unless the user explicitly pauses or redirects the work.
|
|
- Prioritize uptime, admin usability, content correctness, multilingual integrity, redirects, and frontend polish before lower-priority refactors.
|
|
- Keep the local git history current with meaningful commits as major stabilization steps land.
|
|
|
|
## Phase 0 — Discovery (current)
|
|
- Confirm brand positioning statement
|
|
- Confirm CMS selection
|
|
- Audit existing content, imagery, and assets
|
|
- Capture full legacy URL inventory for 301 mapping
|
|
- Confirm content ownership and editorial workflow
|
|
- Deliverables: finalized brief, IA, content model, tech plan
|
|
|
|
## Phase 1 — Design
|
|
- Design tokens and component library
|
|
- Homepage, Products overview, Product Detail
|
|
- Support landing, FAQ, Warranty, Contact
|
|
- Downloads, About, Dealers, News list + article
|
|
- Mobile and desktop parity
|
|
- English and Chinese copy samples validated in layout
|
|
|
|
## Phase 2 — Build
|
|
- Next.js project scaffold with i18n routing
|
|
- Design system in Tailwind + component primitives
|
|
- Payload CMS schema implementation and editor onboarding
|
|
- Page routes, data fetching, preview mode
|
|
- Product content integration for downloads, videos, and reviews on product detail pages
|
|
- Downloads center integration from CMS-managed file metadata
|
|
- SEO foundations (metadata, sitemap, hreflang, structured data)
|
|
- 301 redirect map wired at edge
|
|
- Contact form with validation and spam protection
|
|
|
|
## Phase 3 — Content & QA
|
|
- Editorial content entry for both locales
|
|
- Seed import QA for firmware packages, videos, and reviews
|
|
- Visual QA on desktop and mobile
|
|
- Accessibility review (WCAG 2.1 AA)
|
|
- Performance tuning to hit Lighthouse ≥ 90 on mobile
|
|
- SEO audit, internal link audit
|
|
- 404 and redirect verification
|
|
|
|
## Phase 4 — Launch
|
|
- Staging sign-off
|
|
- DNS cutover plan
|
|
- Post-launch monitoring: uptime, errors, Core Web Vitals, 404s
|
|
- Hotfix window
|
|
|
|
## Phase 5 — Post-launch
|
|
- Content governance rhythm
|
|
- News publishing cadence
|
|
- Quarterly SEO review
|
|
- Performance and accessibility re-check
|
|
|
|
## Roles
|
|
- Product lead: scope, priorities, sign-off
|
|
- Design lead: visual system, page design
|
|
- Engineering lead: stack, CMS integration, infra
|
|
- Content lead: copy, translation, editorial workflow
|
|
- SEO lead: redirect map, metadata strategy, post-launch audit
|