What is included
Doorlist is a ticket marketplace for live events, with both sides of it built: fans find a show, pick seats and check out; organizers create shows, watch sales, scan tickets at the door and get paid. It ships 23 page files that render over 100 routes from demo data, a 47-component UI kit, light and dark modes, four presets and a right-to-left layout.
The stack: Next.js 16 (App Router), React 19, Tailwind CSS 4, shadcn/ui
on Base UI, MapLibre GL for the maps and Hugeicons for the icons. There
is no backend: every list is a typed array in lib/data/,
and what a visitor does (saved events, held seats, a paid order, a
sent ticket) lives in the browser's local storage.
For fans
| Route | What it does |
|---|---|
/, /home-2 | Two home pages: search with suggestions, this weekend by day, a seat-map preview, the fan guarantee, trending shows, FAQ |
/events | Listing with search, category tabs, filters, sort, saved-only and a grid, list or map view |
/events/map | The same listing beside a live map with price pins and search-as-you-move |
/events/[slug] | Event page: gallery, tiers with all-in prices, lineup and schedule, venue, organizer, similar shows |
/events/[slug]/seats | Seat map for reserved shows: theatre and arena plans, best available, a ten‑minute hold |
/checkout | Four steps with validation, the hold timer, a saved card and a confirmation |
/orders/[id] | Order confirmation: QR codes, add to wallet or calendar, transfer and resale |
/tickets | The fan's wallet: next show, upcoming, past and saved |
For organizers
| Route | What it does |
|---|---|
/sell | The organizer pitch: fees, a payout calculator, plans and a case study |
/organizer, /organizer-2 | Two dashboards: sales charts, tonight's show, recent orders |
/organizer/events, /organizer/events/[slug] | Every show, and one show's tiers, weekly sales and orders |
/organizer/orders, /organizer/orders/[id] | Order search, refunds, resend, and an order's activity |
/organizer/door | The door list: search, check in, undo |
/organizer/payouts | Paid and scheduled payouts, the payout account, a CSV export |
/organizer/settings | Profile with a live preview, team roles and invites, email notifications |
/organizer/new | Create an event in five steps with a live card preview |
Company and reference
| Route | What it does |
|---|---|
/about | Story timeline, team, pledge and open roles |
/contact | Help center with search and topics, self-serve fixes and a contact form |
/design-system | Every token and every kit component on one page |
| 404 | A not-found page with search |
Requirements
Node.js 20 or newer, and npm. Nothing else — there is no database, no API key and no build service to sign up for.
Working knowledge of React helps if you intend to change behaviour. Changing text, images, colours and the mock data needs no React at all; those live in plain files described below.
Install and run
Unzip the package and open the template folder in a terminal.
npm install
npm run dev
The site is now at localhost:3000. Edits appear without a reload.
Seeing the layout grid
While npm run dev is running, press Shift+G
to lay the column grid over any page — 4 columns on a phone, 8 on a
tablet, 12 on a desktop, the same grid the sections are built on — and
Shift+R for rulers. Drag a guide out of a ruler to
line something up; drag it back to remove it. None of this exists in a
production build.
Trying the presets
While npm run dev is running, the button in the bottom-right
corner opens the preset panel: light or dark mode, the brand colour, and
four presets — Original, Soft, Crisp and Editorial — each a type pairing
and a set of corners. Every pick is saved to preset.json, and
your build ships with it. A production build leaves the panel out; to
remove it for good, delete components/preset-panel and the
lines in app/layout.tsx that name it. The look in
preset.json stays.
Right to left
The panel's Right to left switch previews the whole site mirrored.
Set "direction": "rtl" in preset.json and
the build ships right to left. The copy stays English; a site written
in Arabic or Hebrew can delete the Right to left block at the end of
app/globals.css once the copy is translated.
Building for production
npm run build
npm start
npm install fails, check your Node version with
node -v first. An older major version is the cause nine times
out of ten.
Project structure
| Folder | What lives there |
|---|---|
app/ | One folder per route, plus layout.tsx (fonts, header metadata) and globals.css (every colour, radius and shadow) |
lib/data/ | The demo content: events, venues, organizers, orders, seat plans, people, photos, help articles. The files you will open most |
lib/site.ts | The site's name and address |
lib/format.ts | Currency, dates, times and units, in one place |
lib/nav.ts | The header's Explore menu, the mobile menu and the footer links |
components/ui/ | The UI kit: buttons, fields, selects, dialogs, tabs and the rest |
components/<page>/ | The sections of each page, by page: home/, events/, seats/, checkout/, organizer/ and so on |
components/site/ | What several pages share: header, footer, event cards, the demo store |
DESIGN.md | The design language, for you and for a coding agent |
Making it yours
1. The site's name and address
Open lib/site.ts. Change siteName by hand.
siteUrl finds itself on Vercel; on any other host set
NEXT_PUBLIC_SITE_URL to your address. The sitemap, every
canonical URL and the structured data read it.
2. The brand colour
In app/globals.css, change --primary,
--primary-ink and --primary-foreground in
the :root block and again in the .dark block,
then run npm run design so DESIGN.md agrees.
A colour or preset picked in the panel is saved to
preset.json and laid over those values.
3. The text and the demo data
Page copy sits in the section components under
components/. Events, prices, venues, organizers, orders and
people are typed arrays in lib/data/: edit a row and every
page that shows it changes. Figures such as the ticket limit or the
refund window are declared once there, so a change reaches every page
that prints them.
4. The photography
Photos load from Unsplash and Lummi through next/image,
listed by key in lib/data/photos.ts. Replace a URL there
to swap a photo everywhere it appears. To host your own, put the files
in public/ and point the entries at them; another remote
host goes into images.remotePatterns in
next.config.ts.
5. The fonts
Google Sans Flex sets the headings and Geist the body text, loaded with
next/font in app/layout.tsx and named in
app/globals.css as --font-heading and
--font-sans. The presets' faces load only when a preset
picks them.
6. Logo, contact details and footer
The logo is components/site/wordmark.tsx. Support hours
and reply times are in lib/data/support.ts, the company
story in lib/data/company.ts, and the footer's links in
lib/nav.ts.
Working with an AI coding agent
The template carries its design language as a file an agent reads:
DESIGN.md at the root holds the colours, type, corners and
motion — generated from app/globals.css by
npm run design — and the rules for using them. Point your
agent at it before asking for a new page, and it builds in the same
style.
Three ready-made skills sit in .claude/skills/:
build-page for a new page or section,
restyle for a new brand colour, font or corner, and
review-design to check a change against the rules. Claude
Code picks them up on its own; Cursor, Copilot and others read them
through AGENTS.md.
AGENTS.md at the root is the short guide for any coding
agent: what to set before deploying, the conventions a plausible edit
breaks first, where the demo data lives. Claude Code reads it through
the one-line CLAUDE.md beside it, so keep that file: add
your own instructions below its line rather than replacing it.
Before you launch
- The site address. On Vercel there is nothing to set. On any
other host, set
NEXT_PUBLIC_SITE_URL; left unset, the sitemap, canonical URLs and structured data point at a reservedexample.comaddress. - The name and logo.
siteNameinlib/site.tsand the wordmark incomponents/site/wordmark.tsx. - The organizer logos in
public/logos/are Logoipsum placeholders. Replace them with marks you have the right to use. - The photography is hotlinked from Unsplash and Lummi under their own licences. Check each image you keep, or swap in your own.
- The demo data. Every event, organizer, person, order, figure
and review in
lib/data/is invented. Replace it, or wire the pages to your API. - Forms and payments. Checkout, the contact form, the
newsletter and every organizer form succeed in the browser and send
nothing. Connect each to your backend and payment provider. The
checkout opens on a payment provider's published test card,
demoCardinlib/data/checkout.ts; empty it for a real deployment. - The second pages.
/home-2and/organizer-2are alternative layouts. Keep the one you prefer and delete the other folder and its links inlib/nav.ts. - The reference page.
/design-systemis for you; deleteapp/design-system/andcomponents/design-system/before launch if visitors should not see it.
Deploying
It is a standard Next.js application, so anything that hosts Next.js hosts this: Vercel, Netlify, Cloudflare, or your own Node server behind nginx.
On Vercel, push the folder to a Git repository and import it — the
defaults are correct and no environment variables are needed: the
sitemap and canonical URLs pick up the production domain, a custom one
included. Elsewhere, set NEXT_PUBLIC_SITE_URL to the
site's address, run npm run build and serve with
npm start under a process manager.
Licensing
What you may build with this template is set by the licence you bought it under — the one issued by the store you bought it from. Your receipt links to its terms; how many end products one purchase covers is the part worth reading twice.
Every font, image source, icon set and library that ships with or is
loaded by the template is listed with its own licence in
licensing/LICENSE.txt, next to this file. Read the section
on photography before you launch: some images are loaded from a remote
host for the demo and are not yours to keep.
Support
Questions, bugs and anything the documentation does not answer go to booliitheme@gmail.com, or through the item's page on the store you bought it from. Support covers the template as delivered — it does not cover customisation work, third-party services or hosting.
The release history is in licensing/CHANGELOG.txt. Updates
are free for the life of the item and appear wherever you downloaded it.
If this template saved you a week, a rating on the item page is how it reaches the next person.