The top level structure is split up in sections for stylesheets, images, frameset definitions and content files.
At first you decide where to place your HTML project. Therefore you create a root folder where everything you need is placed in. For example we name the folder "example" and place it under "D:\scot".
Now we've got a root folder and its path is "D:\scot\example". By the way, this is the path that you give as the source path when running scot-app (see Running SCoT).
There are several properties to store with the project. This is the right place to do it: the project.properties file in the top level folder. See how to write project properties file for further information.
For corporate design we'd prefer to use stylesheets like cascading stylesheets, CSS for short. The place to store our CSS is a folder named "css". Let's create it in "D:\scot\example". Now put in a simple stylesheet and name it "screen.css" to make clear that this stylesheet is used for output on screen.
The path to our stylesheet is now "D:\scot\example\css\screen.css". The name of the file is up to you, but it must be place in a parent folder named "css" being placed in your root folder.
Images are put in a folder named "images". When you've got a favIcon just put it in this folder.
To stay at our example, we've got now an image with the following path: "D:\scot\example\images\myFavIcon.ico".
Framesets are somewhat different from contents or images, and so they'll get their own folder, "frames" by name. Maybe we'd like to create a frameset named "start.scot" so we should place it into "frames".
Frameset files compiles to HTML documents that are named like the frameset file with the suffix "frame.html".
At last we've got a file with "D:\scot\example\frames\start.scot" as its path. The resulting HTML document will be named "startframe.html".
See how to write frameset files for further information.
These are the real contents. Therefore this folder named "contents" will be the one with the most files and subfolders(!) in it.
The most used HTML documents are those named "index.html". To create one, add a subfolder "index" to "D:\scot\example\contents" and put an "index.scot" file into it.
Lets see what we've got: a file "D:\scot\example\contents\index\index.scot".
See organizing content files and how to write content files for further information.
Fragments are pure content. Fragments are referred to from other content files to be merged into them. Fragments can be used in one or more content files. Fragments get their own folder name "fragments" which is placed in "D:\scot\example". Let's create a footer fragment that contains content that can be displayed at the end of every HTML document. Name it "footer.scot" and place in "fragments".
By now we've got a footer file "D:\scot\example\fragments\footer.scot".
There are two fragment files that will always be processed if they exist. These are "pageHeader.scot" and "pageFooter.scot". They form the header and footer of every HTML document that is created.
See how to write fragment files for further information.
Let's have look at all these nice little files and folders we created during this lesson.
Description | Path |
---|---|
root folder | D:\scot\example |
project.properties file | D:\scot\example\project.properties |
stylesheet folder | D:\scot\example\css |
screen stylesheet | D:\scot\example\css\screen.css |
images folder | D:\scot\example\images |
favIcon image | D:\scot\example\images\myFavIcon.ico |
frameset definitions folder | D:\scot\example\frames |
frameset definition | D:\scot\example\frames\start.scot |
content folder | D:\scot\example\contents |
index.html | D:\scot\example\contents\index\index.html |
fragments folder | D:\scot\example\fragments |
footer fragment | D:\scot\example\fragments\footer.scot |
Back to how to organize your SCoT files.
Diese Seiten wurden mit SCoT nach folgenden Standards erstellt: xHTML 1.0, CSS 2.0.
Zuletzt geändert: