CSS Styles

Teradata Viewpoint is Teradata's strategic and innovative SOV (single operational view) for Teradata DB, Aster, and HDP Hadoop systems management and monitoring that enables Teradata's Unified Data Architecture (UDA).
Teradata Employee

CSS Styles

The default CSS styles for the widget library are defined in global.css in CommonsWeb. Styles for individual portlets should be defined in the css directory of each portlet. The PDK will create this directory for you. Although it is acceptable to have multiple stylesheets for a portlet, the best page loading performance is achieved with the fewest stylesheets. A unique CSS classname should be assigned to each new type of portlet that is developed. In order to prevent namespace collision, this CSS classname selector should be used in all portlet style sheets.

How Do I Look?

To maintain the harmonious, unified look to the portal, the color palette, font style and font hierarchy should be adhered to by all portlet developers.


Background color and font color selection should be limited to these colors whenever possible

Font Style

The font face to be used throughout is Verdana. Verdana is a sans-serif font that is narrower than Arial and wider than Tahoma. It is also less bold than either.

Font Hierarchy

To ensure that proper emphasis is given throughout, a font hierarchy has been developed for the portlets.

Preferences Pages

Preference Page Colors

The preference page overlays the current portal display. 

Preference Page Text and Layout


Data Collection Pages

Document Standards

The Document Type determines how CSS is applied to a document. The Viewport Portal does not support the Strict standard. All pages should be developed with the Transitional document header:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

Caveats and Tips

Different browsers and different versions of browsers have different default spacing for HTML elements and different interpretations of CSS. While it is easiest to develop in Mozilla, the customer base requires that we support Internet Explorer version 8. Since IE is an older browser, it has more compatibility baggage to carry and some CSS developed on Mozilla may not work the same or at all on IE8. It is recommended to develop CSS on IE and Mozilla concurrently. Developing entirely on Mozilla first and then trying to change the styles to work with IE is sure to be an exercise in frustration.

Tags (3)