A live app, in one Markdown file

Everything on this page — the prose, the fetched list, the badges, the form, the counter — is a single .wd file. No components. No JSX. No build config. Watch where JavaScript actually enters.

Static until proven reactive

This whole section is plain Markdown. The list below is unrolled at build time from a JSON file — it renders into HTML with no runtime at all:

• Folder routing without config — Pages come from site/pages, and hidden work is just dot or minus prefixed.

• One loop, @loop — Loop a JSON file, an in-scope value, or a :state list — includes inside inherit the loop value.

• Colocated behavior — A matching .skin or .js file beside the page is picked up automatically.

Fetched data, looped, with nested conditions

:fetch pulls JSON over the network into reactive state — from a static file here, or any API. Until it lands, the page shows a fallback. Each row then decides its own badge from nested conditionals, in plain Markdown:

No ternaries, no .map(), no framework — the outer :if checks blocked, the inner one checks shipped, per row, and both stay reactive.

A counter that survives reload

:state … persist keeps this in localStorage, and :computed derives from it. Star a few, reload the page, and it holds:

A form that talks to a real server

This form posts to the demo echo endpoint and shows the reply. With JavaScript it is a fetch; without it, the exact same markup is a native POST. On Vercel/dev the sample endpoint replies; on static-only hosts, point action= at your own backend — Darkmown adapts instead of owning one:

That was one file. Static prose, build-time loops, fetched data, nested conditionals, persistent state, computed values, and a server round-trip — and the only JavaScript on the page is the shared runtime Darkmown loads for you. Read the docs or deploy your own.