Blog
Keeping a theatre website current
A cast change, a sold-out night, a new season. The words are usually ready. These notes are about what happens when publishing them still means a webmaster, and about the updates a theatre should be able to make on its own.
The poster QR code still opens last season
The poster is new. The code on it opens a homepage that still leads with a show that has closed, because the site was not part of the print job.
ReadThe building is closed. The website has not heard.
Snow, heat, a strike, a cancelled performance. The company knows before the doors would have opened. The homepage still invites people in.
ReadWorkshops have nowhere to live
A talk, a workshop, a late-night reading. The company is doing it. The website has no obvious place to say so, so the event lives in a caption.
ReadThe about page still names the last director
The artistic leadership changed. The staff list on the website did not. Visitors and artists meet a company that no longer works there.
ReadThe photograph is ready. The page still has a grey box.
The production images came back from the shoot. The show page still uses a placeholder, because putting a picture on the site is its own job.
ReadThe spreadsheet knows the dates. The website does not.
The company keeps the true calendar in a sheet. The public site is a second copy, updated when someone has time, so the two disagree.
ReadThe archive became a junk drawer
Old shows stay online with live ticket buttons and no sense of when they happened. The history of the company is there, and it is a mess.
ReadThe season PDF is still the real website
The brochure is finished, printed, and shared. The public site still shows last year, because publishing the season there is treated as a second job.
ReadThe partner venue’s website cannot be updated
The visit is confirmed. The company’s own channels say so. The host theatre’s site still lists a different week, because the guest cannot touch the page.
ReadThe phone number is three box offices ago
The desk moved. The hours changed. The visit page still prints a number nobody answers, because practical details were treated as a one-time setup.
ReadWhen the login leaves with someone
One person knows how the site works. When they leave, everyday updates become archaeology: shared passwords, old emails, and a freelancer nobody has called in a year.
ReadThe review came out. The show page never heard.
Opening night is written about the next morning. The sentence the company wants on the site sits in an email, while the page stays as it was before the show opened.
ReadWaiting on a webmaster for a one-line change
A sold-out night, a corrected name, a curtain time moved by half an hour. The words are ready. Publishing them still means writing to someone else and waiting.
ReadThe schools page still describes last year’s matinee
Teachers plan months ahead. A schools page with last year’s dates, prices, or contact note sends them elsewhere — or into a phone call the theatre then has to unwind.
ReadTake the webmaster off the website budget
Hosting is one bill. The person who has to publish every change is another. A theatre can stop paying for that second job.
ReadTwo venues, one website that names the wrong room
A second stage, a studio, a tour stop. The show is in the right building. The page still sends people to last year’s address or the main house foyer.
ReadOpening week is when the website falls behind
The understudy is on, the extra matinee is in, and the only person who can edit the site is in another job.
ReadAccess notes should not wait in a webmaster’s queue
A captioned performance, a content warning, a step-free route that changed. The company knows. The page still shows last month’s note.
ReadFive 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.
ReadSearch still sends people to last season
A visitor googles the theatre and lands on a closed show. The building has moved on. The page that ranks has not.
ReadThe show is sold out. The button still says get tickets.
A stale button is a small error with a public cost. It tells the audience the theatre is behind its own night.
ReadYou already wrote it for the newsletter
The news post is finished for the mailing list. Putting the same words on the website means another wait, so the site stays quieter than the inbox.
ReadThe audience arrives with five questions
What is on, when, where, who is involved, and how to get a ticket. A theatre website is doing its job when those answers are easy to find.
Read“Coming soon” is still there in March
A placeholder page was meant to last a week. The season moved on. The empty ticket link and the vague promise stayed.
ReadThe 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.
ReadThe cast list is still the first preview
Rehearsal changed the company. The programme in the foyer is right. The website still names the cast from the first announcement.
ReadA general-purpose website brings maintenance you did not ask for
WordPress and Drupal can run a theatre. They also bring hosting, updates, plugins, and security work that has nothing to do with the season.
ReadThe homepage became a museum
Last season’s photograph still leads the site. It looked strong in June. In October it tells visitors the company is living in the past.
ReadTheatre websites already share a shape
Shows, a programme, people, venues, and news. Starting from those blocks is faster than starting from an empty page.
ReadEarly 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