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.
Most theatres end up on a general-purpose platform. WordPress and Drupal are the usual ones. They are capable. They also assume someone will look after them as software, as well as a programme of shows.
That care has a shape. Hosting has to stay up. The core software has to be updated. Plugins have to be updated, and sometimes they disagree with each other after an update. Accounts have to be limited, because a flexible admin can do damage. Security becomes a task with its own calendar. None of this is the production. All of it sits with the theatre, or with the webmaster the theatre pays so the theatre does not have to sit with it.
A small company feels this as a standing worry. The site works, until an update is overdue and nobody is sure who is meant to press it. A form plugin asks for a licence. A login is shared because creating a proper account means calling the person who set the site up three years ago.
The worry steals attention from the season. Someone is always half-waiting for the next break: a white screen after an update, a spam flood through a contact form, a backup that was never tested.
A platform made for theatres can take that layer back. Hosting, updates, and security belong to running the product. The company keeps the part that is actually theatrical: the shows, the dates, the people, the news.
The maintenance the season never asked for stops being a second job. The website stops feeling like software the company happened to inherit, and starts feeling like a place to publish the work.