Colors and color scales

The Colors module stores brand colors as named tokens with values in multiple color spaces, and supports parent/child scale relationships for web-ready design systems. Clients can copy individual values, download the full palette, or export it in a format their tools can consume directly.

Color tokens

Each color is a named token — for example, Brand Blue or Vault Gold. A token stores the color's value in one or more formats:

HEX — #b8913b
RGB — rgb(184, 145, 59)
HSL — hsl(40, 51%, 48%)
CMYK — for print use (optional)
Pantone — PMS reference (optional)

Clients can click any value in the portal to copy it to the clipboard. The copied format matches the format shown — clicking the HEX value copies the hex string, not the RGB equivalent.

Web color scales

For design systems that use a scale (50–950 increments), boveDAM supports a parent color with child scale entries. The parent token holds the brand name; child tokens are numbered steps that inherit the parent's name with the step appended.

Example: Brand Blue (parent) → Brand Blue 100, Brand Blue 200, … Brand Blue 900.

Parent/child relationships are set when adding a token. A child token cannot exist without a parent. Deleting a parent token prompts you to either delete all child tokens together or promote them to standalone tokens.

Exporting colors

The Colors module's download panel exports the complete palette in three developer-ready formats:

JSON — a flat object with token name as key and all value formats as properties
CSS custom properties — a :root block with one custom property per token (HEX by default)
Tailwind config — a colors object compatible with tailwind.config.js or tailwind.config.ts

Exports include only active tokens. Archived tokens are excluded.

Adding and editing tokens

From the Colors module, click Add color. Enter a name, choose a primary value format (HEX recommended), and fill in any additional formats. To edit an existing token, click its card and select Edit.

Tokens can be marked as Archived instead of deleted — archived tokens remain in the database and in past exports, but are hidden from the client-facing portal view and excluded from new exports.