§ masterplan.md
Brutalist Event Posters
A raw, typography-first events site for underground concerts and workshops. No images, just bold type, ASCII art and date grids.
01
App overview and objectives
An events site built like a wall of posters: enormous type, hard edges, one accent colour, and a ticket link that never takes more than two taps. It should look like the flyers stapled outside the venue.
02
The problem worth solving
Event listings sold as polite cards all look the same, and a scene's identity lives in its graphic language. Turning the listing itself into the poster gives small venues an identity that platforms strip away.
03
Target audience
- Primary — Independent music and art venues and their regulars.
- Secondary — Promoters and artists submitting events.
04
Roles and permissions
- Visitor — read-only public pages, can sign up.
- Member — owns their own records, cannot see other users' data.
05
Core features
- Poster-style event listings generated from title, date and one image
- Event detail with lineup, doors, age policy and accessibility notes
- Ticket handoff to a provider, or on-site basic ticketing
- Archive of past events with photos
- Promoter submission form with review queue
- Venue page with map, capacity and technical specs
Deliberately later
- Membership passes
- Waitlists for sold-out shows
- Printable poster export
06
Technical stack
Static-rendered React, a small CMS for events, tickets handled by an external provider.
Why: Ticket sales spike hard; letting a provider absorb the load and the payment compliance keeps your site simple and always up.
Alternatives: Full in-house ticketing (better margins and data, real financial and fraud responsibility) or a listings platform (zero effort, zero identity).
07
Conceptual data model
Event — title, date, doors, lineup, poster image, ticket url, status
Venue — name, address, capacity, tech specs, accessibility
Submission — promoter, event draft, status, reviewer notes
ArchiveItem — event, photos, recap, attendance
08
Integrations
- Ticketing provider
- Map embed
- Image storage
- Calendar export
09
UI design principles
- Raw structure on display: visible grid, hard edges, black-on-white with one violent accent.
- System or grotesque type at extreme sizes; no decoration that isn't structural.
- Interactions are instant and blunt — no easing, no fades.
10
Security considerations
- Submissions are moderated before publication to prevent scam listings.
- No payment data handled on-site when using an external ticket provider.
- Contact details of promoters kept private.
11
Development phases
Phase 1 — Prove the core
- — Poster-style event listings generated from title, date and one image
- — Event detail with lineup, doors, age policy and accessibility notes
- — Ticket handoff to a provider, or on-site basic ticketing
- — Static content and design system in place
- — Basic analytics
Phase 2 — Make it real
- — Archive of past events with photos
- — Promoter submission form with review queue
- — Venue page with map, capacity and technical specs
- — Accounts, sign-in and password reset
- — Empty, loading and error states everywhere
Phase 3 — Polish and launch
- — Performance, accessibility and SEO pass
- — Legal pages, contact route and 404 handling
- — Wire up: Ticketing provider
- — Wire up: Map embed
Phase 4 — Grow
- — Membership passes
- — Waitlists for sold-out shows
- — Printable poster export
12
Challenges and solutions
Risk — Brutalist type destroys readability on phones
Solution — Fluid type scale with a hard minimum size and a tested contrast ratio on every colour pair.
Risk — Poster generation looks cheap
Solution — A few strong layout templates chosen by aspect ratio, not one generic template.
Risk — Stale listings after events pass
Solution — Automatic transition to archive at midnight after the event.
13
Future expansion
- Scene-wide network across venues
- Artist profiles
- Merchandise drops tied to shows
14
Page list (13 pages)
- 01 PUBLIC Upcoming — The poster wall of what is next.
- 02 PUBLIC Archive — Past shows and photos.
- 03 PUBLIC Venue — Location, capacity, specs, accessibility.
- 04 PUBLIC Tickets — Handoff and purchase guidance.
- 05 PUBLIC Submit — Promoter event submission.
- 06 AUTH Sign up — Create an account with email or a social provider.
- 07 AUTH Log in — Return to the account, with error and lockout states.
- 08 AUTH Reset password — Request a reset link and set a new password.
- 09 APP (signed in) Account settings — Profile, email, password, language and delete account.
- 10 PUBLIC Contact — Contact form plus real address, phone and email.
- 11 LEGAL & SYSTEM Privacy policy — What data is collected, why, and how to remove it.
- 12 LEGAL & SYSTEM Terms of service — Rules of use, liability and account termination.
- 13 LEGAL & SYSTEM 404 not found — Friendly dead end with search and links back.
15
Page map
PUBLIC AUTH APP (signed in) LEGAL & SYSTEM ─────────── ───────────────── ─────────────────── ─────────────────── ├─ Upcoming ├─ Sign up └─ Account settings ├─ Privacy policy ├─ Archive ├─ Log in ├─ Terms of service ├─ Venue └─ Reset password └─ 404 not found ├─ Tickets ├─ Submit └─ Contact key flows: Upcoming ──▶ Tickets Upcoming ──▶ Venue Archive ──▶ Upcoming