asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: general fixes and improvements (#13417)

Browse Source
This commit is contained in:
Shahed Nasser
2025-09-04 19:27:34 +03:00
committed by GitHub
parent 55a35e4721
commit 8785fb4e1a
5 changed files with 69 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
www/apps/book/app/learn/customization/reuse-customizations/page.mdx
+10 -4
View File
@@ -4,14 +4,20 @@ export const metadata = {
# {metadata.title}
In the previous chapters, you've learned important concepts related to creating modules, implementing commerce features in workflows, exposing those features in API routes, customizing the Medusa Admin dashboard with Admin Extensions, and integrating third-party systems.
In the previous chapters, you've followed the [brand example](../custom-features/page.mdx) to learn important concepts related to:
You've implemented the brands example within a single Medusa application. However, this approach is not scalable when you want to reuse your customizations across multiple projects.
- [Creating modules](../custom-features/module/page.mdx).
- [Implementing commerce features in workflows](../custom-features/workflow/page.mdx).
- [Exposing those features in API routes](../custom-features/api-route/page.mdx).
- [Customizing the Medusa Admin dashboard with Admin Extensions](../customize-admin/page.mdx).
- [Integrating third-party systems](../integrate-systems/page.mdx).
To reuse your customizations across multiple Medusa applications, such as implementing brands in different projects, you can create a plugin. A plugin is an NPM package that encapsulates your customizations and can be installed in any Medusa application. Plugins can include modules, workflows, API routes, Admin Extensions, and more.
You've implemented the brands example within a single Medusa application. However, this approach is not scalable. If you want to use the same brands feature in different Medusa applications, you would have to manually copy the code and maintain it across all projects.
Instead, to reuse your customizations across multiple Medusa applications, you can create a plugin. A plugin is an NPM package that encapsulates your customizations and can be installed in any Medusa application. Plugins can include modules, workflows, API routes, Admin Extensions, and more.
![Diagram showcasing how the Brand Plugin would add its resources to any application it's installed in](https://res.cloudinary.com/dza7lstvk/image/upload/v1737540091/Medusa%20Book/brand-plugin_bk9zi9.jpg)
Medusa provides the tooling to create a plugin package, test it in a local Medusa application, and publish it to NPM.
To learn more about plugins and how to create them, refer to [this chapter](../../fundamentals/plugins/page.mdx).
Refer to the [Plugins](../../fundamentals/plugins/page.mdx) chapter to learn more about plugins and how to create them.