Five updates that should not need a developer
Add a production, change the cast, move the dates, publish a news note, make a new page. That is the ordinary work of a theatre website.
A theatre website has a rhythm, and the rhythm is a season of small edits, repeated.
Add a new production. The title, the dates, the room, the short description, and the place to buy a ticket. This is how a season becomes visible.
Update the cast. Names change in rehearsal. A role is recast. The page the audience reads should match the programme in the foyer.
Change performance dates. An extra show, a cancelled Monday, a time that moved. The programme and the show page have to move together.
Publish a news article. An announcement, an interview, a note about access. The company already writes these. Putting them on the site should be part of the same job.
Create a new page. A visit page, a page for the youth company, a page for this year’s festival. The structure can stay familiar. The team should still be able to open a page and fill it.
These five are the work a marketing or communications person already owns. A developer is the right call when the system needs a kind of page it has never had. Tuesday’s cast change belongs with the people who already know the cast.
When those everyday tasks need a developer, the website is asking the company to staff a job the season creates every week. A platform built around shows, dates, people, venues, and news keeps that job inside the building.