2 central configuration files and 3 types of file to describe the dressing

A file to configure general information about the web site

As stated in the installation part you will first have to edit the 'config' file in the 'Bin' directory of the package to specify general characteristics of your web production workflow

• The directory of the plain html pages : the 'Src' or Source Directory
  This is the root directory which will contain everything you need to build your website : simple html files that will be organized into subdirectories, image and other media files included into or linked from the HTML file, and one or more of the later presented files that will describe template for the web site design, objects to be used within the template or directly inside plain html page, and browsing tree description.

• The directory of the dressed html pages : the 'Docs' or Destination Directory
  This is the directory where ManyPage will put the html page he produces.
  
  
• Be sure that the 'Src' directory is readable by the user of the script and that he has writing right in the 'Docs' directory.
  
  
• NB. : in version 0.9 you may define only one couple 'Src/Docs' directory, i.e., you can manage only one server's root directory at a time. Nevertheless, as it doesn't take to much place, you can easily install one different package for each server. It is planed that later on, the 'config' file will be able to contain an unlimited list of couple 'Src/Docs'.
  
  
• Here is a example of what you could find in a config file :
  <Source>
/usr/httpd/Src
</Source>
<Destination>
/usr/httpd/Docs
</Destination>

A file to configure different versions of the design

In some case, it is interesting to be able to present the same information in different ways. It could be to make a page either more easy to be printed or with less heavy graphics to download, or more easy to understand by blind people. It is something very easy to do with ManyPage.

First you choose a suffix for these pages, for instance 'light' for pages with less graphics and only textual menu. Then you have to edit the 'autre_habillage' file in the 'Bin' directory of the package to specify in which part of the site you want to use more than one template.

For instance the following 'autre_habillage'file...

<Autre_habillage>
<NOM>light</NOM>
<PARTIE>/</PARTIE>
</Autre_habillage>

<Autre_habillage>
<NOM>print</NOM>
<PARTIE>/Articles</PARTIE>
<NOT_PARTIE>/Articles/Data</NOT_PARTIE>
</Autre_habillage>

... will mean that, in all the site, there will be 2 pages produced in the 'Docs' directory for each page in the 'Src' directory (one with a 'light' suffix) and 3 pages in the '/Articles' subdirectory. For instance if there is a file 'index.en.html' in 'Src/Articles/', ManyPage will produce the following files in the 'Docs/Articles/' directory : 'index.en.html', 'index.light.en.html' and 'index.print.en.html'.

The "NOT_PARTIE" defines a subpart in which the second dressing is not produced.

A important point is that every links that appears inside the Source files will be replaced with the adequate suffix inside each destination file ("/Toto/titi.en.html" will be transform into" /Toto/titi.light.en.html" into the 'index.light.en.html' file). ManyPage consider that links exist only as a value of one of the following HTML attribute : 'HREF', 'SRC', 'BACKGROUND' and 'CODE'.

If you don't want a link to be transformed in that way, you have to put the corresponding HTML code within the following tags :

<!---PARALLELE--->
HTML code example : <A HREF="/LinkNotModified/toto.fr.html">It will not be modified</A> and that and this...
<!---/PARALLELE--->

Of course, to define the different designs of these pages, one should specify specific templates respectively in '.dress.light' and '.obj.light' files at the same place where we already defined '.dress' and '.obj' file for the default template.

---

Dressing description

To specify a design for a site, we have to define a template : a simple HTML file that structure the information, in which we will put HTML objects (like a browsing menu) and data from the source plain file.

The following files may appear anywhere inside the Source Directory. There should be at least one .dress and certainly one .obj file in the root directory. By default one of these files apply to the directory in which it is put and all its subdirectories. One can specify .dress and .obj files for only one file by using its prefix with the adequate suffix. For instance, I will introduce objects dedicated to the file tata.en.html into a file named tata.obj

.dress : main template

.obj : objects used in the template

.link : browsing tree