Yes. Add a lineup column as a nested JSON array of acts grouped by day and stage, then surface it through a list mapping that renders Friday-Saturday-Sunday columns with stage headings and set times. New waves of acts are appended to the array, no template change.

Create a second page group with urlPattern like /festivals/{slug}/day/{n}/ that reads the same database and filters the lineup array to a single day. Each per-day URL renders Friday alone or Saturday alone, with its own meta and OG card optimised for that specific day's headline set.

Yes. Each act object in the array carries name, stage, day, and set time. List mappings render them in stage order with set times next to each act. Updates from the production team flow through the sheet to every page on the next cache flush, even mid-festival when stages run late.

TBA slots are entries in the array with name set to "TBA". When the actual act is revealed in a later wave, edit the entry. The poster art and the per-day URL update on the next cache flush, with backlinks intact. There is no separate "wave" infrastructure required because the database is the source of truth.

Yes if you maintain a parallel artists feed. Run a third page group at /artists/{slug}/ keyed by artist slug. Within the festival lineup array, add an artistSlug field per act and use it in the list mapping to link each act in the grid to its artist page, building cross-link authority across the SEO surface.

SleekRank does not sell tickets. Add a ticket URL column at the festival level and map it to the CTA in the base page. For tier-based ticketing, add separate columns per tier and render them through selector mappings. The page routes fans to your existing platform, like DICE, Festicket, or AXS, with the festival slug appended for tracking.

Yes. Add a stage map image column and a downloadable PDF schedule column, then surface them via selector mappings on the base page. The PDF schedule can be re-uploaded each time it changes, but the live HTML lineup grid is the primary source for set times because it updates instantly.

The base page can group the array by time-slot rather than by stage, surfacing clashes naturally. Or add a clashFinder block that lists acts by hour across stages for each day. Both are list mappings against the same lineup array, so the festival organiser doesn't maintain a second source of truth for the clash view.