For the complete documentation index, see llms.txt. This page is also available as Markdown.

Theming Guide

Limio supports theming so each customer can have their own visual identity while using the same component library.

How it works

Every component's appearance is driven by CSS custom properties (design tokens). You inject a stylesheet that overrides the tokens you want to change — everything else inherits from the default theme.

You can inject custom CSS via your Limio settings (Developer → General Settings). See how to inject custom code for the general approach.

Customising your theme

Inject a CSS stylesheet that overrides the design tokens you want to change:

@layer base {
  :root {
    --tw-primary: 220 85% 45%;
    --tw-primary-foreground: 0 0% 100%;
    --tw-text-primary: 220 60% 15%;
    --tw-text-secondary: 220 30% 35%;
    --tw-surface-main: 220 15% 96%;
    --tw-radius: 0.75rem;
  }
}

Only override what differs from the default. All other tokens inherit automatically.

Colour values are space-separated HSL triplets without the hsl() wrapper (e.g. 220 85% 45%, not 220, 85%, 45% and not hsl(220, 85%, 45%)). Components compose the token as hsl(var(--tw-primary) / <alpha-value>), so a comma-separated value produces invalid CSS and silently breaks every opacity utility (for example the Button's hover:tw-bg-primary/80).

Testing your changes

Use your browser's developer tools to override token values and preview changes instantly in Storybook.

Further reading

  • Design Tokens — all available tokens and their defaults

  • Primitives — the component catalogue

  • Compositions — real-world patterns showing themed components in action

Last updated

Was this helpful?