Step 1
Set Config
Keep the public API base URL in `config.js` so the UI stays clean and deployment remains static.
Static multi-page frontend
This frontend stays deployment-friendly for GitHub Pages: plain HTML, CSS, and JavaScript with no build step, no framework, and no server-side routing.
Current backend coverage
Step 1
Keep the public API base URL in `config.js` so the UI stays clean and deployment remains static.
Step 2
Login on the auth page and keep the JWT in the browser for later admin requests.
Step 3
Use the dashboard to create a device entry and test heartbeat calls against the backend.
Upload the entire `frontend/` folder as static files. The pages link to each other with relative paths, so they work from `file://` URLs and from GitHub Pages. Configure the backend URL in `config.js`. The backend still needs CORS enabled if the frontend and API are served from different origins.