A theme is a set of decisions about contrast, color, and density. Done well, it disappears: the reader sees rows and levels rather than a palette. Done badly, it turns every chart into a puzzle. This chapter covers the palette structure used throughout this manual and the rendering settings that determine whether the theme survives a change of display.
Palette Structure
A working theme needs four groups of colors: background and grid, text and labels, directional data, and emphasis. Each group should have a small fixed set of values. Directional data needs two hues that remain distinguishable at small sizes and in low light; emphasis needs one hue that does not appear anywhere else. When emphasis shares a hue with directional data, every alert looks like a market signal and the alert loses meaning.
This manual's palette uses a cool neutral background, a near-black ink, a deep teal for the primary direction, and an ochre accent for emphasis. The accent is deliberately rare. A theme with three accent colors has no accent at all; it has three competing directions.
Contrast and Density
Text contrast should be checked at the smallest size actually used, not at the heading size. A color that looks comfortable at eighteen pixels may fail at ten. Grid lines should be visible but not competitive: if the grid is the first thing you notice, it is too strong. Hairlines at low opacity do more for structure than solid lines at full strength.
Density is a separate axis from contrast. A dense theme packs more rows into the same space and demands more from the eye. A sparse theme is easier to read and slower to survey. Match density to the panel's role: a footprint chart used for detail can be dense, while a workspace overview should be sparse.
Heatmap Ramps
Heatmaps translate magnitude into color. A good ramp is monotonic in perceived lightness, so that a larger value never looks darker than a smaller one by accident. Two-hue ramps that pass through a light midpoint are common and often fail this test: the midpoint disappears against the background, and the map reads as two unrelated scales.
For depth and volume surfaces, use a ramp with a single hue and a controlled lightness range, and reserve a second hue for a signed quantity such as delta. If both magnitude and sign must be shown, use lightness for magnitude and hue for sign, never the reverse. Reversing that assignment makes the map unreadable for anyone with a color-vision deficiency.
Color-Vision Considerations
Roughly one in twelve men has some form of red-green color-vision deficiency. A theme that relies on red versus green alone will fail for that reader. Use lightness and shape as secondary channels: a filled cell versus an outlined cell, a solid bar versus a hatched bar. These cues survive both grayscale printing and color-vision variation.
Test the theme by converting a screenshot to grayscale. If the directional distinction disappears, the theme is relying too heavily on hue. This test takes seconds and catches most problems before they reach a reader.
Antialiasing settings can change the apparent weight of one-pixel rules. A hairline that looks crisp at one scale factor may vanish at another. Check the theme at the display's native scale factor before adopting it.
High-DPI and Multiple Displays
Scale factors differ between displays, and a workspace can span several. Text that is legible on the primary display may be too small on a secondary display with a higher density. Where the platform allows per-display scaling, set it at the system level rather than compensating with font sizes inside the theme; compensating inside the theme produces inconsistent spacing that is hard to unwind later.
Image-based elements such as icons should be vector or drawn in CSS so they remain sharp at any scale. Raster icons at a fixed size will blur on a high-density display and undermine an otherwise precise theme.
Theme Files and Portability
Store a theme as a small set of named values rather than as a screenshot-matched list of every element. Named values survive redesigns; hard-coded per-element colors do not. Keep a light and a dark variant that share the same names, so switching variants does not require relearning the interface.
When a theme is shared, include the grayscale test result and the display scale factor it was designed for. Those two facts explain most of the differences a recipient will notice. A theme without them is a picture, not a specification.
Common Theme Faults
- Accent inflation. Too many highlighted elements, so nothing stands out.
- Low-contrast labels. Values become unreadable at the size actually used.
- Non-monotonic ramps. Magnitude reads backward in the middle of the scale.
- Grid dominance. Structure overwhelms the data it was meant to support.
- Hue-only encoding. Direction is lost in grayscale or with color-vision deficiency.
Each fault is correctable with a small change to the theme file. None requires rebuilding the workspace.