From 86a75e9e2da2e276846660808ec96949fa8bbf24 Mon Sep 17 00:00:00 2001 From: StanisLove Date: Tue, 14 Jul 2026 13:57:08 +0300 Subject: [PATCH] Add design and product documentation --- DESIGN.md | 12 ++++++++++++ PRODUCT.md | 21 +++++++++++++++++++++ 2 files changed, 33 insertions(+) create mode 100644 DESIGN.md create mode 100644 PRODUCT.md diff --git a/DESIGN.md b/DESIGN.md new file mode 100644 index 0000000..7e26c64 --- /dev/null +++ b/DESIGN.md @@ -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. diff --git a/PRODUCT.md b/PRODUCT.md new file mode 100644 index 0000000..5c8c400 --- /dev/null +++ b/PRODUCT.md @@ -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.