Collection colors

A Collection is a business category that groups related Engines or modules. The Collection owns the shared visual identity; individual Engines and modules do not have independent colors.

For example, Sales and Accounting may work together as part of the same business category. When they belong to the same Collection, both use that Collection's color so users can recognize their relationship across navigation, dashboards, cards, charts, and other interfaces.

Collection
├── Engine or module A
├── Engine or module B
└── Engine or module C

Collection → assigned categorical color
Engine/module → inherits its Collection identity

Collection colors describe business grouping, not semantic state. They must never replace Info, Success, Warning, or Danger.

Collection palette assignments

Each Collection receives an identity from the reusable categorical palette.

Lime is intentionally unassigned. It remains available for future Collections, charts, datasets, calendars, categories, and other grouping needs.

Identity preview

Usage

Use the Collection token wherever the interface needs to show that Engines or modules belong together:

.sales-collection-card {
    border-color: var(--lesli-color-collection-sales);
}

.finance-collection-marker {
    color: var(--lesli-color-collection-finance);
}

LesliAssets exposes the same identities to Tailwind:

<section class="border-l-4 border-collection-sales">
    Engines and modules in the Sales Collection
</section>

Do not assign a unique color token to every Engine. The Collection token intentionally makes related Engines and modules share one identity.

Accessibility

The Collection color is an identity accent, not a guaranteed text/background pair. The current 500 identities work best for borders, icons, chart marks, and other accents. For larger surfaces, use an appropriate foreground and a lighter or darker shade from the assigned categorical family.

Historical palette aliases

lesli-css 4.1.0 preserves the historical Ruby, Ember, Maize, Agave, Jade, Cenote, Quetzal, Bugambilia, Cacao, and Obsidian token values for backward compatibility. They are deprecated and should not be used when implementing new Collection identities.