Starting from a tree with nothing in it, deliver one complete, entirely self-contained static website: choose the layout yourself, write every configuration file by hand, and depend on nothing that …

Starting from a tree with nothing in it, deliver one complete, entirely self-contained static website: choose the layout yourself, write every configuration file by hand, and depend on nothing that must be fetched. No package manager, no CDN links, no remote fonts, no external images, no submodules of any kind — the verifier re-runs everything offline with no network and no credentials, and a pointer it cannot fetch reads as a build failure rather than as the cause.

Everything the pages need must be committed as ordinary files in the diff.

Content: a small documentation site for a fictional but coherent command-line tool of your own invention — a landing page, a page of worked examples, and a reference page — written well enough that a stranger could follow it.

Structure: hand-written HTML, hand-written CSS, and at most a small amount of plain JavaScript that the site degrades gracefully without; responsive down to a narrow phone width and legible with styles disabled.

Include a short README naming the single command that produces or serves the static export from a fresh checkout and what a reader should see, and declare the check the verifier should run so that it genuinely inspects the exported output rather than passing on an empty tree. Keep the scope to those three pages: the point is a site that builds and reads cleanly offline, not a large one.