The skin's constants feed information about your design to the core TypoScript objects. These values are particularly important for controlling the maximum image widths and for proper operation of the modules and columns.
This file is located in the skin directory at typoscript/skin_constants.ts
This set of constants is very important and governs the maximum image widths and module/column widths. You need to set a value for the each content area within each template that you are using.
For example:
containerWidth.f1a.feature = 980
means that the feature area in template F1a is 980 pixels wide. These values are often written in multi-line format.
For example:
containerWidth {
f1a {
feature =980
contentBlock-1 = 980
}
f1d {
feature = 980
contentBlock-1 = 700
generatedContent-1 = 260
}
}
would mean that:
Set this constant to "1" if you want feature content to bleed by default or set it to "0" if you want it not to bleed by default. In either case the default can be overridden on a page by page basis via a drop down menu in the page properties.
These values are needed so the framework can adjust the max image widths for the feature area. When calculating the values add the CSS padding and border values together.
As an example, if your CSS is 20px of padding on the right with no border then you give featureRightPadding a value of 20. However, if your CSS is 20px of padding on the right and a 4px right border then you would give featureRightPadding a value of 24.
The system can automatically generate an H1 headline from the page title and place it at the beginning of the main content block (contentBlock-1). Set this constant to "1" to have the headline generated by default or set it to "0" to not have it generated. In either case the default can be overridden on a page by page basis via a drop down menu in the page properties.
These constants are not really needed by the core but in the QuickSite supply info needed to generate the local menu located in the generated content -1. These constants are often adjusted in various parts of the page tree to tailor the local menu to each section.
These constants set the id of the SysFolders from which content is pulled for the generated content blocks (generatedContent-1 & generatedContent-2). Note that these constants can be reset at different points in the page tree. This, for instance, allows you to pull one set of content for a products section and another set for the rest of the site.
These constants are for the proper rendering of modules and columns.
This is the value that specifies how many pixels you want between modules or between columns.
Set this value to "1" if you want your column groups to have a CSS class of "columnGroupRule" by default or set it to "0" if you do not want the class added by default. This default can be overridden on an individual column group basis. The CSS class is normally used to add a bottom border on the bottom of the column group.
These are the padding values around the body of the module. These are needed to recalculate the max image widths when the modules are set to bleed or the module feature image FCE is used.
This needs to be the width of any border you put on the div with a class of moduleBodyWrap within a module.
Set this to "1" if you want the module title to render on the front end by default. Set it to "0" if you want the module title to not be rendered by default. This setting can be overridden on a module by module basis.
Give the total height for the footers on your modules. This is needed for calculating the module heights and evening out those heights. Include any top/bottom border or padding in this number. Enter "0" if you do not want a footer on your modules.
This constant allows the developer to specify the tag that wraps the module header. It can take values like h1, h2, h3, h4, h5, div and p. The default is h3.
This constant allows the developer to specify what should be the normal header level of content elements within a framed module. Its value can be numbers 1 through 5. A value of 3 would mean that a "normal" header inside your module would be an h3. If no value is specified it will use the normal header specified for the entire site.