The Ugly Website Roundup

No, this isn’t an official installment in the 2011 Orchestra Website Reviews, instead, it’s a recap of the Your Website is Ugly! session from the National Arts Marketing Project Conference (#NAMPC) in Louisville on the benefits of open source software and how it’s changing the business of web development. But I wanted to take some time to examine a few additional items that didn’t make it into the session.

Session attendees 10 minutes before the session began. They were an inquisitive, engaged, and upbeat group with a terrific stream of questions!

Overall, the session was a real hit with attendees and I’m grateful to have had the opportunity to work with Ceci Dadisman, Kimberly Clark, and David Dombrosky The four of us covered a great deal of ground and you can find all of our respective PowerPoint presentation slides at the conference website (thank you Americans for the Arts!):

We had a terrific turnout of very inquisitive attendees, most of which were loaded with questions and I don’t think we lost anyone once the session started. There was a marvelous Twitter discussion going on via #uglywebsites but unfortunately, and at the time this article was published, Twitter seems to have banished the entire thread to hashtag purgatory as it is nowhere to be found. It’s a real shame as it provided a very good overview of what we discussed alongside unfiltered attendee reaction.

The Open Source Review

Just to make sure we’re all on the same page with regard to understanding what open source is, here’s a good working definition from

Open source is a development method for software that harnesses the power of distributed peer review and transparency of process. The promise of open source is better quality, higher reliability, more flexibility, lower cost, and an end to predatory vendor lock-in.

Be sure to check out David Dombrosky’s handout for a review of the open source options we covered in the session but for the most part, WordPress emerged as the clear favorite among panelists, including me, and a number of attendees.

Two Quick Definitions

In order to make a good bit of the following info easier to understand, it will help if you know the difference between your website’s frontend and backend:

  • Frontend: this is the part of your website that end users, i.e. visitors, interact.
  • Backend: This is the interface used to create and manage content; typically accomplished in most contemporary systems via a content management system.

What Open Source Can Do

Talking with one of the session attendees later that afternoon. Photo: Frankie Steele for Americans for the Arts

Although this section deserves an entire series of articles, we’re going to look at some of the most important benefits and keep it short and sweet (which means list form).

  • Most come with a content management systems (CMS) allow users to create and edit basic content through a point and click interface (meaning, you don’t need to know HTML or any other sort of code). Some content management systems are better than others while certain open source platforms strive to refine the CMS to the point where the point and click interface allows users to accomplish increasingly complex tasks.
  • They’re free! That’s undoubtedly a good thing but you still have to pay for hosting, know how to install it, set it up, and learn how to use it, which brings us to the next point.
  • There are a growing number of professionals out there who specialize in open source programming to help you get more out the platform you select. Having said that, they rarely have any expertise or understanding of issues unique to PAOs so don’t expect them to provide anything beyond technical support (and be prepared to spend extra time, and therefore money, to get past the miscommunication curve).
  • They’re extensible; meaning they play nice with other software programs. Granted, some platforms do this much better than others but they all pretty much have some sort of modular plugin or add-on capability.

What Open Source Can’t Do

Even with the substantial improvements over the past year in both free and premium theme CMS admin panels mentioned above, the one thing performing arts organizations (PAO) will still have difficulty dealing with is event management. Granted, this is the very same area where most custom tailored solutions fail but it’s fair to point out that open source is not going to make this task any easier.

Case in point, a number of the US and Canadian orchestras in the 2011 Orchestra Website Review which built their sites atop open source racked up low scores in sub categories which examined event management issues, such as event index pages (calendars and lists), event details pages, landing page event persuasion triggers, etc.

This happened even though most of those organizations used some sort of existing event management plugin solution (the reviews turned up both free and fee based solutions). But this wasn’t because those solutions aren’t any good; rather, they aren’t designed to accommodate the very unique sets of requirements that accompany POA event management and display.

Keeping with the short and sweet motif, here are a few content management and design points related to event management that you need to walk away with to help understand why this is such an issue (especially when talking to any developer about this issue):

  • Multiple occurrences of the same event on non-sequential days and times.
  • PAO events don’t have fixed end times for most events.
  • Many PAOs don’t control which box office solution they have to use.
  • Automatic sync of event management info throughout various areas of the site along with unique event index display needs.

What ends up happening more often than not for groups that use open source solutions with an inadequate event management system is they trade one set of traditional problems (for example, lack of direct content management) for a set of new problems (an event management system that creates more work than it was intended to solve) all of which lead to a place where managing your website content becomes a major pain in the neck.

To provide some frame of reference as to how big of a deal all of this is, consider this: designing and programming the Venture Platform’s event management component comprised the lion’s share of resources (both time and treasure). Likewise, it comprises the bulk of regular updates and maintenance work in order to follow through on a system that only requires users to create/edit event information with point and click simplicity from a single admin panel that can sync all of the respective data with all frontend uses, such as index and event details pages, calendars, upcoming events widgets, etc.

In the end, event management is an enormous task and there’s no simple solution out there in open source land that can turn it into a simple task (avoid the temptation to use any of the existing free or fee based plugins and add-ons).

Why Open Source Matters

During the Your Website is Ugly! session, I took a moment to impart to the attendees why open source not only matters but why we were making such a big deal out of it. In short, the impact of open source on the development community is nothing short of the impact Henry Ford’s assembly line had on the automotive industry.

Think of it like this; the workers used by Ford had to maintain very specific skill sets which were just as valuable on the assembly line as they were in the previous model. Programmers and designers of today are no different; their hourly costs are no different when using open source but since open source provides a platform (i.e. the assembly line component) that reduces a considerable amount of time in the overall development process, this should have a substantial impact on lowering overall development costs.

PAOs should benefit by getting a much bigger bang for their buck (although they do need to be on guard against emerging predatory practices). What’s exciting in all of this is we’re only in the heady beginning stages and we have yet to see just how much impact all of this is going to have on how PAOs interact with their audiences, improve administrative efficiency, and increase marketing performance.

As for now, expect to hear some contradictory advice coming from various voices within the development community, especially when you begin collecting proposals for your website development projects.


Open source is terrific. Period. It’s a powerful platform that can provide a stable foundation to build just about anything you need. Only the largest of budget groups with extremely unique requirements will need to look at solutions that aren’t built on top of open source (although that gap is narrowing on a monthly basis as open source continues to evolve).

Every POA should consider using open source regardless of whether you need custom development and/or outside technical support and training. So if you want to reduce the likelihood of producing an ugly website (frontend and backend) while retaining your unique branded identity, then open source is a comparatively low risk investment. the only real drawback is the lack of acceptable event management tools (but the same is true for custom designed solutions so there’s no added value by going in that direction).

We’ll begin diving into some of these issues in greater detail in subsequent articles but in the meantime, send in your open source questions and I’ll provide the answers. Keep in mind everyone approaches these issues from different points in the learning curve so there really is no such thing as a stupid question; likewise, feel free to revel in geek-speak and technical minutia. Either way, don’t be shy!

About Drew McManus

"I hear that every time you show up to work with an orchestra, people get fired." Those were the first words out of an executive's mouth after her board chair introduced us. That executive is now a dear colleague and friend but the day that consulting contract began with her orchestra, she was convinced I was a hatchet-man brought in by the board to clean house.

I understand where the trepidation comes from as a great deal of my consulting and technology provider work for arts organizations involves due diligence, separating fact from fiction, interpreting spin, as well as performance review and oversight. So yes, sometimes that work results in one or two individuals "aggressively embracing career change" but far more often than not, it reinforces and clarifies exactly what works and why.

In short, it doesn't matter if you know where all the bodies are buried if you can't keep your own clients out of the ground, and I'm fortunate enough to say that for more than 15 years, I've done exactly that for groups of all budget size from Qatar to Kathmandu.

For fun, I write a daily blog about the orchestra business, provide a platform for arts insiders to speak their mind, keep track of what people in this business get paid, help write a satirical cartoon about orchestra life, hack the arts, and love a good coffee drink.

Related Posts

0 thoughts on “The Ugly Website Roundup”

    • No arguments there, analyzing ugly websites (frontend and backend) would have been a fun and useful exercise but it probably wasn’t the ideal option since most folks required the sort of in-depth review of open source options etc.

      But you always have the orchestra website reviews and don’t forget that they included a homepage gallery for the US and Canadian reviews this year.

  1. Drew-

    Other than the event management issue, were there other common problems people seemed to have? Particularly, I was wondering if there were things that one might assume were common knowledge but continually popped up as “how do I do…” type questions

    • I can only provide observational knowledge here by way of head nodding etc. but folks seemed to have issues with using a large number of plugins for solutions. One of the double edged sword issues in open source is the explosion of plugins. On one hand, they expand functionality a great deal but it isn’t like the App Store where products are released only after going through tremendous scrutiny. As a result, conflicts can occur (such as jQuery and javascript) and some plugin authors don’t make regular updates which means your one-time solution can turn into a problem. Of course, there are some amazing plugin developers out there, I even use two licensed plugins for Venture from a developer I know and have worked with for some time.

      I also got the sense that even with the proliferation of improved CMS options available, that didn’t mean complete newbies could jump right in. If anything, I think this issue is connected to the traditional ongoing support problems folks are used to. Training and support, or more precisely a lack thereof, is a crucial element that a number of folks didn’t seem to be getting in both quantity and quality (without being charged exuberant rates).

      Beyond that, there were plenty of how to style questions related to specific platforms (like WordPress) but in a number of instances, the answers depended on first filling information gaps so that folks could have an adequate understanding of the issues they were experiencing.

      Does that help?

      …and BTW, if anyone from the session feels like adding some observations, please don’t be shy about it!

  2. A website in wordpress really doesn’t guarantee that it’ll not be ugly; it just has more potential to be easily transformed into something attractive somewhere down the line. There is an events plugin for wordpress that works; it’s not very pretty, but a good programmer could probablyfix that.

    • Absolutely, the panel made those points abundantly clear in that platforms don’t guarantee final products. However, there is just as much potential to to create an attractive design (as in graphic design) for a WP site as any other platform and comparatively, the design costs should be easier to control given the advantages mentioned in the article about working with the WP platform.

      But regarding the event manager plugins that currently exist for WP, I can speak to this with direct knowledge as I have examined all of them and can say that customizing any of them to incorporate the sorts of features and functionality reviewed in this article is going to be a costly and painful process. It simply isn’t something that can be easily tweaked to fit the needs of professional performing arts organizations.

    • See my comment above to Alexandra but in short, there certainly are a number of good programmers who can edit existing event manger plugins but given the amount of work necessary to incorporate the needs of the most basic performing arts organization, it simply isn’t cost effective. Even the fee based plugins (which can’t be edited without the owners permission as they are not open source) would require substantial modifications and once again, a group would end up spending more to fix/edit an existing plugin.

Leave a Comment