compiling node modules
This commit is contained in:
@@ -49,6 +49,30 @@ compilation: debug
|
||||
listening on http://localhost:5150
|
||||
```
|
||||
|
||||
## Styling (CSS build)
|
||||
|
||||
The UI uses Tailwind CSS + daisyUI. Rather than the render-blocking Tailwind
|
||||
Play CDN, the stylesheet is compiled ahead of time into a purged, minified
|
||||
bundle at `assets/static/css/app.css` (served at `/static/css/app.css`).
|
||||
|
||||
One-time setup:
|
||||
|
||||
```sh
|
||||
npm install
|
||||
```
|
||||
|
||||
Rebuild the bundle after changing any class names in `assets/views/**/*.html`
|
||||
or the theme config:
|
||||
|
||||
```sh
|
||||
npm run build:css # one-off, minified
|
||||
npm run watch:css # rebuild on save while developing templates
|
||||
```
|
||||
|
||||
`assets/static/css/app.css` is committed, so a deploy needs no Node step — but
|
||||
remember to rebuild and commit it whenever the templates change. The Tailwind
|
||||
source lives in `assets/css/tailwind.css`; theme config is `tailwind.config.js`.
|
||||
|
||||
## Full Stack Serving
|
||||
|
||||
You can check your [configuration](config/development.yaml) to pick either frontend setup or server-side rendered template, and activate the relevant configuration sections.
|
||||
|
||||
Reference in New Issue
Block a user