I believe a lot of architects working with Sitecore ecosystem is eager to learn CM cloud, if they're not already started, while working with XM Cloud has some close enough implementation to headless implementation with XM on premise or PaaS it has some differences, a great presentation I attended in the SUGCON NA last month where Andy Cohen shared some very important tips when working with XM Cloud, in this post I will share some of my takeaways out of that session.
While we all probably know the Why XMC, here are some benefits for using XMC, like reducing the development costs, reducing the site maintenance and infrastructure costs, improving marketer productivity , having future upgrade cist avoidance and rapidly adopt new disruptive tech. we should all know what are the things that we should do or should not do when it comes to an XM Cloud implementation, so here is the list I got from session:
What are the things you should NOT do:
- DON'T customize the authoring CM Server
- DON'T make your front-end devs run a Cm container
- DON'T reference home in navigation
- DON'T create sync jobs of external content into CM
- DON'T author content in DEV.
- DON'T overlook complexity of multi-language
- DON'T Use GitFlow
- DON'T add workflow at the end
- DON'T wait until your last week to publish or Promote to Prod
- DO focus on the head, learn typescript and learn REACTJS or use the dotnet rendering SDK
- DO use your cloud CM.
- DO be careful with your content architecture
- DO use integration tools
- DO use serialization tools.
- DO use the add site language scripts of SXA
- DO Use Truck based development
- DO plan a Sprint 0
- DO consider all of your workflows front-end, backend, marketer
- DO look at the examples
- DO Publish often
- DO Go-Live with DNS switching
- DO Consider a Go-Live Plan
- DO Have Fun!
No comments:
Post a Comment