Code, Cloud & Sitecore

It has already been passed 2 years from first Sitecore SXA version release.  It became more popular in time and reached enough maturity. We were thinking to use for a project and finally, I found an opportunity to try it.  There are already some good tutorials about using Sitecore SXA and Creative Exchange Live but I want to share my experience and give some keynotes about them, especially Creative Exchange Live. I've used these versions in my example: Sitecore Experience Platform 9.0 rev. 180604 (9.0 Update-2) Sitecore PowerShell Extensions: full 4.7.2 version (CM) Sitecore Experience Accelerator 1.7 Update-1 Setup Notes Import PowerShell Extesions before SXA package Restart the Sitecore Client and Restart the Sitecore Server before close import wizard Rebuild indexes Note: If you have a publish error, contact with Sitecore Support. I had and they provided me a patch to fix that issue. I cannot share that patch at the moment because the fix is needed...

That's true, Sitecore components are useful and provide lots of facilities. They allow to build fully flexible website. And there is not much problem using post-backs to display your contents. However, if your website has user interactions, then it could be a headache. Too many post-backs would occur a poor user experience. That's why client-side technologies are really powerful and popular for a long time. There are plenty of javascript libraries and frameworks which all try to provide better user experience in different ways. It is not a topic of this article why I chose React. There are some good articles about it (e.g. Jonne Kats' great article ). However, one of the reasons is React only focus on view part. It is not a fully framework like Angular, it is rich featured library instead. And that's what I was looking for! The idea was to benefit Sitecore server-side and React client-side power. It seems they are very good match! Let's dive into code... I...

I know it is assertive topic for first post, but maybe it is better to be assertive from the beginning! My plan is to keep here with as possible as challenging topics, discussions and experiments. Let's begin. Why Repository & Services Pattern instead of Modular Architecture? First, personal reason: I have experience with Repository & Service Pattern and not with Modular Architecture! I've recently worked for a long term custom big project (not Sitecore project), used this approach and saw its capabilities. During the development, we have faced too many requirement changes, new features etc. We could manage quite well with this approach. I couldn't see Modular Architecture capabilities for a such project yet. Second, technical perspective: Although, I haven't seen Modular Architecture capabilities on a real big project, when I have a look to Habitat and other implementations, I see some difficulties: Difficult to decide modules Big requests or requi...