Troubleshooting
Concrete checks for common installation, theme and integration problems.
HTML has no CSS
- Keep root HTML files beside assets.
- Check stylesheet hrefs and filename case.
- Do not add crossorigin to file:// stylesheet links.
- Hard-refresh with Ctrl+F5 or use the localhost helper.
- Inspect the first failed request in the Network panel.
Theme does not change
Reset saved appearance when testing changed defaults. Check data-theme, data-bs-theme and dir on the document element. Replace fixed custom colors with shared tokens and ensure overrides load after shared styles.
HTML edits disappear
A workflow script may rebuild main on load. Edit its render function or stop that demo module from controlling your new server-rendered page.
Mock API fails to connect
- Start mock-server.cjs and keep the terminal open.
- Open /api/health at the correct port.
- Use localhost HTTP, not file://, for a cross-origin HTML client.
- Check the fetch API base URL in your custom script.
- Read the JSON error body for 409/422/503 responses.
- Remember that restarting the mock server resets all records.
Records seem missing
Browser data is separate for different ports, hostnames, protocols and editions. Session-only showcase records reset by design. Export important demo records before clearing browser storage.
Report a reproducible issue
Include edition/version, exact route, browser, viewport, theme/direction, reproduction steps, expected and actual behavior, a screenshot and the first relevant console error. Remove secrets and personal data. Seller contact and support policy must be supplied by the seller; this guide does not invent them.