Consulting is a fast-paced and rewarding environment, in stark contrast to the iterative and perfection-chasing product design environment. But one thing is constant and should be a top priority: Accessibility.
We at XCentium have developed a service that allows us to integrate an InsiteCommerce solution with a Salesforce Marketing Cloud. Read about what we’ve done to allow Insite to drive specific emails through Salesforce Marketing Cloud's robust email management system.
The administration console is the powerhouse of an Insite Software B2B Commerce solution. It is home to advanced configuration options for the product catalog, customer information, search options, and much more. Learn how to extend this console quickly and efficiently to add features that can increase functionality and control.
Sitecore components and placeholder are one of the main tools that allow content editors to take charge of a page, and control what a site visitor might see. It is often necessary to design components with ease-of-use, as well as re-use in mind. One of the drawbacks of the standard Sitecore placeholder is that it cannot be used multiple times on the same page; Sitecore ends up populating all instances of that placeholder with the same content. This was a problem for me in a recent project, which prompted me to create a Dynamic Placeholders extension. For this post, I will be sharing the process I went through to get Dynamic Placeholder functional in a Sitecore MVC project.
In my previous article Authentication using OpenID Connect in a Sitecore application, I have discussed the steps involved in configuring the Owin Katana Middleware. This article outlines on how we use consume this configuration to authenticate extranet anonymous users in a Sitecore MVC application using ClaimsIdentity...