This site provides several opportunities for users to add HTML content to screens. For instance, the Community, Project home, and My start pages might include custom HTML content.
Custom HTML generally inherits the styling from the page's Cascading Style Sheet (CSS) files. Styles and formatting defined in the style sheet will apply also to user-supplied content, adding to or possibly overriding any formatting specified in it. For instance, the stylesheet might specify that table heading (th) content is to be aligned left. Table headings in user-supplied HTML that appear center-aligned before inclusion will automatically be left-aligned after inclusion. Similarly, the fonts and colors will match that of other HTML appearing in the same page.
In most cases, this is desirable for the sake of consistency and ease of HTML authoring; however, if it is not, you can use the tips that follow to help eliminate unwanted styling differences.
To make user-supplied HTML more consistent with the site formatting, try to remove the formatting-related elements and attributes from the included HTML. For instance, remove all font tags, style, bgcolor, and align attributes, and use structural HTML elements like headings (e.g., h2), paragraphs, and list constructs instead of breaks (br), images of text, tables for layout, spacer images, and so on.
The most likely cause for the site style application failure is that the HTML fails to identify the structural significance of the text, instead describing its desired appearance. To remedy, convert this sort of HTML:
<font size="4" face="Arial, Helvetica"> <b> Welcome to project foo! </b> <Br> <img src="../images/spacer.gif" height="1" width="1" vspace="4" alt=""> <font size="2"> This is only a picture of a paragraph. </font> </font> <Br> <Br>
<div class="h2"> <h2> Welcome to project foo! </h2> <p> This is a real paragraph. </p></div>
Note that the HTML best suited for application of CSS is also the simplest to write and edit by hand, and results in smaller (faster) files. Furthermore, it tends to remain accessible when rendered outside the context of a desktop PC, such as WebTV or a hand-held browsing device.
A useful tool for automating cleanup of HTML produced by software such as MS Office, FrontPage, or Netscape 4.x Composer is HTML Tidy.
To preserve custom styling in user-supplied HTML, use inline CSS; i.e.,
style attribute instead of the various style-related
attributes and elements such as
valign that CSS superseded in 1996.
For instance, the following HTML may not render with the intended styling in the context of a site screen:
<h1 align="center"> <font face="Times" color="#cc0000"> Welcome to project foo! </font> </h1>
To preserve such styling, the various formatting properties should be expressed using CSS:
<h1 style="text-align:center; font-family:Times; color:#c00"> Welcome to project foo! </h1>
This inline CSS will override any conflicting styling provided by the site stylesheet. To learn more about CSS usage, check the following sources:
More complex or extensive style customization may call for appendices to the site stylesheets themselves and requires a deeper understanding of CSS in the site than this document aims to provide. Please provide feedback to CollabNet about your expectations in this area.
The following is a suggested configuration file for HTML Tidy. This utility will clean up many HTML syntax and usage problems that can lead to unexpected results with the site in various browser/platform contexts. For best results, use Tidy on all HTML you intend to integrate into the site screens.
tidy-mark: no markup: yes wrap: 0 wrap-attributes: no wrap-script-literals: no wrap-asp: yes wrap-jste: yes wrap-php: yes literal-attributes: no tab-size: 1 indent: auto indent-spaces: 1 indent-attributes: no hide-endtags: no input-xml: no output-xml: yes add-xml-pi: no add-xml-decl: no output-xhtml: no doctype: auto char-encoding: ascii numeric-entities: yes quote-marks: no quote-nbsp: yes quote-ampersand: yes assume-xml-procins: no fix-backslash: yes break-before-br: no uppercase-tags: no uppercase-attributes: no word-2000: yes clean: yes logical-emphasis: no drop-empty-paras: yes drop-font-tags: yes enclose-text: yes enclose-block-text: no fix-bad-comments: yes add-xml-space: no alt-text: "" write-back: yes keep-time: no show-warnings: no quiet: yes gnu-emacs: yes split: no