The season is ready. The website still shows last year.

The brochure has gone to print. The homepage still leads with a show that closed in June, because updating the site is a project of its own.

Season announcement gathers the usual problem into one week. The titles are chosen. The dates are argued through. The brochure is at the printer, the press release is drafted, and the company wants the homepage to change on the morning they tell the public.

On a lot of theatre websites, that morning depends on a webmaster. The new shows are a batch of pages. Each one needs a title, a picture, a date range, a room, and a way to join a list or buy a ticket. If the only person who can assemble that is outside the company, the announcement waits on their calendar. Or the press goes out, and the site catches up next week, still leading with a show from June.

The audience notices the gap. They search the theatre after they see the poster. They find last season. They wonder if the new work is real yet.

Internal teams notice too. Development wants the site to match the brochure they signed off. Marketing wants one source of truth. Instead there are two calendars: the printed one and the live one, drifting apart until someone pays to reconcile them.

The team that built the season already has the information. Publishing it should be part of the announcement, in the same week, by the same people.

A website that can take a production, a date, and a ticket link makes the season launch a publishing task. It stops being a second project that starts when the brochure is already in the post.

All posts

Early access

Theatre.show is in development.

We are building the first version now. Join the early access list to hear when it is ready and follow the development of the platform.

Join the early access list