Is there any reason to use external cms? #2681
Replies: 1 comment 1 reply
-
In the end, it is your call to structure your stack as you see fit, and nothing restricts you from adding CMS functionality to Medusa. To do so, you can:
You will now be able to use the custom data in your storefront. The reason for not including this in Medusa by default is that we think there are excellent CMS systems out there that do a much better job of managing content than what we can reasonably do. At the same time, using an external CMS decouples your operational commerce data from the representation layer, giving more flexibility in how you organize internal teams, build customer experiences, and evolve your tech stack as you grow. Considerations like these are typically not relevant if you are just getting started, and in such cases, it may be perfectly fine to use a simple approach that holds all your content within Medusa. Hope this is helpful :) |
Beta Was this translation helpful? Give feedback.
-
Hello, I'm configuring my medusa setup and tbh I don't really know why do headless ecommerces use external cms solutions for item descriptions. My understanding is that Medusa provides only short description and full product page should be stored with external cms. Is there any advantage to that? To me it seems like additional postgres table would avoid syncing problems, decrease deployment complexity, use much less resources etc etc. I'm sure there are reasons why it's done the way it is so here are my questions:
Thanks for any responses, I'm genuinely trying to learn more about Medusa :-)
Beta Was this translation helpful? Give feedback.
All reactions