02 - Custom Design or Template?
Now that we’ve looked at some of the issues regarding the choice of ExpressionEngine for building a church site, we’ll tackle the burning design question - should you have a custom design created for your church site, or purchase a pre-existing template?
One of the really nice thing about ExpressionEngine is that it really can drive sites of all designs - but this fact does put you back in the place of having to make a decision of how you will come up with a design for your church site.
Essentially there are two ways - create a new one, or buy an existing one.
To some web-folks the whole idea of purchasing a template is simply not an option—it’s akin to purchasing a suit off the rack rather than having one tailored to fit. It’s like getting fast-food rather than a professionally-prepared meal by a trained chef. It’s cheap, it’s tawdry, and it cheapens the whole process of building a website.
To which I say…well…let’s just say I don’t agree. Sometimes I think a template approach is the only logical choice.
Here’s the thing—there are plenty of times in life that we purchase major items that are either mass produced and then personalized, or based on a common start that could have been used by someone else.
For example - do you own a house? Did you have it custom-designed or was it based off a common blueprint and modified somewhat? My house is one of several very similar houses on my street - with the same essential floorplan, and just flipped end for end or having a single stall garage vs. two-stall garage, or a slightly different roofline, etc. Some folks can afford and desire a custom-designed house, for the rest of us, well…this is still home.
How about your vehicle? We Americans especially like to talk about how our rides are so much a part of who we are, yet not many of us completely build a custom car from the ground up. Most of us buy a mass-produced version and then personalize - if desired - with aftermarket accessories.
Now this isn’t to say that I think templates are always the right choice for websites. In general I actually prefer to build sites with a custom design - the end result is usually tighter, more specific to the client, and does a better job of presenting them on the web.
However, in the business world I’ve often encountered businesses with a set budget for their website. And within that budget it boils down to a matter of choice - do you want to start with a customized template and invest more in advanced functionality and content management, or do you want to invest in a custom design and then implement in a more static fashion? Many businesses choose the former - and as a web developer I don’t shy away from those projects because I think they still end up with a site that meets their needs and it was still paying work.
In the world of church websites I think the case for templates is even clearer. Sure - there are mega-churches that can (and should) hire a talented designer to create a custom design for their site. But there are also thousands of smaller, neighborhood churches that simply don’t have the staff or funding to do that. The results of that situation are painfully evident on the web—just head over to HealYourChurchWebsite.com to see Dean Peters’ take on some of these sites.
Or - do a search on the churches in your hometown. Chances are, frankly, that most of them will have websites that are pretty bad - not only from a design perspective but with out of date content as well.
One argument that is often levied against templates is that they are not always coded in the most optimal fashion. And that’s been true. But I am seeing more and more templates that are CSS-based, and that’s now trickling down into the “Christian Templates” as well. While searching about for a template to use for this series I came across ChristianTemplatesOnline.com, and they offer their templates in both CSS-based and table-based versions, and they looked pretty nice (they don’t necessarily scream “template!” like so many I’ve looked at).
So my assumption (or thesis) for this whole series is that ExpressionEngine + a purchased design template == a much better site (from both a design and content management perspective) than many churches currently have. If your church can afford it however - get a few quotes on having a designer do a custom design for your church website.
It was a bit hard to choose a template for this series because I don’t have a set of requirements like I normally would with a client-specific project. However, I knew I wanted to cover the implementation of some features that churches typically want - like podcasts, event calendars, etc. After trading some email with ChristianTemplatesOnline.com about the nature of this project, today I purchased their #119 Church template as I liked the feel of it, the number of header images, and the different page types included in the set.
I reviewed the code this afternoon and it will take a bit of tweaking to be used with EE in an optimal fashion - but nothing earth-shattering and for the $58 price it’s well worth what you get (it actually has more page types than the templates I’ve purchased in the past). That price plus $99 for the Personal license of ExpressionEngine puts us at a total investment of $157 so far—not bad!
Note that I did deliberate for a while over using a free template vs. one that needs to be purchased for this series. The free approach worked well in the Small Business series as it allowed people to “play along” at home - but I think it also had the effect of causing a large number of bright-green sites to be launched.
This time I wanted to build a site that looked more polished as it’s going to be auctioned off at the end of the series and actually used by someone. It made more sense to purchase a higher-quality template to begin with so as to have a nice site for the end recipient without also encouraging a large number of look-likes sites to be born.
So there are my thoughts on using templates, and the first look at the visual design of the site we’ll be building.
Next up? Good question.
How about we come up with a sitemap, and start thinking about the ExpressionEngine Architecture that it will require.