I’ve ended my previous post I’ve mentioned that I would add redux in a Sitecore-ReactJS mix. That is what I’m going to talk about in this post. Continue reading “How to marry ReactJS and Sitecore with Webpack – Part 2. Adding Redux”
There were a few posts on the internet on how to integrate front-end code into a Sitecore solution. It all started with a post from Alex Shyba. Back in February, he describes the general concept of an integration. Then Richard Seal created a module for Sitecore that allow you to use jsx renderings in Sitecore.
I was trying to solve a problem of an HTML handover between front-end and Sitecore developers for a while. Finally, I was able to play with ReactJS and Sitecore by myself and here is what I end up doing.
Our port of Sitecore Reference Storefront finally passed all internal checks and got open sourced on EPAM’s GitHub account right before Sitecore SYM 2016.
Fell free to dig in and answer your questions in comments, social networks or in person during the Symposium (you will be able to find near an EPAM booth during breaks)
As I’ve mentioned in the previous post, I’m this one is going to be dedicated for one of the features. I think that it make sense to start from a catalog, as an e-commerce implementation will heavily rely on products information all over the site.
Let’s dive into … Continue reading “Sitecore Catalog Feature for Habitat”
I’ve been working a lot on Sitecore development infrastructure recently and package management is one of the areas, particularly NuGet.
Unfortunately, Sitecore doesn’t provide any feed that you could use right away. so carrying over Sitecore DLLs in a repository is a standard practice that I’ve seen for few years and actually been using.
So I decided to create my own packages and here how I did it.
In my previous post, I’ve described the benefits of composition pattern over inheritance in code generation and mentioned that it simplifies restoration of models from reflection. From my point, this is a huge plus as it enables the creation of developer friendly modular architecture in Sitecore.
I do not think that someone still has problems with a creation of an update package with Sitecore config transforms, but it is not really possible to install an update package in your Visual Studio solution. Of cause, you can install it in Sitecore, grab all libraries from bin folder and copy to your source, then serialize installed items into your project, generate your models based on “everything” you have in Sitecore.
To me, it doesn’t sound like a good approach, moreover, there are many of solution like NuGet, npm, bower that drastically simplify package management and installation for development. Also, when referencing items from packages, you don’t expect to modify DLL coming with them, so I do not think that you should have to serialize Sitecore items to use them in your model generation.
Most likely you already have information about your templates in compiled into your module DLLs. Below you would see how you could use it.