Overriding authoring styles with cascading style sheets (CSS)
| |
|
|
Note
|
This topic assumes you have a thorough understanding of cascading style sheet syntax and the use of cascading style sheets within Web applications.
|
Within Hyper.Net's sample WCMS application, the management of styles is handled as follows:
| |
· |
The styles representing the originally authored formatting are stored in the property HNTransformedStyle in each Topic. Note that this style information only exists when the source is coming from a Word or Word-compatible document.
|
| |
· |
The sample WCMS application uses cascading style sheets to control the presentation of all content. In the case of controlling the appearance of published content, the style sheet that's important is portalStyle.css. To locate this style sheet, go to the site collection root, select Modify Content and Structure and select the style library named HNWCMS within the Site Content and Structure Browser:
|
| |
· |
portalStyle.css is the default style sheet for the entire application, and the value of HNTransformedStyle is used to define the style information for each rendered page. Thus the style information in HNTransformedStyle overrides the information in portalStyle.css.
|
| |
· |
You can prevent the information in HNTransformedStyle from taking precedence by using the !important notation in portalStyle.css. Style information marked as !important will then not be overridden when pages are rendered, allowing you to take global control of how specific content is formatted.
|
| |
o |
There are examples of the usage of !important in portalStyle.css.
|
| |
o |
If you have created your own WCMS application, you may decide to not reference the HNTransformedStyle property at all from your application's page layout aspx.
|