Now that I’ve decided on an outline for our model Church site, I can plot out the backend components of ExpressionEngine, or the “ExpressionEngine Architecture” that will be required to power the front-end.

In this post I’ll compare the template against our goals for the site, and make some structural and navigation decisions.

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?

Before getting into the “rubber hits the road” details of implementing a church site on ExpressionEngine, I thought it might make sense to talk about the “business case” for using EE for this purpose and how it stacks up against a Dreamweaver/FrontPage approach, an open source CMS approach, and an Application Service Provider approach.

Yea, OK, so the world getting another blog is no big deal.  In the time it took you to read that sentence at least 3 or 4 other blogs just went live.  However if you are in the place of needing to learn ExpressionEngine for a project I hope you’ll be excited about the series I’m planning to break this blog in with - which will cover building a website for a church on ExpressionEngine.