rfw documentation

Guides

• The mental model: rfw in a single concept; the
  DOM as a projection of Go state.
  
• Why rfw (and why not): an honest comparison with
  templ + HTMX, Datastar, and SPA frameworks.
  
• Getting started from Node: install Go,
  fix the PATH gotcha, and map npm mental models to the Go toolchain.
  
• Build a real-time dashboard in 30 minutes:
  scaffold, stores, @for lists, event handlers, and a live data feed.
  
• Dynamic lists and events: fetch data, render
  rows, handle clicks; the pattern behind every real page.
  
• Server Side Computed (SSC): host components, host
  signals, broadcasts and serving; the server-driven half of rfw.
  
• State and lifecycle: batching, memo values,
  asynchronous resources, component scopes, and browser library cleanup.
  
• Routing: named routes, redirects, cancellable loaders,
  metadata, scroll restoration, and built-in component wrappers.
  
• SSC security model: what crosses the wire, what
  stays on the server, and the auth work rfw leaves to you.
  
• Hot reload: what is instant, what is not: measured
  rebuild times and the honest limits of the dev loop.
  
• Testing: native tests, browser (wasm) tests with
  wasmbrowsertest, race testing and golden templates.
  

Plugins

• Pages plugin: file-based routing generated from the
  pages/ directory.
  

Measurements

• Benchmarks: TodoMVC and live updates vs Svelte, Solid and
  htmx; bundle sizes, load, interaction and memory.