Introducing: TheaterCalculus™
Right before my summer teaching gig, I threw out a brief tease on twitter about a web project I was working on (the brand new BackStage Theater Company website and blog) and what it means, okay, I’ll say it, for the future of content-driven websites for small theater companies.
What’s wrong with how theaters do things now, you ask? Well, it’s too much work, frankly, for mixed and muddled results. Traditionally, even simple web features for organizing production information have required a kind of wonky content management system or database to allow non-tech-savvy company members to update the website without breaking it in the process. In practice, however, without a self-explanatory one-stop-shop in place (that doesn’t require knowledge of HTML, FTP, Photoshop, and MySQL) the burden of updating that kind of site inevitably falls to the single person who created or assumes responsibility for the site, not the people that the site represents. As a result, the solutions I’ve seen out there (that don’t require keeping a high-powered design firm on retainer) fall into two camps of despair. Some are traditional, static sites that are updated irregularly and do not evolve into the waters of web 2.0 because of the high time cost of making changes. Others are entirely built on the read-it-now-or-forget-about-it blog model and sacrifice long-term infrastructure and the accrual of a body of work for the immediacy of now.
You know who you are, and it wasn’t your fault.
Both approaches need a way to talk to each other, so that the catalogue of old wisdom – past productions and company history – has a place to talk to the new vibrancy of what is exciting today and next week. Our entire world feels like it’s doing this right now, which is why you’re getting all these young hipsters digging into the history of the depression, WPA and CCC right now.
I’ll get into the technical details in later posts (you know, so you can steal the idea for yourself, or use it to convince your board to hire me and my merry band of outlaw graphic designers, marketers, and hackers) but for now, I’m going to focus on the features of something new I developed with the help of the < a href="http://backstagetheatrecompany.org">BackStage project, something I think is a winning equation:
Wordpress + Flutter + TheaterCalculus™ = A great content management system for your theater or personal portfolio.
Wordpress – you’ve heard of this, perhaps? It’s arguably the most extensible blogging platform out there, with an active open-source community that creates bajillions of plugins that fill 95% of any arts company’s web presence needs, like:
- Self-hosting a website
- Customizable themes that allow for completely self-branded sites
- A ‘pages’ infrastructure that extends wordpress beyond the features of a blog and allows all web content to be editable.
- Most-used plugins do everything from protecting blog comments from spam, to Search Engine Optimization, to integrating your Constant Contact and Google Analytics accounts with your website.
Flutter – Flutter is a new and very promising plugin for Wordpress that extends the ‘pages’ and ‘posts’ functionality of wordpress to provide some powerful and more importantly, easy-to-use and easy-to-update database functionality. What does that mean for you? Well, in the case of BackStage, we’ve added two sections to the wordpress sidebar here that are for “Shows” and “Company”. Each one leads to a standardized form that contains all the little bits of knowledge – the schema – that a company needs to decide and collect for each production along its life cycle. Because the form is powered by wordpress, adding a show to the site is just like filling out a blog post. Because the form is more complex than a blog post, with more fields, the show data can be calculated and presented in a unified way over the long term – and even allow you to change the way the data is presented later without re-editing 75,000 blog posts. Flutter also comes bundled with some awesome features.
- Powerful image management, including automatic thumbnail generation, caching and cropping
- Edit in place functionality (this has got to be my favorite – don’t have a ton of time but noticed a copy error? if you’re logged in, just click on the text – on the site – edit, and hit save.
TheaterCalculus™ – Yup. This is the part I’ve cooked up – a Wordpress theme mix-in that does a lot of the repetitive tasks of maintaining a theater website. Based on the Chicago Theatre Database’s flexible and comprehensive database schema – which we derived from production data from over 1,000 shows and 300 companies – I created a series of à la carte Flutter forms and adapted the logic from several theater company websites that can be adapted to fit a large number of applications. Basically, this is the brain that helps the website follow along with how theaters work and helps automate some of the more repetitive website-updates.
- Enter three critical dates into the show form – Opening Night, Closing Night, and Extension Closing – and the website will calculate clear and helpful language based on the current date – “Opening in November!”, “Now Open!”, “Closing Soon,” and “Extended through March 29!”. Better yet, shows that close can move themselves over to the past productions page and off the home page
- Review / pullquote, photo, video, and cast & crew bio forms helps keep production assets organized and connected to their sources. As marketing strategies tend towards cross-promotion, having a form that reminds you to enter your cast’s portfolio websites – and everything else you need to capture to promote your work – is a nice tool to have in the kit.
- Like any database-driven site, there’s an advantage in being able to display the same information in multiple contexts throughout the site – say, a tagline of a show. If there’s an error in the tagline, static sites required you to update four or five pages, which caused even more errors. By having all show info in one place, the site does the work of distributing it according to your marketing and web usability strategy.
There’s too much detail to go into in a single post – this has been a system I’ve been working on for over six months or three years, depending on how you measure the amount of time I’ve been thinking about the perfect CMS for theater. So I’ll be coming back to TheaterCalculus as things develop. I’ll be launching a few other theater websites (companies and individual portfolios) in the coming weeks using it as the underlying architecture, and so hopefully we’ll all be able to see just how flexible it can be.
This post provided to you by BackStage Theatre Company, naturally, and also sound designer John Leonard, who was nice enough to buy me a coffee even after I stole his idea from a wiki and wrote about it. If it’s the discovery I think it is, I’m going to need to buy him many, many, many, many coffees laced with some nice single malt.


1) Be very careful with conflating the identity of a graphic designer and a programmer / web developer. It is actually rare to get both in the same person, and boards tend to like designers but forget the programmer. (though now that’s starting to shift: Social media means there’s now a primary focus on web developers — but everyone still assumes that they also design, which many of them don’t) To really confuse the issue, designers also often think they can program (you know I love you guys), and programmers often think they can design (you’re my peeps). If someone says they are both, look at both sides of their portfolio. You need BOTH when you’re creating an online identity, but given the realities of long-term theater budgets, I’d argue you MUST have a good programmer or you will be fighting bad programming decisions for the life of the site, and that will cost you in time and missed opportunities. You also want to make sure that in addition to submitting a nice proposal (ooh! It’s velo-bound!) and coming in under budget and on time, your designer and programmer are hearing you and thinking creatively about how to translate the identity of your company into both a functionality (programming) and a look (design). It’s the same thing as theater, and board-types from the corporate world forget that when they put on arts marketing hats. (Don’t get me started with the corporate world and web presences – they know they need one and that theaters are bad at creating them but 90% of them don’t know how to achieve that on a granular level.) You know what designer/director trust feels like in your company, and you know what a designer who can’t execute their ideas looks like. And what do you do when they design beautifully but can’t execute? You hire them a technician – an ME, a sound engineer, a Technical Director. Same theory applies here.
2) The
So about those deductions. I use my debit card almost all year long rather than cash. It’s really annoying for splitting the bill, but I find that getting a receipt for everything is both a good budget reminder and takes care of my paperwork for me. I sort and file these receipts all year long into deductible and non-deductible expenses in a little coupon file like this one, one for each year. Best part about the folder? It’s a deductible office expense. I also keep track of my budgets, expenses, and anticipated freelancing income using the cheap and pretty useful online software 




Oh yeah… And there’s some