Running the stack / Forma 3.0
See the server
do its work.
Change a request, inspect the HTML and follow what happens next. These labs use Forma’s Rust rendering path, with browser behavior added only where the example needs it.
Start in Rust. Update in the browser.
Open at 7, then choose Add one: the existing counter becomes 8 without a new request. Refresh returns to the count in the URL. Inspect the initial HTML and the island’s source.
Explore 06 / No JavaScriptLet a form request the next page.
Enter a count and submit. Rust returns complete HTML at the result, even with JavaScript disabled. The number travels in the URL; this demo does not save it in a database.
Explore 07 / Application authorizationA paywall before the HTML.
The fictional Lantern Ledger checks a server-held session before sending its full article. Simulate a subscription, refresh, then reset access. Ordinary forms; no payment or real subscriber account.
Explore Inspector / Actual build artifactsLook inside the rendering contract.
Inspect the native lab’s FMIR, declared props, manifest and build diagnostics. Connect the authored TypeScript to the bytes the Rust renderer consumes.
ExploreTwo useful places to experiment
The playground compiles editable TSX and runs it inside a browser preview. It teaches signals and DOM updates without executing a Rust server. These labs make real requests to the site’s Rust service and show the returned HTML. A static-only copy of the site cannot run that service.
For a saved edit that survives a restart, download the separate Field Notes application. For the application-owned access check behind the paywall, read the engineering case study. Forma’s renderer does not add storage, authentication or billing automatically.