Introducing olwibaDX: the developer experience layer
Build-time tooling shared across the ecosystem: dev banners, plugins, and asset generation that make every project feel finished.
Some of the best parts of a polished project are the ones nobody writes twice: the dev server banner, the generated favicons, the OG images that make links look professional. olwibaDX is where that tooling lives.
What it is
olwibaDX (@olwiba/dx) is the developer experience package: Node-only, build-time utilities shared across every ecosystem repo. It is a devDependency, never shipped to the browser, and it carries the small details that separate a finished project from a scaffold:
- Dev server banner: the branded terminal banner you see when running a Genesis project locally, themed from the same project config as the UI
- Build-time plugins: Vite-level utilities that wire project identity into the toolchain
- Asset generation: programmatic OG images and favicons, so every scaffolded project gets a complete social and browser identity without opening a design tool
Why a dedicated package?
Tooling has a habit of being copy-pasted between projects until no two copies match. The ecosystem rule applies here as much as it does to components: solve it once, publish it, and let every project consume the same maintained version.
It also enforces a useful boundary. olwibaDX is intentionally Node-only, which keeps build-time concerns from leaking into browser bundles. If a helper belongs at build time, it has a home, and that home is not your app code.
The compounding detail
Individually, a dev banner or a favicon generator is small. Collectively, they are why a project scaffolded this morning looks and feels like a product by the afternoon: correct icons, correct link previews, a branded terminal, consistent identity from the first run.
That is the ecosystem thesis in miniature: encode every solved problem, even the small ones, so no project starts from zero.
Where it sits in the stack
olwibaDX has no runtime dependencies on the other packages and serves all of them. Genesis consumes it as a devDependency for its banner and asset pipeline. Like the other foundation layers, it is open source under MIT.