77 lines
2.6 KiB
Markdown
77 lines
2.6 KiB
Markdown
|
# Content Strategy Draft
|
||
|
|
|
||
|
|
## Tone of Voice
|
||
|
|
- Brand line: "A refined way to experience music."
|
||
|
|
- Minimal English
|
||
|
|
- Premium, calm, precise
|
||
|
|
- Short sentences
|
||
|
|
- International rather than region-specific
|
||
|
|
- No retail urgency language
|
||
|
|
- No exaggerated marketing copy
|
||
|
|
- No heavy technical jargon in overview pages unless needed
|
||
|
|
|
||
|
|
## Content Principles
|
||
|
|
1. Show restraint.
|
||
|
|
2. Lead with product meaning, not sales language.
|
||
|
|
3. Let images do part of the work.
|
||
|
|
4. Keep support writing practical and direct.
|
||
|
|
5. Separate brand storytelling from support utility.
|
||
|
|
6. Structure content so Chinese and English can diverge where needed, without breaking layout.
|
||
|
|
|
||
|
|
## Content Priorities
|
||
|
|
1. Brand perception
|
||
|
|
2. Product understanding
|
||
|
|
3. Support access
|
||
|
|
4. Dealer confidence
|
||
|
|
|
||
|
|
## Homepage Content Roles
|
||
|
|
### Hero
|
||
|
|
- Lifestyle scene
|
||
|
|
- One clear headline
|
||
|
|
- One short supporting line
|
||
|
|
- Primary CTA: explore product
|
||
|
|
- Secondary CTA: support or learn more
|
||
|
|
|
||
|
|
### Featured Products
|
||
|
|
- Exactly 4 products
|
||
|
|
- Each card should contain:
|
||
|
|
- product image
|
||
|
|
- model name
|
||
|
|
- one-line descriptor
|
||
|
|
- details CTA
|
||
|
|
|
||
|
|
### Technology / Craft Section
|
||
|
|
- Explain what makes the products distinct
|
||
|
|
- Avoid engineering overload on the homepage
|
||
|
|
- Link deeper technical content from product pages
|
||
|
|
|
||
|
|
### Support Entry
|
||
|
|
- Fast utility links
|
||
|
|
- Keep wording plain and functional
|
||
|
|
- Make service access obvious without letting support dominate the homepage
|
||
|
|
|
||
|
|
## Content Types Needed
|
||
|
|
- Brand copy
|
||
|
|
- Product overview copy
|
||
|
|
- Product detail copy
|
||
|
|
- Technical spec formatting
|
||
|
|
- Support content
|
||
|
|
- FAQ
|
||
|
|
- Dealer information
|
||
|
|
- News / press content
|
||
|
|
|
||
|
|
## CMS / Localization Considerations
|
||
|
|
- Chinese and English should be managed as parallel content, not a single locked translation layer.
|
||
|
|
- Components must tolerate different line lengths and content density across languages.
|
||
|
|
- Support content should be structured for easy maintenance in both languages.
|
||
|
|
|
||
|
|
## Open Content Questions
|
||
|
|
- Whether copy should be written English-first or translated from Chinese
|
||
|
|
- Whether product pages should lead with emotion or technical credibility
|
||
|
|
- Whether awards, reviews, and media quotes are available and approved for use
|
||
|
|
- Whether support content already exists in structured form
|
||
|
|
- Which team will own CMS publishing and updates
|
||
|
|
|
||
|
|
## Seed Content Rule
|
||
|
|
Example data used in design review, staging, and editorial onboarding should be scraped from the current Eversolo site (EN and ZH) rather than generated from scratch. Product imagery, copy, specs, support text, news, and dealer data should come from the legacy site so the new site is evaluated against real content. See `SEED-DATA-POLICY.md` for the full rule set.
|