Settings that apply to the whole account rather than to one page. Only the super admin can change them — they are commercial terms, and they take effect on every workshop page at once.
How far ahead the first bookable date sits. The date picker on a workshop's reservation panel refuses anything earlier, and the page tells the visitor to ask about expedited options instead.
0 means a date can be booked for today. Saving stages the change as a draft, so the calendars change when you click Save changes.
How long before an event a booking can still change, and what a late change costs.
Three surfaces print these numbers — every workshop page, the FAQ, and/event-terms-and-conditions, which is now the site's single legal document. Saving stages them as a draft; click Save changes to publish.
Each ladder reads top to bottom, furthest from the event first. A tier runs from its own day count up to the one above it, and the last tier always runs to the event itself.
These apply to both formats. The wording around them — Event Subtotal, Notice, Maximum charge, Committed costs, No-shows, Force majeure, Agreement priority — is fixed text insrc/data/site-options.js and is not edited here.
What happens between the booking and the event, category by category — because the seven categories do not run on the same clock. Nothing ships to an in-person event; a kit has to be at every door days early.
This is what the workshop pages show. Every one of the 186 pages under/events/virtual and /events/in-person draws its "Process and timeline" section from the panel below, so an edit here changes the page on the next deploy and there is nowhere else the wording lives.
Which workshops each process covers is worked out from their tags, not listed by hand, so a workshop re-tagged in /admin/workshops moves to its new process on the next build. A workshop belongs to exactly one. Format wins first, then whether anything is delivered — a wine tasting that ships nothing runs the Nothing ships clock, not the tasting one — and then the activity, in the order the panels appear.
Three numbers write themselves, so a step can name them without going stale when they change:{deposit} becomes $250, {instantLabel} becomes the instant-booking window set above, and {addressDeadline} becomes 14. Type them with the braces and leave them alone.
The run of show during the event — the order the hour goes in, as a guest experiences it. It is the companion to the process and timeline above: that card covers booking through delivery, this one covers the event itself.
This is the "Agenda / Run of show" section on the workshop pages. Every workshop that states a duration draws it from the panels below, so an edit here changes the page on the next deploy and there is nowhere else the wording lives.
Six categories, not the seven above, and on purpose. The process files a workshop by whatships; an agenda has to file it by what the hour is like — a pasta kit's hour is a cooking hour, a paint kit's is not. A workshop takes the first panel whose tag it carries, andCooking & baking is the catch-all at the bottom.
Times are shares, not clock times. Each step takes a percentage of the session and the page turns that into the times a guest reads — so one agenda fits a 45-minute happy hour and a two-hour in-person event. The last step absorbs any rounding, so it always ends exactly on the stated duration.