What is DMS?

DMS is a relatively simplistic architecture for websites based around simply setting up a master design, and using includes to serve content. This is an extremely flexible solution. What this allows you to do is set up templates to house various types of content, and then write multiple includes to fit the templates. Previously, this was more difficult, as there was no concept of a template, only your base design.

Then, with the advent of the <inc> xml file structure, this problem went away, and users can now implement any number of designs.

Why reinvent the proverbial wheel?

Most "CMS" systems are...far too bloated. DMS's purpose is to pare the huge feature set of a CMS down to the bare basics - serving a website and organizing your thoughts. The rest of the a CMS's features are...deminimis -- too unimportant to be carried over.

What does it run on?

While the concept of DMS could be implemented in any language on any platform, this specific implementation uses PHP on IIS...previously it was PHP on Apache.

What should DMS be used for, and by whom?

DMS is intended for small- to medium-sized websites of under 20 pages. This, however, describes a major portion of all websites on the web for individuals or small businesses. DMS is intended for use by those who know a thing or three about HTML already, and aren't afraid to write HTML and CSS. Those more timid about such things would be better served by WordPress or Blogger.

When should DMS not be used?

DMS should not be used on any site that is primarily data-driven, requires any sort of e-commerce function, or has a significant public / private dichotomy. While it is very possible to integrate this functionality into DMS, it is intended to be a flat-file / XML / Javascript based web system -- not database-driven.

Where is DMS going?

The next step I'm taking for DMS is session control. What this will do is allow navigation to be automated, and will also permit us to

The