Osetailer-doc is an OSEtailer OSELIB taglib with taglib the actual OSELIB package. It contains several powerful tags for the templating document. With the osetailer-doc taglib you are able to remove all content from the template giving the template the job of presentation layout. The content is managed in files with a .cmf type and should contain only a few html and taglib tags. I've been limiting the tags in the content to html <p> <br> and taglib <doc:link ...> tags. The template documents live in the pages directory of the webroot.
The doc:page tag is a powerhouse tag that renders the DOCTYPE tag, the opening html tag, the complete head tags including the title and style, the opening body tag and the closing doc:page tag will render the closing body and html tags. I forgot to mention in that last sentence that doc:page also renders the appropriate div tags with style class and style id as desired. Unless specified the style class equals the product value given and the style id equals the application given.
| Tag Id | attribute | requirement | value type | default value | description |
|---|---|---|---|---|---|
| doc:page | This is the initializing tag and is required for other tags to work properly. | ||||
| product | required | string | none | This defines the product level of directories, message properties and the default style class. | |
| application | required | string | none | This defines the application level of directories, message properties and the default style id. | |
| page | required | string | none | This defines the page level of directories, message properties. | |
| autostyle | optional | boolean | true | Use auto generated style class and style id? | |
| styleClass | optional | string | autostyle ? product : null | The class value of the style attribute. | |
| styleId | optional | string | autostyle ? application : null | The id value of the style attribute. | |
| doc:pagehead | This tag uses the ApplicationResources properties file keys to generate the h1 and h2 headers. The h1 header is searched for using header as the key value. It builds upon the header value by also search for product.header and product.application.header keys. The previous values of header and product.header may be erased by using a .override key like product.application.header.override. The h2 header ApplicationResources properties key is byline and is treated the same as the h1 header key. | ||||
| styleClass | optional | string | autostyle ? product : null | The class value of the style attribute. | |
| styleId | optional | string | autostyle ? application : null | The id value of the style attribute. | |
| doc:heading | This tag uses the ApplicationResources properties file keys to generate heading level tag with the specified key value. | ||||
| level | optional | integer | 1 | The heading level value. Because of HTML contraints the max value is 6. | |
| key | required | string | none | The ApplicationResources properties key for the heading value. | |
| styleClass | optional | string | autostyle ? product : null | The class value of the style attribute. | |
| styleId | optional | string | autostyle ? application : null | The id value of the style attribute. | |
| doc:zone | This tag includes the .cmf file and surrounding it with div tags giving the style class and style id attributes. | ||||
| id | optional | string | center | The cms directory and style id specification. This will look for the named cmf file in a directory with the id name. For example it will cms/product/application/center/foo.cmf then will look for cms/product/center/foo.cmf then look for product/center/foo.cmf. A file not found will give unexpected results. | |
| cmf | optional | string | page | The cms .cmf file specification. | |
| styleClass | optional | string | autostyle ? product : null | The class value of the style attribute. | |
| styleId | optional | string | autostyle ? application : null | The id value of the style attribute. | |