We often get told ‘We want to make changes to the web site ourselves when it’s finished’ when being briefed for a web site. This causes two directions of thought:
- The client either needs to know programming, which is rare, because if they did – they’d make the site themselves.
- The client will use Front Page or Dream Weaver to make their own changes.
One of the big problems with the second choice is that the client who will inevitably be making those changes doesn’t think like a programmer and doesn’t know the intricacies of amending even the simple things such as text. For instance, putting & instead of & (which I’ve seen today on someone’s site.
Why should that matter?
Accessibility is an issue that is really starting to sink in to most business web sites now and these innocent changes can ruin the rest of the ‘accessible’ powers of a well built site. This means that your ‘well oiled car’ could be let down by one or two rogue washers.
The third option is to build a database behind the web site. This is an excellent option for a News Section, for example where a person can log on to an admin section of a web site, add stories and upload pictures, and then this would automatically update the page that people see.
The important part of that is regularity of updates. If your news section shows ‘old news’ then that could do you more harm than good. This also defeats the point of the initial requirement. It is a common story (we’ve done it ourselves) where we added content management to our web site and then never managed the content on a regular basis. We scrapped that and went back to the old way of plain old html pages.
One more very important issue with Database Driven Web Sites that often gets overlooked is that databases run on queries. A web page will query a database for information, which is then sent back in the correct format to be displayed. The problem with many databases are that they don’t adapt to direct approach on the web. This is where a person may search in a search engine and be directed to a specific page on your web site, rather than just to the home page. From a visual point of view, this may look like:
http://www.yourdomain.co.uk/RunScript.asp?p=ASP\Pg0.asp
This means nothing to many people but is crucial. You need to make sure that people understand when they are being driven to your site. Blogs cope with this perfectly by creating a ‘Permalink’ for each individual page that they create (Blogs run on databases, don’t you know). Therefore you can create direct links into pages. For example, the permalink for this page is:
http://theescape.typepad.com/blog/2006/01/database_driven.html
Another very important point on this issue is that Search Engines like to understand your pages. The name of the actual page counts for a lot. This may relate to the database created name (as above) or even on static pages where some people (still) create pages with names such as page1.html, page2.html. Google wants to see clarity, eg.
http://www.the-escape.co.uk/ourwebwork/sallygunnell/index.asp
It’s also a hell of a lot easier when you are trying to direct people to specific pages!
I’m sure that your web design agency knows these things, but if you want people to find you with clarity - you need look after the detail.