One config should ship every surface
Why OMEGA exists, and the stubborn opinions holding it together.
Make one brand config the whole machine — website, backend, desktop, extension — so builders spend their time on the product, never the plumbing.
A stack where launching your fourth surface is as boring as your first — configure it, compose it, ship it. The machinery disappears; the brand is all anyone sees.
Five frameworks became one stack
The consolidation that produced OMEGA.
A backend manager, a website manager, a desktop manager, an extension manager, a shared web library — each carried one surface, each solved the same problems its own way
The OMEGA monorepo unified them: one config format, one CLI, one section library, shared theming — with every consumer's semantics preserved
The section library landed: every page is composition calls over your data, themes reskin the same content, and a showcase documents every band automatically
Published packages, real brands, and the same one-command birth for everyone: npx omega setup
What we refuse to compromise on
Four principles, in order. When two collide, the smaller number wins.
Upgrades never make you relearn your own project. The machinery changes; your contract doesn't.
Delete a key and the surface disappears. No dead switches, no zombie config.
Nothing publishes because you committed. Shipping is a verb you say out loud.
Every value lives in exactly one place — and secrets never live in config.