27 Results for Category Architecture

The landscape of business and shopping is changing!. With the help of unique Artificial Intelligence (AI) capabilities, e-commerce platforms are able to leverage the latest advancements in technology to learn about their customers and create personalized shopping experiences. One of the recent improvements in this market is voice-activated shopping using intelligent personal assistants. One of them being Amazon's Alexa, which stands out to be the most powerful and accurate voice system on the market.

In this article, I will go over my experience of integrating Sitecore Commerce application with Alexa. The integration of Alexa with Sitecore Commerce will delight the end users with a completely new way to interact with commerce applications. 

Insite has a built-in EmailService that allows a developer to easily send emails to a customer whenever they perform an action on the system. This EmailService utilizes the RazorEngine in order to parse HTML and generate rich content emails for delivery. On a recent project, I had many scenarios where an email was being sent to the customer. All of the emails contained a common look and feel, including a fully rendered header and footer. In this blog, I will go over the process I followed in order to allow for the use of the standard Layout property in the Razor template for emails.

Sitecore Commerce currently allows object extension through the use of weakly and strongly typed properties. Although the recommended development practices point to the strongly-typed approach as being preferred our experience shows that the weakly-typed should be used in the majority of the use cases. In this blog we look at the cons and pros of each approach and the reason behind the recommendation.

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.

Preface: This blog will not cover the basics of a Sitecore custom data provider. It is highly recommended to read The Black Art of Sitecore Custom Data Providers before this blog.

Often lauded by Sitecore developers is the ability to customize virtually any aspect of Sitecore. We will take a deeper look into Sitecore Custom Data providers and talk about what it takes to implement a whole new database for Sitecore.

The goal will be to have separate Sitecore database outside of Sitecore (i.e. not core, master, or web). This means that:

  1. The database has no reliance on the other databases (except perhaps core)
  2. All media items work within that database
  3. Presentation / Page preview works
  4. All layouts / sublayouts are in that database
  5. And of course all content items works