Entries tagged with “html”.

In our last exciting episode, I promised a crude flowchart and I don’t want to let anyone down. You’ll need to click on it to see the whole thing. Feel free to open it in another window and follow along.

As I read my previous posts it occurred to me that you may not see where I am leading with all these files. The idea I have in mind is to allow editing a particular section of the web site in just one file, but more importantly, I want to limit the changes made to that file to affect only that portion of the web site we are making changes to. As long as each section edit maintains well formed markup, that should happen in each instance.


In our last exciting episode, I presented a very basic use for SSI. Let's take a closer look. Here's an example include directive which pulls in the contents of a file named content.html located in my www directory.

  1. <!--#include virtual="/content.html" -->

Now that's pretty powerful if you have never seen it before, but it gets old quick. Let's add a little power using an Apache variable.

  1. <!--#set var="content" value="/content.html" -->
  2. <!--#include virtual="$content" -->


A CMS is great for people who don't know HTML, but what about those of us who do know HTML and CSS and all those other things?

A CMS is a great way to set up a web site for a customer. Weighing in at 15 to 20 Megabytes, they are often cheaper than forcing your customer to pay for every little update. If you have the tie to learn even a small part of their features you can serve your web site design customers well and keep their costs down.

Quite a few years ago I was working with Apache on a web site and we needed quick and dirty method of creating content for each page which used common headers, footer, menus, etc. Perhaps I was too inexperienced to know about Content Management Systems or perhaps there were just none around.