# AC HTML Frontend Style Guide How we build dashboard and utility pages on aesthetic.computer. --- ## Philosophy No frameworks. No build step. No npm for the frontend. One HTML file, readable top to bottom. If you can't understand the whole page in one sitting, it's too complex. AC services are named and self-contained: **oven** bakes, **judge** moderates, **silo** stores. Each gets its own subdomain and its own single `index.html`. The frontend is just the face of the service -- the server does the real work. --- ## File Structure One file per dashboard: ``` service-name/ ├── server.mjs (or api-server.mjs) ├── index.html (the entire frontend) ├── package.json ├── .env └── deploy.fish ``` Everything lives in `index.html` -- styles, markup, script. No separate `.css` or `.js` files unless the page genuinely exceeds ~1000 lines of CSS (kidlisp.com is the one exception, using modular CSS imports). --- ## HTML Skeleton ```html