From 5d19789aaac66f321c8fcae997483c9c4d7efb38 Mon Sep 17 00:00:00 2001 From: Stephan Date: Tue, 25 Nov 2025 14:54:23 +0000 Subject: [PATCH] Layout Template System Guidelines aktualisiert --- Layout-Template-System-Guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Layout-Template-System-Guidelines.md b/Layout-Template-System-Guidelines.md index cd3cd79..d897227 100644 --- a/Layout-Template-System-Guidelines.md +++ b/Layout-Template-System-Guidelines.md @@ -3,7 +3,7 @@ - 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/). - 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). - Do not work destructively! This means guaranteeing that the new system can still represent the starter template design