What is it with fundamental, KJV only, pre-millennial, independent Baptist churches and web design that wants to party like it’s 1999? Case in point, the website for the Faith Baptist Church of Dayton Ohio.
I’ve said this a couple times before, if a congregation desires to follow and worship God with such strictness where only a single interpretation of the original Hebrew and Greek – that’s fine. I’m no likelier to get bent out of shape over this issue as I am over the debate whether ManischewitzÂ® matzos make for a more Biblical communion experience than SaltinesÂ® – this and other issues well covered by Paul in 1 Corinthians 10.
What does confound me is how people whom love the law in just about every other area of their lives, practice web design as if no governing standard and/or practices exist; such as the W3C. Especially in a day and age when so many inexpensive and/or free web standards-based publishing systems exist.
I just don’t get it.
What I do get is that today’s example proves once again that FrontPage doesn’t kill web sites, but that people with FrontPage kill websites. Especially people who borrow designs from “Greg and Violet Preston BBFI Missionaries here in Panama” – whose sending church is some other church than FBC of Dayton – though I find no credit given to either.
All this in mind, here are 5 things I’ve visually annotated, and would change about the Faith Baptist Church of Dayton Ohio website:
- Lose the annoying animated GIF banners. Usability guru Jakob Nielsen sums up why this is such a bad practice:
Some links to applications use animated words in an attempt to appear even more attractive and promote the application’s various benefits. This technique backfires even more, because users firmly believe that anything containing moving or blinking words is bound to be a useless advertisement. This belief is typically true, and saves users much time once they’ve developed the ability to ignore moving text. – “Nielsen: Ephemeral Web-Based Applications“
- Stop using graphics to represent, render and/or otherwise display text. Search engines cannot index them, and in the case of today’s example, when poorly rendered with grainy backgrounds and/or inconsistent type faces, humans have difficulty reading them as well.
- Image Bloat, in this case best represented by the the image of the church on the home page that suffers a malady described by Father Flanders in his now famous sermon for Sunday, July 13, 2003:
Just because Jesus miraculously turned water into wine doesnâ€™t mean he can miraculously turn your 1280- x 1024-pixel image whose file size is 1.8Mb into an image whose file size is only 74Kb just because you changed the WIDTH= and HEIGHT= attributes to WIDTH=â€420â€³ and HEIGHT=â€336â€³.
In other words, if you’re going to put an image of a lifeless brick building on your church’s homepage – at least run it through the free and easy to use image optimization program IrfanView.
- It no longer takes alchemy or rocket science to ‘embed Google Maps on your church website‘ … as the Web now offers any number of online programs that make it ‘easier way to integrate Google Maps into your church website.’ Use them to create a separate “Directions” page that not only contains all the essential info for getting to the church – but can be printed out onto a single piece of paper that people can use on the driver there.
- Enough with FrontPage. The product is dead, it only inspires crufty, web-standards and search engine hostile designs and limits updates to the one or two persons who own the software application license. Instead, consider employing a content management &/or a blogging service to render your church website such as:
- Church Community Builder,
- Fellowship Technologies,
- For Ministry,
If nothing else, most if not all of the above tools would help generate a more readable and manageable set of menu navigation items than is currently offered.
There is actually much more we could point out here, but the purpose here isn’t to excoriate the good people of the Faith Baptist Church of Dayton Ohio, but rather to point out that they need to carefully reconsider they message they are currently sending with their current web design – along with considering the cost to render it using the arcane tools and metaphors it currently portends.
Similarly, if you can point out – in instructive love – other items we can all consider, then leave a comment.