Users

``` --- ## Fragment Rules * Use fragments for reusable UI components * Keep fragments small and focused * Keep fragment root structure compatible with the HTMX target context (for example row/cell/table containers) ### Example ```html

``` --- ## HTMX Compatibility * Templates must support partial rendering * Use fragments for HTMX responses * HTMX fragments must exclude duplicate `//` wrappers * For endpoints serving both full-page and HTMX responses, branch on `HX-Request` and return the correct template/fragment shape * For HTMX redirects/navigation, prefer `HX-Redirect` or `HX-Location` on non-3xx responses --- ## Expression Rules * Use `${}` for variables * Avoid complex logic in templates --- ## Form Handling * Use `th:action` and `th:object` ### Example ```html ``` --- ## Defaults * Templates directory: `src/main/resources/templates` * Use semantic HTML * Keep templates simple --- ## Naming Conventions - index.html → full page - list.html → fragment list - form.html → form UI - *_row.html → table rows --- ## Anti-Patterns * Do NOT duplicate HTML structures * Do NOT embed business logic in templates * Do NOT mix with SPA frameworks * Do NOT return full pages for HTMX updates * Do NOT define Tailwind/HTMX scripts in templates that are not guaranteed to render in final HTML * Do NOT reference CSS/JS/font/icon CDN URLs in page templates or fragments by default --- ## Validation Checklist Before finishing: - Open page source and confirm Tailwind/HTMX scripts are present in `` - Confirm shared CSS/JS/fonts/icons are loaded from local static paths - Confirm full-page routes render full document structure - Confirm HTMX routes return fragment-only HTML