The problem it solves for agents
An agent that has just written a page can only hand the user a code block. The user then has to copy it, save it, name it, open it — and half the time what opens is subtly wrong: mojibake where the charset was never declared, images that a browser blocks because they were referenced over http://, a stylesheet that resolved against a folder on the machine where the file was generated.
What it does
One request publishes the document and returns a URL. Before the page goes live, six checks run:
- charset — declared, or non-ASCII text arrives as mojibake
- mixed content —
http://subresources are blocked on an HTTPS page - local paths —
file://references resolve to nothing anywhere else - viewport — absent, and a phone renders the desktop layout
- script resolution —
<script src>pointing at a directory that is not there - inline handlers — event attributes a strict host strips
Checks with a safe default fix can be applied automatically; the rest are reported rather than silently rewritten.
Terms
Free pages run for 30 days and can be extended. Publishing requires no account. The URL is generated at publish time.
