Chapter 1. Overview

1.1. The content editor

The end user is provided with an editor which lets him to change the content, save it to local data files, generate the output files and upload the generated files to the server. He can also change some configuration options such as the names of the source and output directories, the connection data to the server (address, username and password) etc. The whole of the data is grouped into projects.

1.2. Model of processing

  • Content - data provided by user

  • View - Templates (Template::Toolkit) - created during setup

  • Controller Template::Toolkit processor and this software

Content is provided as directory structure containing data files. The output is the same directory structure with html files (and images). Each content file after processing becomes one html file in the output. In the same input directory structure are provided template files which would be used during prcessing - this way the administrator have quite much power as to which templates shoud be used with which data files. The templates can use data not only from the exact file being processed but also from other data files in the same project.