How-to

Recipes

Each recipe is one task: the complete code first, then how it works. Every wf example on these pages parses and type-checks in the test suite; a recipe that needs more than its page — a setting in webfluent.app.json, a picture, a data file, a script, another recipe — says so in a Needs: line above the code. To try one, paste the page into a new file under src/pages/ of a project. Most claim the address / or a name the wf init starter already has (Home, Tasks, Settings, User), so start a new project for it (wf init try-it), or replace the starter's file of that name (src/pages/Home.wf for /).

Testing

Checking that a page does what it should before a reader finds out it does not.

Desktop and phone apps

The same project in a window of its own, with Tauri or Electron.

Server rendering

WebFluent as a template engine: HTML and PDF from data, from the command line, Node or Rust.

Projects

Two complete projects, explained step by step. They are read along in the finished code under `examples/tutorials/`, not typed along; each says how to build it yourself if you want to.