Medusa Hub
Medusa Hub extends Medusa.js with community solutions: plugins, starters, and practical guides. It brings together installation instructions, configuration examples, and implementation guides in one searchable place.
Start here
Why Medusa Hub exists
Medusa Hub exists to:
- explain how to install, configure, and operate community extensions,
- keep configuration examples and gotchas in one searchable place,
- provide pragmatic, implementation-focused guides.
Who it’s for
- Developers building on Medusa.js and related tooling
- Integrators / agencies implementing client projects
- Contributors who maintain or extend community packages
Who maintains it
Medusa Hub is maintained by the community. Source of truth lives in GitHub:
| Repository | github.com/codee-sh/medusa-hub |
| Issues | Report bugs or suggest improvements via GitHub Issues |
| Contributing | Open a pull request to add or update content. See the section below. |
How to contribute
You can add your own plugin, starter, or guide by opening a pull request to the medusa-hub repository.
Add a plugin
- Use the plugin template to create your documentation.
- Add a new folder under
content/medusajs/plugins/(e.g.your-plugin-name/get-started/index.mdx). - Add your plugin to the Available plugins table.
- Open a pull request with your changes.
See Plugins: Get started for requirements and the full checklist.
Add a starter
- Use the starter template to create your documentation.
- Add a new folder under
content/medusajs/starters/(e.g.your-starter-name/get-started/index.mdx). - Add your starter to the Available starters table.
- Open a pull request with your changes.
See Starters: Get started for requirements and the full checklist.
Add a guide
Guides live within plugin sections. To add a guide:
- Create a new
.mdxfile in the plugin’sguides/folder (e.g.content/medusajs/plugins/automations/guides/your-guide-name.mdx). - Add the guide to the plugin’s
_meta.jsonor_meta.jsif needed for the sidebar. - Open a pull request with your changes.
How it will evolve
- We keep docs aligned with the latest stable releases; pages include compatibility notes when relevant.
- Missing, outdated, or unclear docs are treated as a bug: report it as an issue or propose a fix via PR.
- Coverage will expand as we release more modules/plugins.
Last updated on