Configure Tailwind styling pipeline
This commit is contained in:
@@ -29,6 +29,14 @@ This project replaces the Excel/VBA workflow named `Catalog maker - 20` with a N
|
||||
- Keep screenshots and traces in Playwright's ignored `test-results/` and `playwright-report/` directories; do not commit them.
|
||||
- A UI change is not complete until the relevant Playwright checks pass.
|
||||
|
||||
## Styling workflow
|
||||
|
||||
- Use Tailwind CSS for new styling and UI changes.
|
||||
- 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.
|
||||
- Use Playwright to inspect the rendered result after every visual change at desktop and narrow viewport sizes.
|
||||
|
||||
## Runtime
|
||||
|
||||
- Start the web app with `npm run dev`.
|
||||
|
||||
Reference in New Issue
Block a user