Codex
131 lines
3.1 KiB
Markdown
131 lines
3.1 KiB
Markdown
# Sitemap
|
|
|
|
## Launch Scope
|
|
Phase one includes the following pages:
|
|
- Home
|
|
- Products
|
|
- Product Detail
|
|
- Support
|
|
- Downloads
|
|
- FAQ
|
|
- About
|
|
- Dealers
|
|
- News
|
|
|
|
## Primary Navigation
|
|
- Products
|
|
- Support
|
|
- About
|
|
- News
|
|
- Dealers
|
|
- APP (external static link to https://www.eversolo.com/controlapp/index.html)
|
|
|
|
Home is represented through the logo.
|
|
Downloads and FAQ live under Support as secondary entries.
|
|
The APP entry is an external link to the existing control app page and opens in a new tab; it is not a route on the new site.
|
|
|
|
## Page Structure
|
|
|
|
### 1. Home
|
|
Purpose: introduce the brand, surface featured products, route users into product or support journeys.
|
|
|
|
Modules:
|
|
1. Hero banner (lifestyle usage scene)
|
|
2. Featured products (4 cards)
|
|
3. One restrained brand or technology statement
|
|
4. Support entry (FAQ, Warranty, Contact shortcuts)
|
|
5. News / reviews / awards (light)
|
|
6. Footer
|
|
|
|
### 2. Products
|
|
Purpose: present the product portfolio without retail behavior.
|
|
|
|
Structure:
|
|
- Product overview page grouped by category
|
|
- Category filter or section anchors
|
|
- Entry points into each product detail page
|
|
|
|
### 3. Product Detail
|
|
Purpose: communicate positioning, core features, specs, gallery, and related support.
|
|
|
|
Sections:
|
|
- Hero
|
|
- Value proposition
|
|
- Key features
|
|
- Technical specifications
|
|
- Gallery / usage scene
|
|
- Related downloads and manuals
|
|
- Related products
|
|
|
|
### 4. Support
|
|
Purpose: give users fast access to practical resources.
|
|
|
|
Top-priority entries:
|
|
- FAQ
|
|
- Warranty
|
|
- Contact
|
|
|
|
Secondary entries:
|
|
- Downloads
|
|
- Manuals
|
|
- Firmware
|
|
|
|
### 5. Downloads
|
|
Purpose: serve firmware, manuals, and software files.
|
|
|
|
Structure:
|
|
- Filter by product
|
|
- Filter by file type
|
|
- Clear version and date metadata
|
|
|
|
### 6. FAQ
|
|
Purpose: answer common questions without requiring contact.
|
|
|
|
Structure:
|
|
- Grouped by topic
|
|
- Search / filter
|
|
- Cross-links to related downloads and contact
|
|
|
|
### 7. About
|
|
Purpose: communicate brand identity and philosophy.
|
|
|
|
Sections:
|
|
- Brand story
|
|
- Design and technology philosophy
|
|
- Milestones / awards
|
|
|
|
### 8. Dealers
|
|
Purpose: guide users to authorized purchase channels.
|
|
|
|
Structure:
|
|
- Region selector
|
|
- Dealer list per region
|
|
- Contact details
|
|
|
|
### 9. News
|
|
Purpose: publish updates, press coverage, and reviews.
|
|
|
|
Structure:
|
|
- Chronological list
|
|
- Categories: Announcements, Press, Reviews, Events
|
|
- Article detail page
|
|
|
|
## URL Convention
|
|
- English: `/en/...`
|
|
- Chinese: `/zh/...`
|
|
- Products: `/products`, `/products/[slug]`
|
|
- Support: `/support`, `/support/faq`, `/support/warranty`, `/support/contact`
|
|
- Downloads: `/downloads`
|
|
- About: `/about`
|
|
- Dealers: `/dealers`
|
|
- News: `/news`, `/news/[slug]`
|
|
|
|
## Legacy URLs
|
|
Legacy URLs must be preserved through 301 redirects that map old paths to the new structure. A full redirect table is required before launch and must cover product pages, downloads, news/articles, and any indexed support URLs.
|
|
|
|
## Open IA Questions
|
|
- Whether Products should be organized by category, series, or flagship-to-entry hierarchy
|
|
- Whether News and Reviews should live together or separately
|
|
- Whether Dealers is a primary nav item in all regions
|
|
- Whether About needs a standalone philosophy page or should stay lightweight
|