While the Helix architecture is a great way to organize a Sitecore solution, the principles can be applied to JSS apps too. In this post, we will be using a standard React JSS app to demonstrate how...
In this post, we’ll walk through the creation of a Reach component using the Sitecore-first workflow and following the Helix principles.
What if you have a headless site with more than one layout? We will explore how to do this in a headless application using a standard React JSS app
Kajoo version 1.1 is out! Come see the new features that we've added.
Here’s a step-by-step guide on how to create, edit, and publish a page using Sitecore Horizon
Heard the term ‘headless CMS’ and wondering what it means? Here’s a post for marketers and non-technical users to explain what headless CMSs are
In my last post, I walked through how to implement components in such a way that they could render multiple items that can be edited from the Experience Editor. In this post I’m going to explain how to use that functionality with a popular implementation of Dynamic Placeholders.
The third post in Optimizing Sitecore Experience Editor Series talks about how to develop one component to create and render multiple Sitecore Items while having those items be editable from the XPE.
This is the second post in a series on How to Optimize Sitecore Experience Editor. While the XPE can be extended through programmatic means, it’s also important to know how to use it to its potential with Sitecore’s out-of-the-box functionality.
Sitecore has many out-of-the-box features for supporting the experience editor, such as custom buttons and edit frames. However, there are also some clever ways that you can extend the experience editor.