Inside the plugin-first admin
How the admin shell loads core routes and app surfaces while keeping shared UI, routing, and API helpers in one place.
One shell, many surfaces
Mash apps ship their own admin routes, API controllers, migrations, permissions, and frontend bundles. The host admin shell provides the shared navigation, theme, API client, and UI kit so each app can focus on its own workflow.
The runtime import map keeps React and shared Mash modules single-instanced, which matters for hooks, routing, and UI context across app boundaries.
Why this matters
A plugin-first admin keeps the core smaller while still making installed apps feel native. Teams can enable accounting, CRM, ecommerce, licensing, subscriptions, or other modules without changing how the shell behaves.
Comments (0)
Be the first to leave a comment.
