Each page loads frontage's own Python runtime compiled to WebAssembly and the framework as precompiled bytecode. The source is the same files the browser suite tests.
For with keys, Show, two-way bindingResource, Loading, ErroredSwitch, an Action on submithtml(t"…")A links, query(); ?mode=history for pushStateexamples/site): a whole site rather than a page — pages/ as the site map, one page per post from static_paths(), a layout, a sitemap and a robots.txt as endpoints, and one island on the one post that needs it. It has no single page to link to here; run it with frontage serve examples/site --prerender or build it with frontage site examples/sitefrontage.schema, Markdown rendered at build time — and one ::: island container in a post's prose. Needs pip install "frontage[content]"; build it with frontage prerender, or serve it with frontage serve --prerendermount(page, "#app", when="never") and island(view, when="idle"|"visible"). Under this dev server everything is live at once; the deferral only exists in a frontage prerender buildOptimistic, a Portal modal, an ActionForm