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 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.

Read

When 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.

Read

Waiting 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.

Read

The 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.

Read

Take 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.

Read

Two 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.

Read

Opening 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.

Read

Access 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.

Read

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.

Read

Search 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.

Read

The 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.

Read

You 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.

Read

The 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.

Read

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.

Read

The 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.

Read

A 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.

Read

The 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.

Read

Theatre websites already share a shape

Shows, a programme, people, venues, and news. Starting from those blocks is faster than starting from an empty page.

Read

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