configImperium projectContent you author here, rendered by the shared page engine. The default, and what every site starts as.
Imperium: site types and view modes
Imperium is what puts a website on the internet. A site is one record; a worker matches the incoming hostname to it and serves it, so a new site is live seconds after you publish rather than after a deploy. Everything below is read from the registry the serving code itself uses — 6 site types and 34 view modes.
Site types
A site type answers “where do the bytes come from?” — Imperium renders the page itself, or forwards to something you run, or serves a folder you uploaded. 2 of the 6 are operator-only, because they reach the host beyond that site’s own data; an ordinary member is refused at the write lane rather than at serve time.
proxyReverse proxy — an app you already runForward this host to an origin that is already up: another port, another machine, another provider. You keep it running.
origin- The address of the app that is already running. http or https only.
trustedOrigin- Sends Cookie and Authorization upstream. OFF by default on purpose — turn it on only when the upstream is genuinely yours, or you are handing Leumas session cookies to whoever runs it.
stripPrefix- Removed before forwarding, so an app that expects to live at / can be mounted at /app.
hostHeader- IIS and nginx pick which site answers from this header. If your app is bound to a hostname, the default will 404 while the app itself is perfectly fine.
serverServer — a local app Imperium runsoperator onlyPoint at a folder on this machine and a port. Imperium starts the app, keeps it up, and serves it on this domain. That is the difference from a proxy: a proxy needs the app already running, this one owns the process.
port- Loopback only — a local app is never addressable from off the machine.
dir- Required once "Start it for me" is on. Leave it empty and this simply forwards to the port, without ever spawning anything.
autostart- Off by default: saving a path must never start a process.
command- One argument per chip — npm · run · dev. Spawned with NO shell, so nothing in it can be reinterpreted as shell syntax. Leave it empty to detect from the folder (package.json start, then dev, then an entry file).
healthPath- Probed to decide "is it up yet?" before the first request is forwarded. Must start with /.
env- PORT is always injected from the port above and wins over anything set here, so the app and the proxy can never disagree about where it listens.
trustedOrigin- ON by default here, unlike a proxy: a local app is your own, and sharing the session is the point of running it on your Leumas domain.
stripPrefix- Removed before forwarding, so an app that expects to live at / can be mounted at /app.
hostHeader- IIS and nginx pick which site answers from this header. If your app is bound to a hostname, the default will 404 while the app itself is perfectly fine.
staticStatic bundle (any path)operator onlyServe a built folder — a Vite or Next export — straight from disk, by absolute path. Operator-only, because the path is unconstrained.
dir- Absolute path to the build
spa- Unknown paths fall back to index.html. Turn it off for a plain static site, so a missing page 404s honestly instead of returning the homepage.
bundleUploaded bundle (this site’s files)Serve the build you uploaded to this site on the Files tab. Same serving as a static bundle, but the folder is this site’s own — no server paths involved, which is why a member may use it and static is operator-only.
dir- Relative to this site’s own storage. Empty means the root of what you uploaded. A .. segment is refused — escaping the site folder is the one thing this kind exists to make impossible.
spa- Unknown paths fall back to index.html.
redirectRedirectSend visitors somewhere else. What makes a domain migration painless.
to- An absolute http(s) URL, or a path on this site starting with /.
preservePath- /about arrives at the destination’s /about rather than at its homepage.
permanent- Off by default: browsers cache a permanent redirect, so a wrong one is painful to undo. Turn it on once the move is final.
View modes
A view mode answers the other half — what kind of page this is. It decides the fields you fill in and the renderer that draws them. Every mode has a renderer and every renderer has a mode; a guard asserts both directions, so nothing here can be listed and unbuildable.
| Mode | Name | Group | Fields | Layouts | Needs |
|---|---|---|---|---|---|
agent | Agent Mode | app | 11 | Card, Framed | external |
cell | Cell Mode | app | 11 | — | — |
dataApp | DataApp Mode | app | 5 | Table, Dense, Cards | — |
deck | Command Deck | app | 3 | — | — |
embed | Embed Mode | app | 5 | Framed, Full screen | external |
forge | Forgefull screen | app | 1 | — | — |
hud | HUD / Display Modefull screen | app | 8 | — | — |
mcp | MCP Servernot a page | app | 3 | — | storage |
mediaGlobe | Media Globe Modefull screen | app | 4 | — | — |
operator | Operator Deck | app | 4 | Command — rails either side, Focus — the operator alone | — |
os | OS Desktop Modefull screen | app | 1 | — | — |
review | Review Mode | app | 10 | — | — |
server | Server Mode | app | 9 | Status, Framed | external |
service | Service Mode | app | 9 | Offer, Tiers, List | — |
toolCluster | Tool Cluster Mode | app | 3 | — | — |
fundraising | Fundraising Mode | commerce | 11 | — | — |
multiPageForm | Multi-Page Form Mode | commerce | 8 | — | — |
storefront | Storefront | commerce | 20 | Grid, List, Drop | storage, records |
blog | Blog Mode | content | 8 | Cards, List | storage, records |
docs | Docs Mode | content | 9 | Manuscript, Sidebar, Reference | — |
faq | FAQ Mode | content | 6 | Accordion, Open list, Two columns, Grouped | — |
folder | Folder Mode | content | 8 | — | storage |
gallery | Gallery Mode | content | 5 | Grid, Masonry, Filmstrip | storage |
html | HTML Mode | content | 5 | Framed, Inline, Full screen | blocks |
landing | Landing Mode | content | 12 | Hero split, Poster, Story, Spotlight, Service, Welcome | blocks |
linkPortal | Link Portal Mode | content | 11 | Stacked list, Grid | — |
location | Location Mode | content | 14 | — | — |
policy | Policy Mode | content | 8 | Numbered, Plain, Plain-language | — |
portal | Portal Mode | content | 5 | Tiles, Rows, Single column | — |
timeline | Timeline Mode | content | 7 | Vertical, Alternating, Compact, Milestones | — |
default | Default | core | 3 | — | — |
wireframe | Blueprint | core | 5 | — | — |
exe | Exe Downloads | distribution | 5 | — | storage |
repo | Repo Mode | distribution | 13 | — | — |
Fields is how many values that mode’s form accepts. Layouts are the arrangements it can be drawn in. Needs is what the mode requires of the platform — storage for uploaded files, records for a collection it reads, external for something you run elsewhere, blocks for a page you compose.