+2 -2

docs/Design/Practical/UI/Styling.md

Reviewed

··· 4 4 5 5 Lumina is not minimalistic. It follows web design trends from decades ago with that approach, but also prefers a clean and modern design. This is why coloured elements are very important, but it also allows us to implement features considered old-school nowadays. 6 6 7 7 - Previously, Lumina used [DaisyUI](https://daisyui.com/) and [TailwindCSS](https://tailwindcss.com/), in iteration 3, the aim is to style as much as possible through [OatUI](https://oat.ink/)'s semantic styling, but with [[Styling/Tailwind usage|modifications done using Tailwind CSS]]. 7 7 + Previously, Lumina used [DaisyUI](https://daisyui.com/) and [TailwindCSS](https://tailwindcss.com/), in iteration 3, [OatUI](https://oat.ink/) defines the base theme and semantic styling, with slight overrides within Lumina's CSS. 8 8 9 9 - See also: [Theme](Styling/Theme.md). 9 9 + See also: [Theme](Styling/Theme.md).

+2 -1

docs/Design/Practical/UI/Styling/Tailwind usage.md

Reviewed

··· 1 1 # Tailwind usage within `Lumina:Peonies:itr3` 2 2 3 3 - Tailwind is used in iteration 3, but sparingly. To keep it from colliding with OatUI's classes system, it's configured to only [respond to the `tw:` prefix](https://tailwindcss.com/docs/upgrade-guide#using-a-prefix). Use semantic (OatUI-styled) HTML when possible, only adjust it with Tailwind. 3 3 + Tailwind is no longer used within iteration 3. It complexifies build steps and potentially clashes with the styling done 4 4 + by hand and by Oat.