Event Website Template
Demo brand: Soltide Festival · Music & arts festival · 8 routes · Astro 7 + Tailwind 4
Live preview
The demo is a full desktop site. Open it in a new tab ↗
About this event website template
A complete site for a music and arts festival: eight built routes covering the bill, the six stages, tickets, getting there, and a journal.
Riviera poster modernism — azure, sunshine, cream and coral in flat blocks, set in Syne against Familjen Grotesk. The palette is the loud channel and it is doing all the work: flat colour, no gradients, no glow.
The mechanic is compositional rather than animated. All photography is held inside vintage-poster plate shapes — duotone inside arches — so every image on the site belongs to the same printed object. It is the discipline that stops a festival site turning into a photo dump, which is the failure mode of the entire category.
The 8 pages you get
- Home
/ - The poster, the pitch, the headline acts and the ticket close.
- The bill
/lineup/ - The full line-up — the page that decides whether someone buys.
- The six stages
/stages/ - What each stage is and who plays it. The page that makes a festival feel like a place rather than a list.
- Tickets
/tickets/ - Types, tiers and what is included, with a pre-filled mailto: enquiry path and a live tel:.
- Getting there
/getting-there/ - Travel, parking and camping. The practical page that prevents most of the support email.
- The Journal
/blog/ - A wired content collection — add an .mdx file and it appears here and in the sitemap.
- One worked article
/blog/example-post/ - Why we print nine thousand passes by hand — a long-form piece carrying the full editorial component set.
- 404
/404 - Designed, not default. Keeps the navigation.
What is in the build
- Flat Riviera-poster colour — four blocks, no gradients, no glow, no shadow
- All photography held inside vintage plate compositions as duotone within arch shapes, applied as a rule to every image
- A stages route, which is what gives a festival site somewhere to put atmosphere without diluting the line-up page
- A getting-there route covering travel, parking and camping — the page that absorbs most of a festival’s inbound questions
- Syne with Familjen Grotesk, both self-hosted
- A pre-filled mailto: ticket enquiry path and a live tel:, so the site works before any ticketing integration exists
- Vitest and Playwright suites included in the repository
The design decision
Every template in this catalog is loud in exactly one channel and deliberately quiet in the other three. That single rule is what stops 65 different worlds reading as one design system in different paint.
- The world
- Riviera poster modernism. Azure, sunshine, cream and coral in flat blocks.
- The mechanic
- Vintage-poster plate compositions, with all photography held inside the shapes.
- Loud channel
- Palette
- Imagery. Duotone inside arch shapes
- Type & palette
- Syne · Familjen Grotesk
-
#f4e9cf#172733#e8624a
Who it is for
Built for music and arts festivals, multi-day events, conferences with a personality, and cultural programmes. It suits an event that sells on atmosphere and identity rather than on a speaker grid. For a single venue taking bookings year-round, the event-location build is the right one instead.
Under the hood
- Astro 7 · static output, zero client framework
- Tailwind 4 · one @theme block holds the palette
- MDX content collections for the blog
- GSAP + Lenis for the scroll work, reduced-motion aware
- Self-hosted woff2 — no Google Fonts request
- Sitemap, canonicals and per-route meta wired
- Vitest + Playwright suites in the repository
- Zero third-party requests · strict CSP-ready
How to get started
- 01 Accept the repository invite and clone it.
- 02 Run
npm install, thennpm run dev. - 03 Replace the content in
src/data/with your own — that is where the brand, the copy and every list live. - 04 Swap the images in
public/images/and the palette in the@themeblock. - 05 Run
npm run buildand deploydist/anywhere static.
Questions
Does it connect to a ticketing platform?
Not out of the box, and deliberately — every festival already has a ticketing provider and hard-wiring one in would be a liability. The tickets page presents the tiers and hands off to whatever URL you give it; a pre-filled mailto: path works in the meantime.
Can I use it for a conference?
Yes. The bill becomes the programme, the stages become tracks or rooms, and the getting-there page does the same job. The flat-poster register is the question — it reads as culture rather than as corporate.
Why hold every photo inside a shape?
Because festival sites collapse into a photo dump otherwise. Holding every image inside the same plate composition means a hundred mixed-quality press shots still read as one designed object.
What exactly do I get for $49?
Access to a private GitHub repository holding the complete Astro source of this template — every route you see in the preview, the content model, the images and the tests. Updates arrive in that same repository.
How many sites can I build with one licence?
As many as you like, for yourself or for clients. The licence is per buyer, not per project. The one thing you may not do is resell or redistribute the source as a template, theme or starter kit.
Do I need to know Astro?
It helps, but the common case is editing content and colour. Content lives in typed objects under src/data, colour lives in one @theme block, and npm run dev shows the result. Deploying is a static folder — Cloudflare Pages, Netlify and Vercel all take it as-is.
Is anything loaded from a third party?
No. Fonts are self-hosted woff2, there is no analytics, no tag manager, no CDN script and no external CSS. The build ships static HTML under a strict Content-Security-Policy.
