# Integration Notes

Use `Design.md` as the compact project context and `THEME-GUIDE.md` for visual changes.

## PHP/CMS handoff

1. Use each HTML file as the structural reference for that route/state.
2. Keep `assets/css/theme.css` and `assets/js/theme.js` shared.
3. Load one server-theme stylesheet after `theme.css`.
4. Replace `<!-- Dynamic: ... -->` fixtures with CMS/game/session output.
5. Preserve page-content DOM/classes represented by `playground.html` and the files in `programmer-reference/`.
6. Keep existing project dependencies required by the CMS (Font Awesome, Bootstrap grid/forms, jQuery, Bootstrap JS, `generic.js`, SweetAlert2).
7. `programmer-reference/` is documentation/reference only, not a runtime include directory.
8. Do not introduce PWA registration, service workers, SPA/hash routing, static authentication, payment logic, or production API calls into the frontend preview.

## Source of truth order

When requirements conflict, use this order:

1. Current explicit product/design request.
2. `Design.md`.
3. `playground.html` for component compatibility.
4. `programmer-reference/components-base.template.php` and `components-form-base.template.php`.
5. Individual static page fixtures.