When we first got the proposed design for the Newleaftheatre.org site in 2004, the marketing team of the era was in absolute awe. We were sitting in the spacious, well-lit trendy “living room” of one of our company members’ friends design firm (won’t tell you which one – we’ve been lucky enough to have three such relationships in our eight-year history) and we were each handed this shiny binder with images of orange bevels, warm handwritten text, and black-and-white stills from our current production. It was SNAZZY. For a company that was tiny and had no money, this pro-bono design was the get of a lifetime. We still get comments, in a market five years older, about how great our site looks. That site has caught the attention of artists just landing in Chicago, and we get the privelage of working with them first… because we had a web presence that was simple and sleek and showed us off.
Cut back to 2004. I’m sitting there, trying to figure out the world of marketing as an artist, and I came to that meeting with a question. I was to be the webmaster once the site was rolling, and I wanted to be ready. I had been learning this neat new (to me) programming language called CSS, or Cascading Style Sheets.. The possibilities of CSS seemed to fit right in with such a sleek design – easy to read code meant that the site would be simple to update under many unforseen circumstances. For example, a vertical production photo instead of a horizontal one. I asked the question: “Would this site be coded in CSS?”
Sure, it may have been a rude and rube-ish question to ask a hot shot designer who just handed us the keys to a beautiful pro-bono design. And I felt that rush of guilt immediately, and I backed down.
And you know what? I’m STILL cleaning up and working around and limboing under that jerk’s code five years later. Look at it! Go to Newleaftheatre.org, click on “view source” and look at it! It’s a freaking mess! Table code every which way, embedded font tags that make the simplest updates cumbersome and confusing… The very definition of an unextensible site. Over the years – as I’ve learned more – I’ve slowly updated under-the-hood in little half-day bursts to allow for a database-driven site (which in turn compresses a half-day of updating the site everytime we put on a new show to about half an hour), and fancy things like photo montages, twitter integration. But the thing that prevents all these things from really gelling? Not enough time to massage and fix the shoddy programming that underpinned a beautiful site.
So, you know I love you. I don’t want you or your theater to have this fate. So here’s some tips and ‘gotchas’ to look for when your board and marketing department get a crackin’ for a new website.
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 Good-Fast-Cheap-(Pick 2)” rule applies. As much as I just bitched the dude out, I do think that getting an experienced designer on a pro-bono basis absolutely pays dividends over the long term. Pro-bono means that the designer – for once in their career working for the man – is allowed to play and push their own creative limits, so you can really end up with staggering work if you cultivate the right relationship. To that end – If you’re getting Good and Cheap (gotta have cheap, right?) DO NOT THINK THAT YOU CAN PUSH FOR FAST. Budget plenty of time to get the results you want with little investment. The designer has to take you and your deadlines seriously, but for instance – don’t fall into the trap of the ‘partial launch so that we can hit this deadline.’ This is just asking for trouble, because your developer will usually need to develop two working sites within the time frame that they would normally be building one. Two mediocre sites do not equal one good one. When you sacrifice good, you will burn them out, and then they will drop you like a hot tamale. Check in with them. Find out what makes them excited. Continue to engage their interests, and they’ll keep working with you – just like any collaborative artist.
3) I swear to god, no one does this, but it’s so much more important than getting the right the visual look of a site. When a process neglects Content Management training, designers tend to push their Content-Management-of-choice on you, the client. This allows them to fake you out a bit and get you off their back – when they’re on home turf most designers have great agility and can *appear* to provide all three pieces of the magic triangle: Good, Fast & Cheap! You Win!
Not so fast, Sonic the Hedgehog. Allow enough time in your timeline to make sure that you understand under-the-hood programming choices. You should budget time to have a rep from your company research & discuss the relative merits of each Content Management System (CMS) with the preference but without the bias of the designer/programmer. Some CMS’s that might be proposed:
– Dreamweaver / Text editing. Run away, already. Dreamweaver is an HTML tool, not a CMS, and updating the page will require HTML skill. That means crazy maintenance time and/or costs and a greater likelihood that your updates will break the page.
– Designer maintenance. Not a viable option for the theaters these days, and if you went pro-bono, it’s a laughable thought. The goal here is that the CMS should be easy enough to use that any company member can update the site – because at some point, marketing will be a burden.
– Joomla or Drupal. Perfectly servicable CMSs with built-in databases, though it can be confusing to some – including me, and I know five web languages. Try it out first. Tony will recommend Joomla every time. Tony, you’re a crazy person for this reason.
– WordPress, again with a built-in database. My flavor of choice because of its ease, ubiquity, and extensibility, but it needs some tweaking to wipe away the wordpress “look” and would also need considerable modifications to power say, ongoing box office functionality. I’m biased, too, remember. Again, try before you buy. We did quite a bit of this sort of tweaking with Dan Granata’s new net-home, Theatre That Works.
This post was (once again!) sponsored by Elizabeth Spreen at Ghost Light, who bought me a nice late-night mug of Genmai-cha. The toasted rice tea reminds me of Iwate, Japan. Sigh. Thanks (oh so belatedly), Elizabeth!
Buy Me a Coffee?