Editable data files
Nav lists, config objects and other JSON — edited through a form, not a code file. You choose which files editors can touch.
Not everything is a page. Nav menus, social links, a little site config — the
kind of thing that lives in a nav.json or config.json. List those files in
orbit.config.yaml and Orbit gives editors a form for each, inferred
straight from the JSON shape: objects become fields, arrays become add/remove
lists, and each value picks its own control.
Crucially, only the files you declare are editable — editors stay well clear
of the rest of your code. It’s the ethos in one feature: edit the data, not the
design. (Orbit edits JSON; if your nav is a .ts file, have it import the JSON
and Orbit edits that.)