# Deploy a plain HTML status page on Yeeted

Hand-written HTML and CSS, no tooling at all - the platform's bare
`index.html` detection path, and the page whose whole point is staying up
when everything dynamic is down. `smoke.sh <url>` is the entire test surface,
deliberately: there is no logic to unit-test, and adding a build step would
defeat the sample.

## Run locally

From `static/status-html`:

```sh
python3 -m http.server 8000
```

Open `http://localhost:8000`. Edit `index.html` to change the sample service
names or incident text, then refresh. There are no dependencies or build tools.

## Deploy and verify

Follow the [deployment walkthrough](getting-started.md). Deploy this
folder as static files with no database or manifest.

```sh
sh smoke.sh "$PREVIEW_URL"
```

The script checks that the page is served. There are no unit tests because
there is no application logic. To practice versioning, change the page's
visible text, deploy another preview, then roll back and check that the old
text returns.

## What the page does not do

The operational labels and incident shown in the HTML are sample content,
not live Yeeted service measurements. Nothing polls an API or detects an
outage. Publish a new version to change the status. A page hosted on the same
platform as the services it describes is not an independent outage channel;
use separate infrastructure if that is your requirement.

[All examples](index.md) · [Deploy an example](getting-started.md)