There are two general approaches to creating an inexpensive web site. One is to hire web programmers to design a site using html software like Dreamweaver or FrontPage. To update content (for example, to correct a typo or to add a sentence), you must hire a programmer or expert to post it on the site.
The other approach is to use a Content Management System (CMS) that allows users to post content directly to the site without needing special software. The web programmer merely designs the look and structure of the site. A good CMS will allow agencies to separate the roles of (a) writers who post content, from (b) editors who approve and revise the content before posting it publicly, from (c) programmers who change the graphic design and structure of the site.
This blog is an example of a content management system. It is free and easy to use, but is based on a complex and powerful software platform that just makes it look easy. You can change the structure and look of it in seconds by giving it a new template.
Here's a good article that summarizes CMS's at various price points. Inexpensive CMS's include Trellix, which offers its site-building tool through web hosts like Earthlink and Interland; Windows SharePoint Services hosted by services like UnifiedWebMedia or Apptix; MacroMedia's Contribute; Ektron CMS100;Bricolage; Plone; and ActionApps. Also see Mark Surman's review of mostly open source CMSs, and Robin Good's review of inexpensive ones.
Increasingly even regular web design software like Dreamweaver and FrontPage are selling themselves as CMS's (for example, SharePoint is included in FrontPage.) Some of them require an experienced programmer to set them up and host them before you can begin using them. Others, like blogs, can be instantly used by newbies but don't offer much functionality.
The tasks involved in creating a web site using a CMS are:
1. Decide what you want in a web site (see this article for some tips).
2. Hire someone to help to design the structure, functionality and type of content for your site. If your needs are simple and generic, you can copy someone else's site or use templates like the ones provided by Trellix or FrontPage; in that case, you don't have to hire anyone. But if your needs are more complex, you probably should ask someone to help you figure out who you want to serve and what you want the site to do for you.
3. Select a content management software platform and web host for your site. This should be done after you have defined the site requirements in step one, and at the same time you're designing the site.
4. Create the content and post it. Writing the content should be done in parallel with the previous steps. You won't know what your site should look like if you don't have example content to put into it. And most agencies suffer from writer's block when it comes to populating the site – don't be in the position of delaying a web site launch for months because no-one was writing the material that you want to post.
5. Define the processes for updating it and maintaining the site. Staff must be assigned to ensure that content is updated and that the web site is monitored. You may need to switch web hosts occasionally if service is not adequate, especially if you're using inexpensive services that can be unreliable.
Look for content management and hosting services with the following capabilities:
- Writers should be able to post content using a web browser, without needing to know html. It shouldn't take more than 20 minutes to show a writer how to post content, and preferably less than that.
- There should be a way for editors to review and revise content before posting it publicly, even if it's just to check for spelling mistakes.
- For visitors to your website, it should be compatible with a wide range of browsers, not only the latest version of Internet Explorer. However, it is acceptable to ask your writers and editors to use a specific browser unless you want community members to post content.
- There should be a way to back up data in case the host's server goes down or the host goes out of business.
- You should be able to easily switch programmers and/or web hosts if service is not satisfactory. Don't get locked into a proprietary system or one that only a couple of people know how to use.
- The service should match your needs and your budget. Don't pay for functions that you will not need within the next two or three years. Just make sure you can switch to another platform if necessary. In other words, make sure you can export content. In a small site with just a few pages, you can save content into a word processor. In a big site you need to export content in some kind of database-compatible format.
Services change quickly, and basic Content Management Services are getting cheaper all the time. On the other hand, highly complex needs still require big budgets. (See full-featured services by Atomz for example, as well as this comparison between Ektron and Rhythmyx.) In the next few years, deciding on a web site platform will be as easy as deciding on a word processor. There will be a few big competitors, but all of the serious contenders will be compatible with each other. You won't need to hire a consultant to develop a basic site, just as you don't need to hire a professional desktop publisher to type up a report. Until then, keep up to date with the choices and try to stay as simple as possible.
Update – November 5 2003 – I just looked at Pmachine, a nice looking portal program that appears both inexpensive (under $130 US) and powerful. It's built on PHP and MySQL, and is especially strong at incorporating multiple weblogs into the portal.