World is now on Opti ID! Learn more

KhurramKhang
Jun 19, 2019
  51
(0 votes)

Best practises cheat sheet for your EPi site

  • Prefer Controllerless blocks
  • Don't Create Content Areas in Blocks, No nesting blocks.
  • Minimize database calls. Instead, use Episerver’s caching layer where ever possible.
  • Personalization might have an impact on performance, therefore make sure you implement personalization in a way that has the least possible impact.
  • Avoid frequent querying of the Dynamic Data Store.
  • Try to keep your content tree well balanced.
  • Prefer Lists over ContentArea where possible to avoid big content structures for complex pages.
  • Avoid dynamic properties.
  • Register UIDescriptor, where you disable on page edit and preview views
  • For settings kind of pages, ensure that it will not have a template
  • Use Episerver’s Object Cache instead of .NET’s built-in cache
  • Create all Content Types (Page Types, Block Types, Media Types) in code
  • For property (field) names in code, use standard .NET PascalCase. Make sure to set a friendly Display Name and Description
  • Plan a data hierarchy for Content Types, and use class inheritance
  • Organize groups of properties (fields) into tabs
  • Provide an order of properties, with frequently used properties at the top of each tab, Consider Editors
  • Set default values for Content Types’ Properties (if known)
  • For media properties, use the ContentReference type and the appropriate UIHint
  • Use the PropertyFor method to render properties (fields) in Content Type views
  • Make sure to always create the appropriate Media Types for assets in the project
  • Use Container Pages for folder nodes, without presentation (if required) use IContainerPage.
  • Plan carefully the content structure hierarchy, and avoid overloading a single level with too many pages
  • Make sure to load-test external systems integrations
  • Avoid resolving URLs repeatedly, think about cache.
  • Avoid creating blocks to use for image refernces and pages only along with some text as Alt

Disclaimer: Points have been learned from many different sources and experience, have been adding in my best practices document.

Jun 19, 2019

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |