FRAME 2026 Template: A Conference Site With Tickets
FRAME 2026 Template: A Conference Site With Tickets
FRAME 2026 is one of the 25 ready-made Zugo templates: an event site with a countdown, a speaker grid, a two day schedule, three ticket tiers, an FAQ and a signed in attendee area holding a badge, saved talks and account details. Cloning it costs no credits, and the rest happens through chat edits.
Below is what the file really contains, which parts of an event site earn their keep, how to move it to your own dates and line up, and the point at which you should stop and connect a real ticketing provider.
What is actually inside the FRAME template?
FRAME sits in the landing group, but it is closer to a small platform than a single page: the marketing side and the attendee side are two different products sharing a design. Everything is data driven, so speakers, sessions and tiers are lists you edit rather than blocks you rebuild.
| Screen | What it holds | The first thing people change |
|---|---|---|
| Main page | Countdown to the opening hour, eight speaker cards, two day schedule with tabs, three ticket tiers, FAQ, venue block | Dates, city, speakers, tier names and prices |
| Sign in | Email and password, keep me signed in, forgotten password, link to registration | Copy, then a real account system |
| Attendee area | Entry badge, saved talks, account details with pass type and order number | What the badge shows, which fields matter |
The schedule is a real timetable rather than a list of titles: each row carries a time, a session name, a speaker with their company, and a room, and breaks are marked as breaks. That last detail is what makes a programme readable, because an attendee scanning it needs to see where lunch sits.
The ticket section is built the way conference tickets are actually sold: an early tier with a deadline, a standard tier marked as most popular, and a team tier priced for several seats. The FAQ answers the questions people ask before booking travel, which is where an event site either closes the sale or loses it.
Who is this template the right start for?
The obvious fit is a single track conference, a one or two day format with a countable line up. Everything in the layout assumes a small deliberate programme, and the copy says so out loud rather than hiding it.
It transfers well to neighbouring formats: a workshop weekend, a community meetup series, a summit, a festival with a printed programme. The parts that carry are always the same three, a line up, a timetable and a paid pass, and only the vocabulary shifts.
It also works for internal events. A company offsite or an all hands with a schedule, speakers and a badge needs exactly this shape, minus the ticket tiers, and removing a section is cheaper than adding one. The wider version of the job is in building an event site with AI.
Where it stops fitting is scale and complexity. Five parallel tracks with a personal agenda builder, a call for papers with submissions and review, or a multi city tour with separate programmes are all real products rather than a page you edit.
How do you move it to your own event?
Work outward from the facts nobody can guess. Dates, city, venue and the countdown target are the spine, and every other edit reads better once they are right.
- Set the event: "rename it to Northbeam 2027, 12 and 13 March, at the Old Customs House in Bristol, and point the countdown at the opening hour".
- Replace the line up: "swap the eight speakers for these six, with name, role, company", pasted as a plain list. Fewer speakers is a fine outcome, the grid handles it.
- Rebuild the programme day by day: "day one is this timetable" with times, titles and rooms in one message per day. Splitting it by day keeps each edit reviewable.
- Fix the tiers: "three passes, student, standard and team of five, in dollars, with the early deadline at the end of January".
- Rewrite the FAQ to your own questions. Travel, accessibility, refunds and recordings are the four that actually get asked.
Do the schedule before the styling. A timetable edit changes how much vertical space each day needs, and colour work done before that is colour work done twice. A simple rebuild takes about a minute, so the loop stays fast enough to keep checking after each step.
What does adapting FRAME cost?
Cloning is free: a finished page is copied into your project without a model call, so previewing several event templates costs nothing at all. Credits start moving at the first edit.
| Action | Credits | Notes |
|---|---|---|
| Clone the template | none | Copy of a finished project, no AI |
| One chat edit | 3 | One day of programme, one tier, one section |
| Full rebuild | 6 | When starting the page over is cleaner |
| Multi page platform, first three pages | 12 | Separate pages for speakers, programme and venue |
| Each page after the first three | 3 | A sponsors page, a travel page |
| Hi-Fi edit | 6 | Double the standard mode |
| Hi-Fi build | 12 | Same factor |
Free gives 5 credits, enough for the clone plus one edit, which is enough to see your own event name on the countdown. Pro is $25 a month with 200 credits, around 66 edits, and Business is $99 a month with 800 credits. A conference with two programme days, six speakers and rewritten tiers usually lands between ten and eighteen edits, comfortably inside one Pro month.
What has to be connected before you can sell a pass?
The ticket section in the template is a price list. Choosing a tier highlights it and nothing else happens, which is exactly right for a demo and useless for a real event.
Stripe is the piece that turns it into a sale: one time payments for individual passes, and an invoice friendly path for the team tier your corporate buyers will ask about. Ask for it as its own edit, naming each tier and its price, so the checkout is wired to real products rather than to labels. The general shape of that step is in building with payments.
Supabase gives attendees an account, which is what makes the badge and the saved talks belong to a person instead of a browser. Without it, the attendee area is a screenshot with working buttons.
Then Resend for the confirmation email with the pass details, your own domain because an event on a subdomain reads as unofficial, and Google Analytics to see whether traffic reaches the tickets section at all. Publishing and pointing a domain is covered in how to publish.
Where does the template genuinely stop?
Three limits worth knowing before you promise a launch date to a sponsor.
There is no ticket inventory. Nothing counts remaining seats, closes a tier when it sells out, or stops two people buying the last place at once. Simple caps can be built, but if you are selling hundreds of passes an established ticketing provider handles the edge cases you have not thought of yet.
The badge is a graphic, not a scanning system. Real door control means a code that a scanner at the entrance can validate against a guest list, which is separate hardware and separate software. For a small event a printed list works better than pretending otherwise.
And a call for papers, sponsor management and personal agendas across parallel tracks are each their own product. Zugo will not replace a development team once an event platform gets that deep, though it will get a convincing first version in front of the people who have to approve it.
Where to start with your own edition
Open the gallery, find Frame under landings, and click through the preview, including the sign in and the attendee area. Because the clone is free, you can compare event templates for as long as you like before spending anything.
Then move in the order above: event facts, speakers, programme, tiers, FAQ, and only then payments and domain. Structure first and payment last is the sequence that avoids paying twice for the same screen.
You can open the template and start your own edition at zugo.dev. Free credits get the dates, the name and the countdown to your event, which is usually enough to show a co organiser and decide whether to keep going.