 |
|
|
|
|
ZDS Content Management |
 |
Target User
This system is built for a developer. It's a content management system with the top off.
Everything is tweakable.
It works the way a developer expects a development environment to work.
 | The build system is automated under batch files.
One click and the site is re-generated and re-indexed. |
| Indexgen creates a log of syntax errors, missing images, broken links, page weights and so on. |
| The site uses a cascading style sheet to ensure consistent presentation. |
| The site is generated and checked as valid XHTML. |
| The only language required is XHTML |
| The only tool required is a programmer's editor. |
How it works
| A site page is broken down into panes. Static panes are stored in inclusion files.
Content that needs to change for a page is contained in .htmu files.
The generation program assembles these into complete output pages. |
| Everything that can be made soft is made soft by using $STRING_VALUE$ tags.
The generation program expands these into the output XHTML. |
| Custom tags are provided to support standard furniture such as subheads and
bulleted tags. The generation program expands these into the output XHTML. |
What it's like to drive
Adding new pages is, by design, very similar to the programming experience.
An existing .htmu file that's similar to the new one is copied and pasted into a new .htmu file.
To suit the new page :
| File comment lines, Meta tags, Title and Navigation links are changed. |
| Content is added in the Pane 6 area between the Article START and EMD comments.
This can be anything as long as it's valid XHTML. |
| Using the custom tags speeds up the process and makes the content more readable. |
| The start and end index tags control the span that the index generation will scan.
This is usually the entire article content but the tags can be placed to limit
the indexable area, or omitted altogether if the content should not be indexed. |
|
|
