website-deploylisted

# Website Deploy Website Deploy hosts static websites on simple-host.app. There is no server-side execution, but every site gets a small server-backed backend (shared JSON state, append-only collections) that its own page JavaScript can call. ## Service - API and dashboard: `https://simple-host.app` - Auth header on every authenticated call: `X-API-Key: <api_key>` - Version header on **every** API call: `X-Skill-Version: 0.9.0`. Always send it. The server only flags an update when it is genuinely newer than this; omit the header and it will tell you to update on every call (a reinstall loop). - Config file: `~/.website-deploy/config.json` — resolve `~` to the OS home directory yourself (`$HOME` on macOS/Linux, `$env:USERPROFILE` in PowerShell, `%USERPROFILE%` only in `cmd`). Some tool-call paths do not expand a literal `~`. - OpenAPI reference: `/docs.html` ## The one rule that breaks sites: use relative links Every site is served from a **path** on a shared content host: ``` https://sites.simple-host.app/<handle>/<sitename>/ ``` `handle` is the owner's URL-safe handle (from `GET /v1/me`). Because the site lives under a path prefix, a root-absolute URL like `/css/app.css` resolves off the site and 404s. Use `css/app.css`, `./img/x.png`, `../shared/y`. For framework builds, set the base/public path so the output emits relative URLs. Older `https://<sitename>.simple-host.app/` links still resolve (legacy). ## Read the reference that matches the operation Read