Site Operations
How areactor.org is built, deployed and kept safe. Reference material: edit an entry when reality changes.
01How deployment works
This is a Worker with static assets, not a Pages project, and the difference decides whether server code runs at all.
02Where secrets live
Runtime variables and Build variables are two different boxes with the same label, and only one of them reaches a running request.
03The mail system
Seven endpoints, one provider, no npm packages, and the reason a link in an email never does anything on its own
04Keeping files private
Committed and published are different things, and .assetsignore is what separates them.
05The tools
Four scripts that generate things by hand rather than at request time, and what to run after changing what
06Load-bearing lines
Declarations that look optional and are not, and the class names already claimed by style.css. Both fail silently, and both have caught us more than once.