Layout Template System Guidelines aktualisiert
parent
af26ec29de
commit
5d19789aaa
|
|
@ -3,7 +3,7 @@
|
||||||
- Our starting point is the [next.js-starter ](https://next.medusajs.com/de) template provided by medusa.
|
- Our starting point is the [next.js-starter ](https://next.medusajs.com/de) template provided by medusa.
|
||||||
- The starter template uses [medusa ui ](https://docs.medusajs.com/ui/).
|
- The starter template uses [medusa ui ](https://docs.medusajs.com/ui/).
|
||||||
- Our Layout Template System should use medusa ui as base.
|
- Our Layout Template System should use medusa ui as base.
|
||||||
- Custom Components should be built on top of medusa ui. If medusa ui does not provide a specific component, a custom component should be implemented.
|
- Custom Components should be built on top of medusa ui. If medusa ui does not provide a specific component, an independent custom component can be implemented.
|
||||||
- To look into how different medusa patterns work, there are tutorials and resources for building a[ custom storefront](https://docs.medusajs.com/resources/storefront-development).
|
- To look into how different medusa patterns work, there are tutorials and resources for building a[ custom storefront](https://docs.medusajs.com/resources/storefront-development).
|
||||||
- Do not work destructively! This means guaranteeing that the new system can still represent the starter template design
|
- Do not work destructively! This means guaranteeing that the new system can still represent the starter template design
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue