Every UI Component works in Nebula
Nebula ships hand-written JSON for the core admin — but third-party extensions don't have to lift a finger. Two companion modules make sure every Magento UI Component renders in the Nebula theme, whether you migrate it or not.
Get this on qoliber.comIncludes a seat in the Nebula SlackMembers only
Getting Nebula UI Bridge also grants you access to the dedicated Nebula Slack channel — a direct line to the team building it and the community using it.
coverage of 3rd-party modules*
Universal UI Compatibility
Every UI Component works out of the box
Nebula ships hand-written JSON for the core admin, but it doesn't stop there. Two companion modules make sure that every Magento UI Component — including the ones from extensions you haven't even installed yet — renders in the Nebula theme.
* We estimate this figure based on absolutely nothing. We just know it works.
NebulaUiBridge
RuntimeIntercepts any Magento UI Component while the page is being assembled, walks its node tree and converts it to a Nebula component on the fly. The third-party grid or form renders in Nebula's look — no edits to the extension, no JSON to write.
- Converts columns, filters, paging, mass actions, datasources & form fieldsets
- Two-tier cache: durable in var/nebula/ + in-memory hot path
- Unsupported nodes degrade to a marker, never a white screen
bin/magento nebula:ui:capture-fixtures <component>NebulaUiTransformer
Build-time CLIThe offline counterpart. Point it at a vendor module and it reads the ui_component XML and emits permanent Nebula JSON drafts plus a layout stub — ready to review, tweak and commit into your own module.
- Reads vendor ui_component XML → emits .form.json / .listing.json drafts
- Generates layout stubs and a warnings file for manual edge cases
- Turn the runtime conversion into canonical, version-controlled JSON
bin/magento nebula:ui:transform vendor/magento/module-cmsBridge handles it live for anything you haven't migrated; Transformer lets you bake that conversion into permanent JSON when you want full control. Between the two, third-party extensions just work.
Under the hood
How the Bridge resolves a component at runtime
When Magento schedules a <uiComponent>, the Bridge steps through a four-stage chain — fastest path first, live transform last.
Canonical definition
If Nebula (or you) shipped a hand-written JSON definition for this component, it is used as-is. This is how the core admin screens render.
Durable cache
Otherwise the Bridge looks for a previously transformed definition under var/nebula/ — it survives cache:clean and setup:upgrade.
Memory cache
A hot-path lookup in the nebula_ui_bridge cache type, keyed by component + module hash, returns instantly on repeat renders.
Live transform
On a cold miss, the Bridge walks the assembled UI-component tree, converts every node (columns, filters, fieldsets, fields…) and renders it through NebulaGrid / NebulaForm — then persists the result for next time.
If a node type isn't supported yet, it degrades to a small marker in developer mode — the rest of the screen still renders. Never a white screen.
Command reference
Tools you'll actually use
bin/magento nebula:ui:transform <path>Transformer — read a vendor module’s ui_component XML and emit permanent Nebula JSON drafts + a layout stub.
bin/magento nebula:ui:capture-fixtures <component>Bridge — snapshot a component’s assembled config to a fixture, used to lock down converter behaviour in tests.
bin/magento cache:clean nebula_ui_bridgeBust the runtime conversion cache after enabling/disabling modules or changing definitions.
About that 95%
Nebula hand-writes JSON for the screens merchants touch every day. The Bridge then covers the long tail of third-party components automatically. The exact figure depends on your installed extensions — but in practice, components built on Magento's standard UI library just work. And if one doesn't, the Transformer gives you a clean JSON starting point in seconds.
Support Nebula
Like what we're building? Back it.
Nebula is built by qoliber. If the Bridge just saved you a week of migration work — or you simply want a genuinely modern Magento admin to exist — you can chip in and help us get it to a stable release. Every tier helps; pick whichever feels right.