Quote Originally Posted by Mike_Walsh View Post
As far as the website content is concerned, nothing fancy; basically all that's required is a modern-day, electronic version of the old noticeboard. It's a private member's club; lists of upcoming events, timetables, opening hours, where to find them, that kind of thing. No forums or anything like that; the only external links are to a handful of other websites, where their own link can be found. And that's pretty much it.
That fits within my earlier recommendation of XHTML+CSS or XHTML+CSS+SSI. Either can be done with a page template or two.

About the SSI, if you've decided on Apache2, then you would activate the SSI module with sudo a2enmod include. Then in the relevant <Directory ...> or <Location ...> stanza put Options +IncludesNOEXEC to allow SSI there.

Then name the documents .shtml instead of .html. (Or, alternately, use the x-bit hack). Inside the documents, you can then link to files containing fragments of XHTML, such as navigation menus, headers and footers.

Inside the file you would point to the files containing the fragments for inclusion using virtual= or file=

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
<html xmlns="http://www.w3.org/1999/xhtml">
 <title>A web page</title>
 <link href="anicestylesheet.css" rel="stylesheet" type="text/css" media="screen" />
 <!--#include virtual="/header.html" -->
 <!--#include virtual="/navmenu.html" -->
 <h1>A web page</h1>
 <p>Hello, World</p>
 <!--#include virtual="/footer.html" -->

As I see it, the advantages of SSI are that it is very secure ( and very low maintenance, and very easy once you get the idea and work out a process. The disadvantages are that some web designers might not see it as glamorous, there is a lower number of billable hours in the site development, and the drama/visibility of the maintenance is lower.