Skip to content

Instructions.

How Admit is put together, and how to make it yours: the events, the colours and type, the motion, and what to keep.

Start here

Admit lists everything on in a city and sends each visitor to the place that sells the tickets. Every event, kind of night, venue, organiser and article is a CMS item: change the items and every page follows.

Four homepages come with it (Home, Home 2, Home 3, Home 4). Keep the one you like as Home and delete the rest, or keep them as landing pages. Every other page comes in the versions its menu lists, as in the React and HTML editions: What's On 1–3, Kind 1–2, Event 1, 2, 3 and 5, Venues 1–2, Venue 1–2, Articles 1–2, Article 1–2, Help 1–2, Put on an event 1–2 and Organiser 1–2. Version 1 of an event, kind, venue, organiser and article is its CMS template; the later versions are pages of their own. Their lists read the CMS as the first versions’ do: the rails, runs, boards and bills list your Events, the articles your Articles. Kind 2, Venue 2 and Organiser 2 list one kind’s, venue’s and organiser’s events (Music, Low Level, Night Shift): point that filter at your own item in the list’s Collection list settings. What’s on 2’s month, What’s on 3’s hours and Venues 2’s rooms to scale are drawn, not lists: change their words in place. Keep the ones you like and delete the rest.

Every value in the design is a variable: colours, type sizes, spacing, corners. Change a variable and every page changes with it.

Add an event

CMS → Events → New Event. Give it a name, a date and time, a photograph with its alt text, a kind, a venue and an organiser. The rest is optional.

In Running order write each line as the time in bold, then what happens; make the main act's line a quote and it turns red. Price note is the line under the price: "All-in", or "Second release, all-in" once an earlier release has sold out. Ticket on sale and Ticket on sale price are what the event's card prints on its stub: "Second release", "£28".

In an article, set a portrait photograph's alignment to Normal (it stands narrow, its caption beside it) and a landscape one to Full width (across the column, its caption below). Switch Latest on for the newest article only. A kind's On this month and Venues are the two figures at the top of its page; a venue's Article is A or An, the first word of the line under its name.

Ticket link is where Get tickets goes: your box office, your ticketing provider, or the venue's own page. Admit doesn't take payment itself, so any seller works.

Ticket state tells visitors how the night is going: On sale, Few left, Sold out, Free entry or On sale soon. Sold out swaps Get tickets for Join the waitlist, which goes to the Waitlist link.

Featured puts the event in the homepages' spotlight; Few left puts it in Going fast. Kinds, Venues and Organisers each have their own page listing their events.

Take event submissions

The Create an event page is a native Webflow form. Submissions arrive in Site settings → Forms and by email: read them, then add the event in the CMS. Nothing is published without you.

To change where submissions go, open Site settings → Forms → Form notifications. The Contact and newsletter forms work the same way.

Checkout, sign in and tickets

Checkout, Sign in and Your tickets are drawn as a ticketing service shows them to a fan: tickets held for ten minutes, paying, signing in with a code, and the tickets kept on a phone. Admit takes no payment and makes no accounts, so each page shows its first step, and its forms are native Webflow forms that send to Site settings → Forms like the others.

The other steps are in the page, hidden with the is-hidden class: on Checkout, Pay, Done, a refused card, free places and the hold running out; on Sign in, the code and the signed-in view; on Your tickets, the bookings themselves, sending one to a friend, passing them on, past tickets and the empty state. To work on one, select it in the Navigator, take is-hidden off while you edit, and put it back before you publish.

Never collect card numbers in a Webflow form. Checkout's payment step is there to show the design, not to take payments, and stays hidden. To sell, set each event's Ticket link to your ticketing provider (see Add an event), and use these pages as the look for its checkout and account pages, or delete them.

Colours and type

Open the Variables panel. Colour holds every colour by its job (Page, Text, Accent, Border…) and the brand's own under Brand: Seat is the red. Change Brand/Seat to change the red everywhere.

Colour's modes are the grounds a section can stand on: Poster (the paper), Hoarding, Seat, Blush and Oxblood. A section wears one through its class, and its text and buttons follow.

Type holds the faces, sizes, weights and line heights, with a mode for each breakpoint. Anton sets the display titles and Schibsted Grotesk the rest. To change a face, add it in Site settings → Fonts, then pick it in Type/Family.

Space and Shape hold spacing, corners and widths. Keep values in variables: a colour or size typed straight into a class won't follow the rest when the brand changes.

Components

The Navbar, Navbar Minimal, Footer, Button and Ways In are components: edit one and every page follows. The Navbar has five variants: Base, Over Hero (clear, for a page that opens on a photograph), and Oxblood, Hoarding and Poster, for a page whose header stands on that ground. Home 2 wears Navbar Minimal, the logo and Menu alone. Ways In holds the ways to reach a person, on Contact and Help 2.

A Button has a Label, a Link, Show Arrow and a Variant: Base (the red one, one per view), Large, Small, Ink (the second action), Pass (the yellow wristband, on red and black only) and Text (the underlined word). Change those in the right-hand panel rather than editing inside it.

The logo is an image in the Navbar and Footer: swap the asset to put your own in. The phone menu is inside the Navbar, so it changes with it.

Icons (SVG code)

The Admit mark drawn on the pages, the social icons in the Footer, the QR codes on the ring's tickets and the icons in the phone ticket's list are SVG code inside Embed elements. They take the colour of the text around them.

To change one, select its Embed and open its code (double-click it, or Settings → Open code editor). Paste your SVG in place of the old one, keep width="100%" and height="100%" so it fills its box, and write fill or stroke as currentColor so it follows the text. Keep aria-hidden="true" when the words beside it already say what it is. Save and close.

The social icons live in the Footer component: change them and their links there once, and every page follows. Leave the small filter inside the Navbar's tabs as it is: it gives the drop of ink its soft edge.

How to Edit GSAP Animations

The motion is GSAP custom code: GSAP with its ScrollTrigger, SplitText and ScrollTo plugins, all four switched on in Site settings → GSAP. It sits in Site settings → Custom code → Footer code as one short script for each part, each starting with a comment that names it, so one part can be changed or taken out without touching the rest. Every change the scripts make to the page is a GSAP call.

It plays what Interactions can't: the page gliding under the mouse wheel, the ring of tonight's nights on Home, the doors opening as you scroll on Home 4, the Navbar coming back when you scroll up, titles opening line by line, photographs uncovered as they arrive, and figures counting up. It also wipes open the Navbar's dropdowns, the phone menu and the questions on Help, Host, Fees and each event.

It also runs a drop of ink to the tab under the pointer; plays tonight's running order on Home 2 and pours its Menu over the screen; tilts the phone ticket on Home 2 and Home 4; lights Home 3's seats with a follow spot; opens a day or an article as you point at it on the homepages; lets a list's photograph follow the pointer (Home 2, Venues, each venue and kind); stands the venues as tall as they hold; peels the red off the price photograph under the pointer; moves Home's rail of posters with its arrows; shows the ticket a picker names on Home 3 and Home 4; spins Home 4's reels to a night for Pick a night for me; turns an organiser's Follow to Following; and, on a phone, raises an event's buy bar once its ticket has scrolled away.

The published page is already the finished page: the script adds motion and opens what opens. With the script removed, every title, photograph and figure still shows, but the dropdowns, the phone menu, Home 2's Menu and the questions stay shut, and the pickers, Pick a night for me and Follow stay as published — build them as Interactions first if you take it out. When a visitor asks for reduced motion, nothing moves. One part lives in a page of its own: What's on 2's day seats (Page settings → Custom code → Before </body> tag), GSAP too.

Element map

Each moving element is found by an attribute (Element settings → Custom attributes) or, for the Navbar, a class. Copy an attribute onto a new element and it moves too; remove it and the element stays as published.

  • the page (no attribute): it glides under the mouse wheel (GLIDE), on GSAP's Observer and ScrollTo; touch, keys and the scrollbar stay the browser's.
  • [data-reveal="lines"]: a title rises into place line by line.
  • [data-reveal="rise"]: a block rises into place; a photograph in it is uncovered from below.
  • [data-watch]: when an arrival plays, as its top reaches the reading line (ARRIVE.start, below).
  • [data-drift]: a big photograph drifts against the scroll.
  • [data-count]: a figure counts up to its value (with [data-from], down from that value).
  • [data-motion~="animate-paste"]: a snipe ("Last 60", "Latest") is pasted on as it arrives.
  • [data-motion~="animate-marquee"] and [data-marquee-pause]: a marquee's belt loops; its button pauses it.
  • [data-motion~="animate-pulse-quiet"]: the live dot breathes.
  • [data-js="in-the-round"] and [data-js="round"]: Home's ring of tonight's nights turns, and the front night is named under it.
  • [data-js="opening"] and [data-js="scrub-stage"]: Home 4's doors part as the page scrolls.
  • [data-js="read"]: photographs open out of a line of words as it is read.
  • header[data-js="site-header"]: the Navbar stays at the top of the screen, slides away on the way down and comes back on the way up.
  • [data-tab] with a dropdown, in the Navbar: its dropdown wipes open under the pointer or with focus; Escape shuts it.
  • button[data-menu]: the phone menu wipes open over the page.
  • button[aria-controls][data-i]: a question's answer opens, one at a time.
  • .ticket-picker_button[data-i] and .ticket-picker_wrap[data-i]: a picker shows the ticket it names (Home 3, Home 4).
  • button[data-pick]: Pick a night for me spins Home 4's reels to a night.
  • [data-js="follow"]: an organiser's Follow turns to Following and counts one more.
  • [data-js="running-order"]: Home 2's running order moves to the next night every 4.5 seconds.
  • [data-js="phone-tilt"]: the phone ticket tilts toward the pointer.
  • [data-js="follow-spot"]: Home 3's follow spot lights the seats.
  • [data-js="follow-photo"] and [data-follow-photo]: a row's photograph follows the pointer.
  • [data-pour], [data-pour-open] and [data-pour-close]: Home 2's Menu is poured over the screen in ink.
  • [data-tab] and [data-drop]: a drop of ink runs to the tab under the pointer.
  • [data-js="point-pick"]: pointing at a day or an article opens it.
  • [data-js="rail"] and button[data-step]: a rail's arrows move it a poster at a time.
  • [data-js="buy-bar"] and [data-buy-anchor]: on a phone, an event's buy bar rises once its ticket has scrolled away.
  • [data-skyline]: the venues stand as tall as they hold.
  • .price_layer: the price photograph's red wipes off from the left under the pointer, its own colours under it.
  • [data-js="month"] (What's on 2's own code): a day's seat shows that day's board.

Customizing key variables

Each script keeps its knobs in one settings object at its top (ARRIVE in Arrivals; NAVBAR, MENU, RING, DOORS, RUNNING and the rest in theirs). Times are in seconds.

const ARRIVE = { rise: 28, scale: 0.94, settle: 1.12, duration: 0.8, ease: "power3.out", stagger: 0.08, most: 5, start: "top 90%" };

Duration: to slow every arrival, raise duration in ARRIVE from 0.8 to 1.2. NAVBAR and MENU hold the Navbar's and the menus' own duration; RING.lap is one lap of Home's ring.

Delay: lines and blocks that arrive together set off ARRIVE.stagger apart. Raise it from 0.08 to 0.15 to space them further.

ScrollTrigger: ARRIVE.start is where every arrival starts. "top 90%" plays a block when its top is a tenth of the screen above the bottom; "top 75%" waits until it is a quarter of the way up. DOORS and READ hold where Home's doors and a read line start and end.

ease: "power3.out", // any GSAP ease by name: "power2.out", "expo.out", "none"

Ease: every settings object has its own. Write any GSAP ease by name; "power3.out" is the template's arrival, fast out with a soft settle.

<script> /* Peel · .price_layer: under the pointer the red wipes off from the left… */ gsap.matchMedia().add(…); </script>

To switch one part off, delete its script tag and everything in it: each starts with a comment naming the part and what it finds. The other knobs: NAVBAR.floatLogo is the logo's look while the Navbar floats, RUNNING.turn the seconds each night of Home 2's running order stays, TILT the phone ticket's tilt in degrees, SKYLINE.least how tall the smallest venue stands, POUR.back how far the links not pointed at step back, GLIDE.duration how long the page glides.

Removing GSAP animations

  1. Open Site settings → Custom code → Footer code.
  2. Delete the script tags and everything in them: all of them to take the motion out, or one to take out one part.
  3. Each script makes its own ScrollTriggers, so they go with it; none sit anywhere else. Then switch off ScrollTrigger, SplitText and ScrollTo in Site settings → GSAP, and delete What's on 2's own script (Page settings → Custom code).
  4. Save changes, then publish.
  5. What you'll see: titles, photographs and figures appear at once, as published, and nothing moves. The Navbar's dropdowns, the phone menu, Home 2's Menu and the questions stay shut, the pickers, Pick a night for me and Follow stay as published, and an event's buy bar stays out of sight: build those as Interactions first.

The Footer code holds 50,000 characters and the scripts take about 47,400 of them, so a new part goes in its page's own Custom code.

Before you publish

Replace the demo's name, email and social links in the Navbar, Footer and the Contact, About, Terms and Privacy pages. Admit and the events in it are made up.

Write each page's title and description in its Page settings, and set a social image. The Event, Article, Kind, Venue and Organiser templates take theirs from the CMS.

The Licenses page lists the fonts, photographs and libraries and what they allow. Keep it, or keep the credits wherever you list yours.