Files
menu/docs/adr/0003-menu-pages-rendered-per-request.md
T
tanshu edea83228c Menu Set store, image pipeline and Site config
The store keeps a Menu Set's state in the directory layout (drafts/ versus
published/) and its metadata in a manifest, with publishing as a single
directory rename. Editing is allowed on Drafts only, so a published menu can
never change under a customer. Stages 2 and 3 of docs/plan.md, with tests.
2026-09-22 21:15:00 +05:30

521 B

Menu pages are rendered per request

The landing page and Section pages are rendered by the app on each request instead of being generated as static HTML at publish time. Publication becomes a single directory rename, and a Draft is previewed through the same renderer customers use, at the cost of every customer page view depending on the app being up.

Considered Options: static generation at publish time, rejected because it would mean two renderers to keep in step and a separate path for previewing Drafts.