Raygun Crash Reporting [https://raygun.com/platform/crash-reporting] is an automated error tracking solution that provides insight into your application through various APIs. These APIs easily integrate with .NET and more specifically Sitecore. There are a number of guides on the Raygun website [https://raygun.com/documentation/language-guides/dotnet/crash-reporting/
Sitecore Experience Forms formerly known as Web Forms for Marketers (WFFM) allows Content Authors to construct web forms that record and report information provided by contacts on a website - ideally without the need for additional development. The integrated nature of Sitecore Experience Forms requires some pipeline and HTTP life-cycle
Since the introduction of xConnect there have been hundreds (if not thousands) of articles, posts and blogs covering the who/what/when/where and wtf? is wrong with xConnect. Many of these articles focus on xConnect setup or issues with the application accessing the certificates from a given certificate store.
It's a well known fact that Sitecore uses an old and somewhat customised [https://www.dictionary.com/browse/bastardize] version of log4net. This can make integrations with other libraries such as Sumo Logic [https://github.com/SumoLogic/sumologic-net-appenders] difficult as the log4net APIs have changed. To work around
With the release of Sitecore 7.5, Sitecore changed their underlying architecture and introduced MongoDB. While this improves the performance of Experience Analytics (formerly Sitecore Analytics), it has brought with it a new set of challenges. The new architecture persists all user interactions into Session until the session ends at
The Sitecore Active Directory module provides integration between one or more Active Directory domains and Sitecore. Out-of-the-box this module supports reading and writing of data types such as: string, int and bool, however a common Active Directory data type byte is not supported. Sitecore only deals with string types regardless
When working with Bootstrap it can sometimes be difficult to determine the active breakpoints for a given screen width. The simplest solution is to add a breakpoint helper to your document and configure it using the standard Bootstrap visibility classes. The example below uses the badge class, however any visual