Templates
Main
There is one template per webspace. Templates are housed in the /templates folder.
The default template file is template1.html which is used for the initial template for each new webspace, and for admin page content.
Each template contains some html that defines the general look and feel, a set of used for inserting the page content, and CSS style definitions.
Making your own
To create or modify a template:
- make a copy of template1.html, save it as template2.html
- edit the html to your liking, and upload it
- finally, change the webspace template setting (Webspace Admin | Settings).
You can also upload templates using the Webspace admin file upload facility, if your users dont have ftp access.
Insertion Field tags
The only tags that are required are and . The rest are optional. For an extended list of tags see Insertable Fields.
|
|
This is the most important tag, it houses the body text for each page , required |
|
|
this is where the small graphic is inserted for managers to access their admin areas , required |
|
|
used for the webspace name, item page name or admin page names , recommended |
|
|
sidebar content text , used for the page item sidebar aswell as admin page dialogs; essential for template1.html, otherwise optional. |
|
Main site nav bar , recomended |
|
|
CMS > Main Admin > Templates |
Used for a cookie crumb nav bar , optional |
Styles
There are two sets of styles. The first is contained in cms.css, whose function is to render a bland default page (designed to be overridden if need be in your webpage styles) and to render the cms formatting (like tables and boxes, headings etc). It is recommended you make as few changes to this style sheet as you can so that it serves as a baseline for future styles.
The second set of styles are in the template itself, and contain whatever you need to define your page layout, plus anything you need to override anything in the css file. If you have extensive styles feel free to put them in a separate sheet.
Mostly the style definitions are functional, with a few exceptions:
- .cms -- The webspace content that is injected into the webpages (body, panelbody) is encased in this class.
- .spacename -- renders the webspace names on the webspace index (H3)
- .itemname -- renders the webspace item names on a webspace main pages (H3)
- .twostars -- renders the **Heading** on webspace item pages (P)
- .threestars -- renders the ***Heading*** on webspace item pages (P)
- .dateline -- this is used for the small texts following the webspace names and webspace item names on the webspaces index and webspace main pages (H3)
- one or two others you can find in the html source if you are curious.
Note
The cms styles are for the better part designed to mimic the default behavior of your average word processor, that is, line endings don`t create a blank line, and bullets are not indented etc. This makes it more intuitive for the average user. Duplicate spaces are honored using non-breaking spaces, and ditto for duplicate new lines. Headings are not H level headings but inline class styles. Its not right, its not good code but its what people want. But psst...you can however create a level 3 heading using pairs of hashs ( like ##My heading##) on its own line of course.
