This reference is being written. The outline below is the intended structure.
Not Medusa’s admin-vite-plugin. The dashboard SDK is Mercur’s own extension framework for both panels — it scans
src/routes/**/page.tsx files, generates navigation, and injects everything through virtual:mercur/* modules at build time. Medusa’s defineWidgetConfig / defineRouteConfig and widget zones are not part of this model. Start with Extending Panels for the authoring guide; this page covers the plugin’s internals and options.What it does
File-based routing, virtual route modules, and block resolution for the admin and vendor panels.Setup in a host app
RegisteringmercurDashboardPlugin in a Vite app.
Configuration options
Backend and vendor URLs, i18n, and build-time config.Extension entry points
admin_ui and vendor_ui entry points exported by block packages.