Guide route
How Variation 04 was made.
This site is a static evidence vault. The guide explains why it reads like a terminal, when to choose concept over real, and how the intake form works.
Brief
Build a distinct JD Workshop variation that is recognizable as “information density as prestige.” Terminal visuals, monospace type, dense metadata, and searchable proof are the core system.
Technical guardrails: static-first, single H1 per route, reduced-motion path, no horizontal overflow, console clean on load.
Evidence labels
Verified repo, live site, public links, or actual JD Workshop material.
Fictional clients, synthetic metrics, or speculative products.
A concept implemented enough to inspect and improve.
Every labeled artifact in the vault follows the same metadata block: status, date, source, verification hash.
Visual system
Deep black background, terminal green tokens, and monospace type for metadata. The target is an evidence lab, not a marketing page. No media say more than a clean metadata record.
Interaction model
- Filter chips restrict evidence by status.
- Search filters by keyword, status, and date text.
- Command palette uses / for evidence search.
- Concept panels disclose fictional work clearly, with close controls.
Critique passes
- Pass 1: Static HTML/CSS/JS route structure built; all proof labels and metadata blocks included.
- Pass 2: Form behavior, command palette, overflow, reduced-motion rule set, and links checked.
- Pass 3: Verification script run; console checked for runtime errors; guide route validated.
Truth rules
Variation 04 follows the design constitution: fake testimonials are not fabricated, awards are not invented, and every concept is flagged. The intake form preserves accuracy by requiring status and context metadata up front.