Migrate UI styling to Tailwind components

2026-08-05 13:04:55 +02:00
parent e60522495a
commit c1c63043c8
4 changed files with 111 additions and 856 deletions
@@ -35,6 +35,7 @@ This project replaces the Excel/VBA workflow named `Catalog maker - 20` with a N
 - Keep shared tokens in `src/tailwind.css` using `@theme` and base/component layers.
 - Run `npm run css:build` after styling changes; `public/styles.css` is generated output.
 - Prefer Tailwind utility classes and Tailwind-style component patterns for buttons, panels, dialogs and responsive layouts.
+- Whenever a reusable pattern appears, prefer Tailwind component patterns (`@layer components` with `@apply`) over handwritten legacy CSS; keep one-off layout details as utility classes where practical.
 - Use Playwright to inspect the rendered result after every visual change at desktop and narrow viewport sizes.

 ## Runtime