Heal Your Church WebSite


Teaching, rebuking, correcting & training in righteous web design.

Go ahead, Mock my Site

One of the important techniques I learned from Vincent Flanders’ original book was that you should first use a graphics application to mock-up what you want your site to look like. Of course, this should be done ONLY after you have:

  1. defined the personality and purpose of your church
  2. clearly identified your target users, and
  3. established a content hierarchy/outline.

Click Here to see full-sized Sub/Section Page Layout

As I continue to work on the Redland Baptist redesign, and having engaged the three above steps, I’m now hashing out the look-n-feel with a mock-up which at arbitrary stopping-points, I post up on the church web site server. I then email a URL to the church staff and others involved to solicit their comments, ideas, thoughts and feelings.

One of the few problems that arise from this approach is that they’re looking at a static graphic, so those viewing it cannot envision what I see with regards to various technical aspects. So along with a ‘clean’ graphic, I also provide them with an annotated mock-layout. This then gives those viewing the mock-up some technical context as to what I’m proposing.

And just to show you I’m no Matthew 23 type pharisee I’ve posted my annotated layout for my sub/section pages here for your inspection. See what you think (careful, the full-sized version is about 42kb).

5 Comments

  1. *ahem* .. a few spell checks might be nice for this piece. first paragraph: “us” -> “use” and “shoud” -> “should”. point 1: “your the” -> “the”. the sentence “As I..” has a comma splice and has tense errors.

    sorry, that’s the english-freak in me.. i’m sure you can find lots of errors on my site.

  2. Is all the content driven by MT, or are there sections that are “static,” i.e., outside of the MT database?

  3. How technical is your staff? I wonder if the “data driven” and “cron job” terminology is lost on them.

    MT for the site too, eh?

    I’m at the same step in the re-design for RidgePoint.com, and put together a 15 page requirements doc that includes site architecture, list and requirements for each page type in the site, branding requirements, and required deliverables.

    I’m lucky enough to have a small design budget, so the requirements doc went to both an outside design firm, and an internal church member interested in taking a shot at the design.

    Not sure how I feel about the “design by committee” approach, though. While getting buy in from the staff is important, shouldn’t the focus be on getting feedback from end users instead? Or are they the “others”?

    Any thoughts/concerns on the masthead focusing on the building?

  4. Hi Dean: I’m a regular at Homesteading today and apparently missed the excitement this A.M. with the hacker. Anyway, when I tried to log in tonight the site was very slow and wouldn’t let me go from one topic to another. You may already know this and I would have e-mailed Chuck directly but I linked to your site from his mission4me site so here I am.

    By the way, I’d like to thank you and Chuck both for your work on the forum. I think you guys do a great job.

    johnkl

  5. Hi Dean: I’m a regular at Homesteading today and apparently missed the excitement this A.M. with the hacker. Anyway, when I tried to log in tonight the site was very slow and wouldn’t let me go from one topic to another. You may already know this and I would have e-mailed Chuck directly but I linked to your site from his mission4me site so here I am.

    By the way, I’d like to thank you and Chuck both for your work on the forum. I think you guys do a great job.

    johnkl