42 lines
1.5 KiB
Markdown
42 lines
1.5 KiB
Markdown
|
# Discovery Questions
|
||
|
|
|
||
|
|
## A. Brand Positioning
|
||
|
|
1. What is the single sentence Eversolo should stand for on the new website?
|
||
|
|
2. Which competitors or adjacent brands feel closest to the intended market position?
|
||
|
|
3. What should users feel after visiting the homepage: trust, aspiration, technical respect, or brand desire?
|
||
|
|
|
||
|
|
## B. Audience Priority
|
||
|
|
Confirmed priority order:
|
||
|
|
1. Overseas HiFi enthusiasts
|
||
|
|
2. Domestic audiophiles
|
||
|
|
3. Dealers / distributors
|
||
|
|
|
||
|
|
Still to confirm:
|
||
|
|
1. Is the website serving more new prospects or existing owners?
|
||
|
|
2. Do domestic and overseas audiences need different messaging emphasis?
|
||
|
|
|
||
|
|
## C. Page Scope
|
||
|
|
1. Which pages are mandatory for launch?
|
||
|
|
2. Which pages can be phase two?
|
||
|
|
3. Does every product need its own detail page at launch?
|
||
|
|
|
||
|
|
## D. Content Inputs
|
||
|
|
1. Do you already have approved product copy, specs, manuals, and imagery?
|
||
|
|
2. Are there brand guidelines, logos, or existing visual assets?
|
||
|
|
3. Do you have media reviews, awards, or testimonials that can be published?
|
||
|
|
|
||
|
|
## E. Technology Stack
|
||
|
|
Confirmed:
|
||
|
|
- A CMS is required.
|
||
|
|
- Chinese and English content must both be supported cleanly.
|
||
|
|
|
||
|
|
Still to confirm:
|
||
|
|
1. Do you already prefer Next.js, Nuxt, Astro, or another stack?
|
||
|
|
2. Are there SEO constraints or legacy URLs that must be preserved?
|
||
|
|
3. Does deployment have any hosting constraints?
|
||
|
|
|
||
|
|
## F. Support Experience
|
||
|
|
1. Which support resources matter most: firmware, manuals, FAQ, contact, warranty?
|
||
|
|
2. Should support live as a top-level destination or a lighter utility layer?
|
||
|
|
3. Do users need product-specific support pages?
|