Add design and product documentation
This commit is contained in:
16
DESIGN.md
Normal file
16
DESIGN.md
Normal file
@@ -0,0 +1,16 @@
|
||||
# Design — Lineform Studio
|
||||
|
||||
## Direction
|
||||
|
||||
Strict Swiss/brutalist editorial system: black and white, large indexed typography, architectural imagery, hard rules, and disciplined asymmetry.
|
||||
|
||||
## System
|
||||
|
||||
- Preserve the existing grid and semantic tokens; avoid soft SaaS cards and decorative gradients.
|
||||
- Use index numbers, captions, measured whitespace, and full-bleed project media.
|
||||
- Motion behaves like editorial sequencing, never spectacle.
|
||||
- Mobile keeps project metadata adjacent to its image and maintains keyboard-visible focus.
|
||||
|
||||
## Intentional patterns
|
||||
|
||||
One-pixel borders, side rules, and indexed tabs are deliberate parts of the architectural system and may be detector-waived with this rationale.
|
||||
21
PRODUCT.md
Normal file
21
PRODUCT.md
Normal file
@@ -0,0 +1,21 @@
|
||||
# Product — Lineform Studio
|
||||
|
||||
Status: approved baseline.
|
||||
|
||||
## Audience and job
|
||||
|
||||
Prospective architecture clients and collaborators need to assess built work, understand the studio process, and submit a qualified project brief.
|
||||
|
||||
## Primary journeys
|
||||
|
||||
1. Explore projects through typology, place, scale, and completion evidence.
|
||||
2. Understand services, process, and studio point of view.
|
||||
3. Submit a brief with location, scope, timing, and constraints.
|
||||
|
||||
## Non-goals
|
||||
|
||||
- No generic stock architecture, invented awards, or lead forms without project context.
|
||||
|
||||
## Success criteria
|
||||
|
||||
Work remains the dominant proof, project metadata is scannable, and the brief form is the clear conversion path.
|
||||
Reference in New Issue
Block a user