v0.3.0
Angie transitions from a standalone CSS Framework to a Tailwind plugin. All our products so far use Tailwind and this step has a few advantages:
- Angie does no longer bring its own base styles. Instead Tailwind's base styles (preflight) are used.
- Angie components use the Tailwind theme system instead of having a parallel token system with css variables. Changes to the Tailwind theme are reflected in the components. No parallel worlds.
- Angie components can use Tailwind to offer dynamic utility styles. Example:
ds-stack
component. As usual in Tailwind you can specify the margin like sods-stack-16
ords-stack-[123px]
. - Angie components are processed by Tailwind's JIT engine. Components not used in a product, are not included in the product's stylesheet. This will become even more important when Angie grows up.
Removed:
- Angie no longer styles class-less elements. You always have to add a
ds-
class, e.g.ds-input
. - angie.css (breaking!)
- support for non-Tailwind products