I recently became Coveo For Sitecore certified and would like to share my experience. Additionally, I would like to offer exam tips to others who are seeking to become certified themselves.


Starting with Sitecore version 9, developers can interact with the Sitecore Experience Database (xDB) using xConnect. xConnect is a OData based service layer that allows communication with xDB data. Any trusted client can leverage xConnect Client API which exposes rich capabilities to search, read, and write contacts and interactions data. In this blog, I want to look at the details on how to instantiate xConnect Client in a non-Sitecore context. One of the reasons you would want to do this is if you need to extract xDB data into another system or application.


Over a year ago, I wrote a piece on trends driving CPG Commerce Growth that I feel needs to be revisited. The catalyst for circling back on this topic comes from a recent report published by Jumpstart related to the “CPG eCommerce Landscape."  My primary theme in the original blogs was three-fold: sell direct, collaborate with retailers and sell via marketplaces. Those recommendations still hold, but Jumpstart’s report highlights through hard facts how CPG brands should optimize these recommendations. Bottomline, they highlighted CPG purchases online have grown 22% since 2017, but most of that growth occurred in 2018. Year-over-year growth in 2019 to date has slowed to around 3%. This pushes a strategy to balance CPG sales for D2C, through retailers, and marketplaces. Let’s give a little context first on what I recommended initially.


If you’ve heard of the term “decorators” or spotted them in code snippets, but still aren’t sure what they do - then this post is for you. In this post I’ll attempt to demystify what decorators are as well as how they can be useful.


Recently, a co-worker pinged me asking about the best way to handle transforms in a Sitecore 9+ PaaS environment. My response: "Transforms are the devil, and there are often zero reasons why you need them in a new Sitecore environment." Sitecore, of course, gives us rules-based configurations out of the box, which give us a lot of control over applying different configurations for different roles and environments, but what about modifications to the web.config? In my experience, most changes to the web.config are "one-time" changes that you can make (and document) as soon as an environment is provisioned. This includes managing assembly binding redirects, which is often something that changes each time you add a new NuGet reference to your project. Read on to learn how you can externalize your assembly binding redirects, instead of having to maintain a copy of the web.config file and/or transforms.


SEARCH ARTICLES