About
About
Essays on why WebFluent works as it does: read once, for the argument, not looked up.
Why WebFluent
Why the language exists, and the choices it makes: one meaning per word, a compiler that refuses what would break in the browser, and one source for the web and for paper.
How reactivity works
What happens between a click and the one text node it changes: signals, derived values, effects, branches and keyed lists, with no virtual DOM in between.
Accessibility
Pages that work with a keyboard, a screen reader or voice control: what the built-ins do, what the compiler checks, and what no tool can check for you.
Security
What the compiler guarantees, what it cannot, and why: markup, secrets, sessions, uploads, the content security policy and what a project trusts.
What a build ships
Learn what a build already does to be fast, see what it weighs, set budgets that warn, time pages in a browser, and avoid what makes a site slow.
Static or single-page
The same source builds as pre-rendered pages or as one app shell. What each gives you, what the pre-rendered page holds, and what each asks of a host.
Contributing
How the compiler is put together, how to build and test it, and how to change the language, a built-in or this guide.