CSS

Most .css is configured in /files/home/configuration/css

this folder contains:

• css.css
• cssx.css

css.css and cssx.css are both sent to the response UNLESS a person is editing a page, and the xStandard editor is configured to ONLY apply cssx.css to the interactive editing window.

A few Placeholders require their own css; and usually linked to from webpage_functions.asp : DrawConditionalJSPostProcess() function. examples include:

• /lightbox/css/lightbox.css
• /css/form_default.css
• /datepicker/datepicker.css
• /anything.variables.yetii.css

anything.varialbes.yetii.css is an exception to the rule as the css is built per request, based on the 'variables' passed to it. This is fully processed in engine_redirector.asp : Engine_Redirector()

The initial intention was that css.css and cssx.css would be configured per instance of the CMS by the person installing the CMS.

• The editable 'body' of a CMS page is wrapped in <div id="content" class="content">
• everything consisting of the 'body' of a cms page is warped in <div id="page" class="page">
• masthead is wrapped in <div id="mnu" class="mnu">
• footer wrapped in <div id="footer" class="footer">

Many placeholders including MessageBoard call on classes defined in css.css directly. It is messy, but was built fast.

Inline style is supported though not recommended as it complicated administrative tasks:
Inline style example - float a portion of code to the top left, with some space around it:
<table border="0" cellpadding="1" cellspacing="2" style="float: left; margin: 0px 10px 0px 0px;" width="202">
<tr align="left" valign="top">
<td>
<p>floated content goes here</p>
</td>
</tr>
</table>

Xstandard Styles - create or modify - example

xstandard_styles.xml

<style>
<id>span</id>
<name xml:lang="en">highlight</name>
<name xml:lang="xx">TODO</name>
<elt>span</elt>
<attr>
<name>class</name>
<value>highlight</value>
</attr>
</style>

cssx.css

.highlight { /* HIGHLIGHT*/
color: red;
}