This section is for people working on Emet itself rather than using it: how the code is laid out and why, how to run it against a site on your disk and how the tests work.
- Architecture is the tour. It covers the content backends, how a running copy decides which one to use, where configuration comes from, the store, the build and the one server-side component.
- Local development gets you from a clone to a running dev server, in local, mock or GitHub mode, and lists every npm script.
- Testing covers Vitest, the shared helpers and what a unit, hook and component test look like here.
The repository’s CLAUDE.md is a terser version of the same material, written for coding agents; it’s kept in sync with the code and worth reading alongside these pages. Contributions go through pull requests against master, and CONTRIBUTING.md has the short version of what’s expected.