Add design and product documentation
This commit is contained in:
9
DESIGN.md
Normal file
9
DESIGN.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# Design — Universal Landing
|
||||
|
||||
Status: direction draft required.
|
||||
|
||||
- Choose one art direction tied to the product rather than a generic SaaS look.
|
||||
- Establish typography, semantic palette, spacing rhythm, imagery, and one accent behavior.
|
||||
- Prefer section composition over repeated cards and pills.
|
||||
- Motion must explain hierarchy or interaction and include reduced-motion fallback.
|
||||
- Validate the complete page at desktop and mobile widths before acceptance.
|
||||
9
PRODUCT.md
Normal file
9
PRODUCT.md
Normal file
@@ -0,0 +1,9 @@
|
||||
# Product — Universal Landing
|
||||
|
||||
Status: product-specific draft required.
|
||||
|
||||
## Baseline journey
|
||||
|
||||
The page must explain one offer to one primary audience, establish proof, resolve the main objections, and lead to one measurable conversion action.
|
||||
|
||||
Before implementation, replace generic placeholders with approved audience, problem, promise, proof, required sections, non-goals, content sources, and conversion criteria.
|
||||
Reference in New Issue
Block a user