Official Forma packages
Forma’s coordinated 3.0 release includes core, compiler, build and create-app on npm; forma-ir, forma-ir-derive and forma-server on crates.io. Their documented contracts are supported together.
| Need | Start here | Relationship |
|---|---|---|
| Signals and browser UI | @getforma/core | Official |
| Native TSX compilation | @getforma/compiler | Official |
| Assets, routes and manifests | @getforma/build | Official |
| Rust page responses | forma-server | Official, Axum integration |
Recipes you can inspect and run
These paths are exercised by the website’s local application checks. “Tested” describes the linked implementation, not every possible configuration of a third-party tool.
| Recipe | Start here | Relationship and verification |
|---|---|---|
| Authored CSS with responsive components | Styling guide · Editable TSX + CSS | Ordinary web compatibility. Plain CSS, responsive layout and browser interaction tested locally; no styling adapter required. |
| Axum + native HTML + declared islands | Native lab · Actual Rust handler · Published starter | Official Forma–Axum response path. Request HTML, response policy, adoption and no-JavaScript behavior tested locally. |
| Fetch, ordinary forms and local persistence | Field Notes source and download · Full-stack lesson | Application recipe using standard HTTP and a JSON file, not a storage adapter. Validation, conflicts, no-JavaScript forms and restart persistence tested locally. Local-only; no user authorization. |
Ordinary web tools, deliberately composed
This site uses CodeMirror for editing, esbuild for browser TSX transformation, Shiki for code highlighting and Pagefind for document search. These are independent projects used by the site, not official Forma adapters or partnership claims. No community adapters are listed here yet.
Tailwind and Sass: available paths, unverified recipes
The Forma build exposes a Tailwind CLI hook. Sass can generate ordinary CSS before the Forma build consumes it. This site has not verified a Tailwind or Sass recipe or version matrix; neither is labelled tested here. Read the styling guide and build configuration before configuring either tool.
Build the application backend
The starter already declares Axum and Tokio as Rust dependencies. Axum routes receive HTTP requests, middleware checks them, and your Rust services can read a database or call another API. Forma renders the page response. Follow the backend guide for the integration and links to the Axum reference.
Validation and persistence belong in your application. The Field Notes recipe does not supply authentication, a multi-instance database or a hosted backend. Its unauthenticated inventory service must remain local until those boundaries are designed for public deployment.
Choose a rendering boundary first
A browser-compatible library can be used in a browser-owned component without implying that its arbitrary JavaScript is part of the native compiler subset. Check native admission rules before moving a component into SSR.