Modules · Festival site per edition
Your festival deserves its own place on the web, but not its own build project. Every edition automatically gets a site on a subdomain, filled from the system.
A glimpse of this module
with sample data, liveFestival site per edition shares data with Crew & volunteers, Programme & stages and Tickets. Change one thing and they move with it.
Nineteen modules, one system. Change it here and it stays right everywhere.
What it does
name.festival.productions is live the moment your festival exists. Linking your own domain is possible too.
Line-up, times, location, frequently asked questions and the link to your ticket shop come straight from your festival data. Enter once, correct everywhere.
The sign-up form for crew and volunteers is on your site and flows straight into the scheduling system.
Colours, typefaces and imagery per festival. The framework is the same, the face is yours.
Tidy previews on social media, fast load time, multilingual if your audience calls for it.
A festival site is where visitors find your line-up, times, location and ticket link. For a recurring festival you want to be able to refresh that per edition without starting a new build project every time. The core idea is that the site always matches what is actually planned: if an act moves by half an hour, the site moves with it.
With festival.productions every edition automatically gets its own site on a subdomain, in the form name.festival.productions. Connecting your own domain is possible too. The content, the line-up, the running order, the frequently asked questions and the link to your ticket shop, comes straight from your festival data. You enter it once and it is correct everywhere: on the site, in the timetable and at the gate.
Note: this is the organiser side with a public festival site per edition, not a native visitor app with push notifications. The festival site is one part of festival.productions and shares its data with the rest of the system, from the programming to the crew sign ups.
Frequently asked questions
A festival site contains at least your line-up, performance times, location, practical info and a clear link to ticket sales. You can build it yourself in a website builder, but then you maintain the content separately from your organisation. With festival.productions every edition automatically gets a site on a subdomain that is filled from your festival data, so you do not enter anything twice.
The basics are line-up and timetable, date and location, ticket link, practical information and frequently asked questions. For recurring festivals a volunteer sign up form and a newsletter subscription often belong there too. In this system the line-up, times and FAQ come straight from the programming and the festival data, so they are always current.
The price depends on the design, the number of pages, multilingual support and whether you maintain it yourself or have it built. A recurring festival mainly pays in time, because every edition has to be updated again. With festival.productions a site per edition on a subdomain comes with the system, so there is no separate build project each year.
Yes. By default your site sits on name.festival.productions, but you can connect your own domain to it. That way you keep your own brand name in the address bar while the content still comes automatically from your festival data.
In this system you build the line-up and the running order once in the programming module. Publishing is then a switch: the site and the timetable immediately show the current names, times and stages. Change something and the site, timetable and internal production schedule all update in one motion.
No. Most festival apps are visitor apps with their own timetable, map and push notifications that you download from an app store. A festival site is a web page that anyone opens directly in the browser. festival.productions handles the organiser side plus a public festival site per edition, not a native visitor app.
Everything in one place
In festival.productions, Festival site per edition feeds straight into Crew & volunteers, Programme & stages and Tickets. You change it in one place and it stays right everywhere, from the budget to the event day.