Medusa Admin Dashboard Customizer FAQs

Question 1

Why does this skill emphasize separating display and modal queries?

Accepted Answer

Separating them ensures that data displayed on the page loads immediately on mount. If display data is tied to a modal's 'enabled' state, the UI will appear empty after a page refresh when the modal is closed.

Question 2

When should I use this skill instead of the MedusaDocs MCP?

Accepted Answer

Use this skill first for planning, architectural patterns, and critical data-loading rules. Use the MCP server as a secondary source for specific API prop signatures and JS SDK method details.

Question 3

Does this skill handle backend logic for Medusa?

Accepted Answer

No, this skill is specifically for Admin UI development. For implementing backend API routes, services, or subscribers, you should load the 'building-with-medusa' skill.

Question 4

What is the recommended component for creating new entities vs. editing them?

Accepted Answer

Following Medusa's design patterns, you should use a FocusModal for creating new entities and a Drawer for editing existing ones.

Question 5

Can I use standard HTML tags like span or p?

Accepted Answer

It is recommended to use the Medusa UI 'Text' component instead of raw HTML tags to ensure proper typography, scaling, and semantic coloring across the dashboard.

Medusa Admin Dashboard Customizer

주요 기능

사용 사례

Medusa Admin Dashboard Customizer

주요 기능

사용 사례