Kentico Xperience Design Patterns

Learn how to maintain a clean and focused Startup.cs with a some design patterns and extension methods.

Learn how to handle a content model with optional or missing data using nullable reference types

Learn about replacing the MVC design pattern with the pattern of combining Page Templates and View Components to maintain a separation of Content and Design

Learn about the Null Object Pattern and how to use it in a Kentico Xperience application to model our content accurately

Learn why C# developers separate all their types into individual files and when it might be appropriate to do the opposite in our Kentico Xperience applications.

Learn why the Maybe Monad might be the best way to model missing data in our Kentico Xperience applications.

Learn how to maintain a clean and focused _Layout.cshtml file using Razor Partials and View Components.

Learn how to deal with failed operations in Kentico Xperience applications using centralized exception handling

Learn the problems with modeling errors as exceptions and why we should return errors from our C# methods instead

Learn why we hard code identifiers in our Kentico Xperience applications, and how to use and protect that data from deletion to guaranteed content and data quality.

Learn why we should register our Kentico Xperience dependencies where they are consumed, not where they are authored, to create more understandable code, flexible applications, and reusable libraries.

Learn how we can use the Result monad to clearly model failures and handle errors in our applications.

Learn a modern approach to defining and organizing content in Kentico Xperience, starting with Page Types.

Learn a modern approach to defining and organizing content in Kentico Xperience with Content Hierarchies.

Learn a modern approach to defining and organizing content in Kentico Xperience with Page Type restrictions.