Build a prototype of your film festival's website

A festival site, not a cinema site with a new logo. Your edition with its dates, a countdown to opening night, and a programme you can browse by day, by strand and by venue. Every film has its own page with its screenings, premieres and Q&As flagged. Single tickets go through a seat map to a confirmed booking.

Passes that behave like passes. Buy a festival pass, a five-film pass or a day pass, then use it on a screening: the credit is taken, the ticket is issued and the count goes down. That is the commerce model festivals actually run, and the part generic ticketing gets wrong.

Accreditation, guests and venues. A press, industry and guest accreditation form, a guests and jury page, and your venues with their rooms. Press and industry screenings exist in the back office and never appear on the public programme.

Behind the public site is a festival back office: an overview of tickets and passes sold by strand, venue and day; a schedule builder where you drag a film into a room and a time and it tells you when two screenings clash; pass sales and redemption; an accreditation queue with approve and reject; guests and hotel nights; the hidden industry programme; and a live sales view of the hour the programme drops.

All of it is a mock-up with generated figures, and every control says so when you press it. What is real is the shape — your strands, your venues, your currency and your language are already in it.

It reads what your site publishes. Plenty of festival sites load the programme with JavaScript from a ticketing widget, and then it cannot see your films; it fills the programme with festival-type world cinema instead and says so. If it cannot find your dates it guesses at your next edition and labels them as a guess. Venue names and addresses it cannot read are marked as samples.

None of that changes what the prototype is for: showing your team what your own festival looks like on Filmgrail, today, without a sales call.