# Theatre.show > Theatre.show is a website builder for theatres. A company publishes shows, dates, cast, and news itself, without a webmaster for everyday changes. Theatre.show is in development. This domain is the product introduction, not a theatre's own website. There is no public price and no customer login here. The introduction is published in eight languages. Those pages say the same thing. The blog is English only. Links below are Markdown copies of the HTML pages. Fetch one file when that is enough. Search engines use robots.txt and sitemap.xml at the site root. Those list the HTML pages. This file lists the Markdown copies. ## Languages - [English](https://beta.theatre.show/en/index.md): A theatre website builder for publishing shows, dates, cast, and news yourself, without a webmaster for everyday changes. - [中文](https://beta.theatre.show/zh/index.md): 专为剧院打造的网站搭建工具。自行发布剧目、档期、演员和新闻,不必再把每次更新交给网站管理员。 - [Español](https://beta.theatre.show/es/index.md): Crea y actualiza la web de tu teatro sin webmaster. Publica obras, fechas, elenco y noticias tú mismo. - [हिन्दी](https://beta.theatre.show/hi/index.md): थिएटर वेबसाइट बिल्डर जिससे टीम खुद शो, तारीखें, कलाकार और समाचार प्रकाशित करे, बिना वेबमास्टर के। - [Français](https://beta.theatre.show/fr/index.md): Créez le site de votre théâtre et publiez spectacles, dates, distribution et actualités sans webmaster. - [العربية](https://beta.theatre.show/ar/index.md): أنشئ موقع المسرح وحدّثه بنفسك. انشر العروض والمواعيد وطاقم العمل والأخبار من دون مدير موقع. - [Português](https://beta.theatre.show/pt/index.md): Crie e atualize o site do seu teatro sem webmaster. Publique espetáculos, datas, elenco e notícias. - [Deutsch](https://beta.theatre.show/de/index.md): Baukasten für die Theaterwebsite. Vorstellungen, Termine, Besetzung und Neuigkeiten selbst veröffentlichen, ohne Webmaster. ## Blog - [Keeping a theatre website current](https://beta.theatre.show/blog/index.md): English notes on theatre websites and the work of publishing them without a webmaster. - [The poster QR code still opens last season](https://beta.theatre.show/blog/the-poster-qr-code-is-last-season/index.md): 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. - [The building is closed. The website has not heard.](https://beta.theatre.show/blog/the-building-is-closed-the-site-is-not/index.md): Snow, heat, a strike, a cancelled performance. The company knows before the doors would have opened. The homepage still invites people in. - [Workshops have nowhere to live](https://beta.theatre.show/blog/workshops-have-nowhere-to-live/index.md): 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. - [The about page still names the last director](https://beta.theatre.show/blog/the-about-page-names-the-last-director/index.md): The artistic leadership changed. The staff list on the website did not. Visitors and artists meet a company that no longer works there. - [The photograph is ready. The page still has a grey box.](https://beta.theatre.show/blog/the-photograph-is-ready/index.md): 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. - [The spreadsheet knows the dates. The website does not.](https://beta.theatre.show/blog/the-spreadsheet-knows-the-dates/index.md): 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. - [The archive became a junk drawer](https://beta.theatre.show/blog/the-archive-is-a-junk-drawer/index.md): 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. - [The season PDF is still the real website](https://beta.theatre.show/blog/the-pdf-is-still-the-website/index.md): 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. - [The partner venue’s website cannot be updated](https://beta.theatre.show/blog/the-partner-venue-cannot-be-updated/index.md): 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. - [The phone number is three box offices ago](https://beta.theatre.show/blog/the-phone-number-is-three-box-offices-ago/index.md): 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. - [When the login leaves with someone](https://beta.theatre.show/blog/when-the-login-leaves-with-someone/index.md): 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. - [The review came out. The show page never heard.](https://beta.theatre.show/blog/the-review-never-reaches-the-page/index.md): 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. - [Waiting on a webmaster for a one-line change](https://beta.theatre.show/blog/waiting-on-the-webmaster/index.md): 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. - [The schools page still describes last year’s matinee](https://beta.theatre.show/blog/a-schools-page-from-last-year/index.md): 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. - [Take the webmaster off the website budget](https://beta.theatre.show/blog/the-webmaster-line/index.md): Hosting is one bill. The person who has to publish every change is another. A theatre can stop paying for that second job. - [Two venues, one website that names the wrong room](https://beta.theatre.show/blog/two-venues-one-stale-site/index.md): 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. - [Opening week is when the website falls behind](https://beta.theatre.show/blog/opening-week/index.md): The understudy is on, the extra matinee is in, and the only person who can edit the site is in another job. - [Access notes should not wait in a webmaster’s queue](https://beta.theatre.show/blog/access-notes-waiting-in-a-queue/index.md): A captioned performance, a content warning, a step-free route that changed. The company knows. The page still shows last month’s note. - [Five updates that should not need a developer](https://beta.theatre.show/blog/five-updates-you-can-publish/index.md): 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. - [Search still sends people to last season](https://beta.theatre.show/blog/search-still-shows-last-season/index.md): A visitor googles the theatre and lands on a closed show. The building has moved on. The page that ranks has not. - [The show is sold out. The button still says get tickets.](https://beta.theatre.show/blog/the-button-still-says-get-tickets/index.md): A stale button is a small error with a public cost. It tells the audience the theatre is behind its own night. - [You already wrote it for the newsletter](https://beta.theatre.show/blog/written-twice-newsletter-and-site/index.md): 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. - [The audience arrives with five questions](https://beta.theatre.show/blog/five-questions-from-the-audience/index.md): 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. - [“Coming soon” is still there in March](https://beta.theatre.show/blog/coming-soon-never-left/index.md): A placeholder page was meant to last a week. The season moved on. The empty ticket link and the vague promise stayed. - [The season is ready. The website still shows last year.](https://beta.theatre.show/blog/the-season-is-ready-the-website-is-not/index.md): 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. - [The cast list is still the first preview](https://beta.theatre.show/blog/people-pages-that-never-catch-up/index.md): Rehearsal changed the company. The programme in the foyer is right. The website still names the cast from the first announcement. - [A general-purpose website brings maintenance you did not ask for](https://beta.theatre.show/blog/maintenance-you-did-not-ask-for/index.md): WordPress and Drupal can run a theatre. They also bring hosting, updates, plugins, and security work that has nothing to do with the season. - [The homepage became a museum](https://beta.theatre.show/blog/homepage-as-a-museum/index.md): 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. - [Theatre websites already share a shape](https://beta.theatre.show/blog/theatre-websites-share-a-shape/index.md): Shows, a programme, people, venues, and news. Starting from those blocks is faster than starting from an empty page. ## Optional - [Full text](https://beta.theatre.show/llms-full.txt): Every language page and every blog post in one file. Use this only when a single page is not enough.