Add design and product documentation
This commit is contained in:
12
DESIGN.md
Normal file
12
DESIGN.md
Normal file
@@ -0,0 +1,12 @@
|
|||||||
|
# Design — Juniper Table
|
||||||
|
|
||||||
|
## Direction
|
||||||
|
|
||||||
|
Seasonal editorial hospitality: warm natural color, tactile food imagery, refined type, and booking-led composition without luxury clichés.
|
||||||
|
|
||||||
|
## System
|
||||||
|
|
||||||
|
- Let menu typography and photography lead; avoid repetitive promotional cards.
|
||||||
|
- Booking controls expose availability and validation states clearly.
|
||||||
|
- Motion is slow and restrained, never delaying access to menu or booking.
|
||||||
|
- Mobile places service window, party size, allergy context, and confirmation expectations in sequence.
|
||||||
21
PRODUCT.md
Normal file
21
PRODUCT.md
Normal file
@@ -0,0 +1,21 @@
|
|||||||
|
# Product — Juniper Table
|
||||||
|
|
||||||
|
Status: approved baseline.
|
||||||
|
|
||||||
|
## Audience and job
|
||||||
|
|
||||||
|
Diners and event hosts need to understand the seasonal menu, service windows, seating formats, allergy handling, and booking confirmation process.
|
||||||
|
|
||||||
|
## Primary journeys
|
||||||
|
|
||||||
|
1. Explore current menu, sourcing, pairing, and dining format.
|
||||||
|
2. Choose a valid date, time, party size, and seating option.
|
||||||
|
3. Disclose relevant allergies or request private dining and understand host confirmation.
|
||||||
|
|
||||||
|
## Non-goals
|
||||||
|
|
||||||
|
- No guaranteed availability, hidden service terms, or unsupported instant confirmation.
|
||||||
|
|
||||||
|
## Success criteria
|
||||||
|
|
||||||
|
Menu and booking information stay current and legible, constraints are visible before submission, and private dining has a distinct qualified path.
|
||||||
Reference in New Issue
Block a user