finish sidebar changes
This commit is contained in:
@@ -14,7 +14,7 @@ A commerce module also defines data models, representing tables in the database.
|
||||
|
||||
## Commerce Modules List
|
||||
|
||||
<ChildDocs onlyTopLevel={true} type="item" />
|
||||
<ChildDocs onlyTopLevel={true} defaultItemsPerRow={2} hideItems={["Overview"]} />
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -1,27 +0,0 @@
|
||||
import { ChildDocs } from "docs-ui"
|
||||
|
||||
export const metadata = {
|
||||
title: `Plugins`,
|
||||
}
|
||||
|
||||
# {metadata.title}
|
||||
|
||||
A plugin is a package of re-usable Medusa customizations, including [modules](!docs!/learn/fundamentals/modules), [workflows](!docs!/learn/fundamentals/workflows), [API routes](!docs!/learn/fundamentals/api-routes), and more.
|
||||
|
||||
Plugins are useful if you want to re-use your customizations across Medusa applications, or you want to share those customizations with the community. You publish your plugin to NPM, then install it in a Medusa application to use its features.
|
||||
|
||||
<Note>
|
||||
|
||||
Learn more about plugins and their difference from modules in [this documentation](!docs!/learn/fundamentals/plugins).
|
||||
|
||||
</Note>
|
||||
|
||||
## Guides
|
||||
|
||||
<Note>
|
||||
|
||||
The sections in this guide help technical users build plugins in Medusa. If you're not a technical user, refer your technical team to this documentation instead.
|
||||
|
||||
</Note>
|
||||
|
||||
<ChildDocs showItems={["Guides"]} hideTitle />
|
||||
@@ -12,4 +12,4 @@ The following troubleshooting guides are intended for technical users. If you're
|
||||
|
||||
</Note>
|
||||
|
||||
<ChildDocs hideItems={["Overview"]} />
|
||||
<ChildDocs hideItems={["Overview"]} defaultItemsPerRow={2} />
|
||||
Reference in New Issue
Block a user