SCoT - simple content management tool


How to Write Your SCoT Files

Every SCoT file is composed of lines. Each line translates into an HTML element. Keeping that in mind, we have to be carefull about what to write in which line.

Writing Project Properties File

The "project.properties" file contains information for the whole project.

Writing SCoT Header Files

The header file contains information about the hole resulting HTML document. By now it is the stylesheet and the title of the document.

The header file also contains a brief description or overview of the following content. When composing the HTML document that displays the overview over this level of your project the content of the header file will be displayed there.

Writing SCoT Content Files

The content files hold content and only content. Every line of a content file is treated as a content line (see how to write content lines).

Writing SCoT Content Order Files

Content order files only hold information which contents will appear in the HTML document and in which order.

Writing SCoT Frameset Files

Frameset files are just what they are named like: frameset definitions.

Writing SCoT Fragement Files

Fragment files are pure content, but this content is part of one or more other contents and can be included into more than one HTML document. Every line is treated as a content line.

Writing SCoT Content Lines

A line in the SCoT files that will be treated as a content line must have as a first character the sign for the blockbuilding tag it will get for its HTML representation. Blockbuilding tags are for example <h1>, <h2>, <p>, <table> or <ul>.

As well there are inline tags to be handled like <a> or <img>. Those inline tags where made up by so called commandos.

Back to overview.


Diese Seiten wurden mit SCoT nach folgenden Standards erstellt: xHTML 1.0, CSS 2.0.

Zuletzt geändert:

© 2004-2005 by Kai Görnt