Blog posts by Adnan Zameer2026-03-03T16:41:00.0000000Zhttps://world.optimizely.com/blogs/adnan-zameer/Optimizely WorldOpenAI-Driven AI Assistant for TinyMCE in Optimizely CMS 12<p>The <b><a href="https://nuget.optimizely.com/packages/a2z.optimizely.tiny.ai/" target="_blank">Tiny.AI</a></b> add-on enhances Optimizely CMS 12 by seamlessly integrating OpenAI directly into the TinyMCE editor. It empowers editors to rewrite, improve, summarize, expand, or translate selected content without leaving the CMS. Instead of copying content into external AI tools and risking formatting issues, Tiny.AI processes HTML safely and returns clean, CMS-ready output.</p><a href="https://www.adnanzameer.com/2026/03/openai-driven-ai-assistant-for-tinymce.html#more">Read more</a>2026-03-03T16:41:00.0000000ZBlog postAdvanced Form Submissions for Optimizely CMS 12 <p> Managing form submissions in enterprise Optimizely CMS installations can quickly become inefficient. While the default Optimizely Forms submission view works, it lacks flexibility, personalization, and advanced management tools. </p>
<a href="https://www.adnanzameer.com/2026/02/advanced-form-submissions-for.html#more">Read more</a>2026-02-12T13:45:00.0000000ZBlog postMaster Language Switcher for Optimizely CMS 12<p>
Managing multiple languages in <strong>Optimizely CMS 12</strong> can sometimes be challenging — especially when you need to promote a new language branch to be the <em>master language</em>.
The <strong>Master Language Switcher</strong> is a new admin tool that makes this process faster and safer by letting you <strong>switch or convert master languages</strong> for pages, blocks, and media directly at the database level.</p><a href="https://www.adnanzameer.com/2025/09/master-language-switcher-for-optimizely.html#more">Read more</a>2025-09-24T12:58:00.0000000ZBlog postPreview Unpublished Pages and Blocks on the Frontend (Optimizely CMS 12)<h3>Introduction</h3>
<p>In my <a href="https://www.adnanzameer.com/2025/09/how-to-show-unpublished-blocks-in-page.html" rel="noopener" target="_blank">previous post</a>, I explained how to customize the ContentArea rendering pipeline in Optimizely CMS 12 so editors can see unpublished block content while previewing pages in the CMS.</p>
<p>That approach works great inside the CMS UI (Edit/Preview mode). But what if you want to enable the same functionality on the <strong>front-end site</strong>, using a simple query string flag?</p>
<p>That’s where the <code>?showdrafts=true</code> parameter comes in.</p>
<a href="https://www.adnanzameer.com/2025/09/preview-unpublished-pages-and-blocks-on.html#more">Read more</a>2025-09-04T09:36:00.0000000ZBlog postShowing Unpublished Block Status in Optimizely CMS 12 ContentArea<h2>Introduction</h2>
<p>One of the most common editor complaints in Optimizely CMS is that it’s not obvious when a <strong>block inside a ContentArea</strong> has unpublished changes. By default, editors can only see those drafts if they preview the block itself (not the page that contains it). This leads to confusion, because the page looks “finished” but actually contains hidden drafts.</p><a href="https://www.adnanzameer.com/2025/09/showing-unpublished-block-status-in.html#more">Read more</a>2025-09-02T15:46:00.0000000ZBlog postHow to Show Unpublished Blocks in Page Preview (Optimizely CMS 12)<h2>Introduction</h2>
<p>
In this post, we’ll look at why Draft Blocks don’t show in Page Preview by default, and I'll show you a clean, drop-in solution to fix that.
The result? Editors get a more accurate <b>“what you see is what you’ll publish”</b> experience - no more hidden draft blocks.
</p>
<a href="https://www.adnanzameer.com/2025/09/how-to-show-unpublished-blocks-in-page.html#more">Read more</a>2025-09-01T17:41:00.0000000ZBlog postRemoving a Segment from the URL in Optimizely CMS 12 using Partial Routing<h3 data-pm-slice="1 3 []"><strong>Problem Statement</strong>
</h3>
<p>In Optimizely CMS 12, dynamically generated pages inherit URL segments from their container pages. However, in certain cases, some pages are renamed, leading to undesired URL structures. The three primary challenges faced in this scenario are:</p><a href="https://www.adnanzameer.com/2025/03/removing-segment-from-url-in-optimizely.html#more">Read more</a>2025-03-14T16:36:00.0000000ZBlog postVisitor Groups Usage Report For Optimizely CMS 12<p>This add-on offers detailed information on how visitor groups are used and how effective they are within Optimizely CMS. Editors can monitor and evaluate the interactions of various visitor groups with site content, leading to better decision-making and more focused content strategies.</p><a href="https://www.adnanzameer.com/2024/04/visitor-groups-usage-report-for.html#more">Read more</a>2024-04-18T14:57:00.0000000ZBlog postPlugin for Identifying and Bulk Deleting Orphaned Missing Properties in Optimizely<p>I am aware that the Optimizely World community has extensively discussed this topic, with numerous solutions and code snippets available to help administrators address this issue. Despite this wealth of resources, I've noticed a lack of a dedicated NuGet package specifically aimed at tackling this problem, especially for CMS 12 on the Optimizely NuGet feed. Here's my perspective on the issue and my contribution: an administrative plugin for Optimizely CMS 12.</p><a href="https://www.adnanzameer.com/2024/04/plugin-for-identifying-and-bulk.html#more">Read more</a>2024-04-11T15:34:00.0000000ZBlog postStreamlining Content Translation in Optimizely CMS with Google Translate<p>The <a href="https://github.com/adnanzameer/A2Z.Episerver.Labs.LanguageManager.GoogleTranslate" target="_blank"><b>A2Z.Episerver.Labs.LanguageManager.GoogleTranslate</b></a> extension is a valuable resource for Optimizely CMS editors seeking an alternative to the built-in Azure Cognitive Services Translator. Its main purpose is to simplify and enhance the content translation process, making it more efficient and accessible. By integrating with EPiServer.Labs.LanguageManager, it harnesses the capabilities of Google Cloud Translation. This integration is through <b>Google.Cloud.Translation.V2</b> NuGet package, enables seamless, automated translations directly within the CMS environment, enhancing the efficiency and ease of managing multilingual content.</p><a href="https://www.adnanzameer.com/2024/01/streamlining-content-translation-in.html#more">Read more</a>2024-01-23T12:39:00.0000000ZBlog postImproving Alt Text for Images within TinyMCE in Optimizley CMS<h2>Introduction:</h2>
<p>Content editors often face a tricky challenge when dealing with images within TinyMCE in Optimizley CMS. In this post, we'll explore the default options, the hurdles, and a straightforward solution to make our content more inclusive for everyone.</p>
<a href="https://www.adnanzameer.com/2024/01/improving-alt-text-for-images-within.html#more">Read more</a>2024-01-19T16:13:00.0000000ZBlog postMaximizing SEO Potential with SEOBOOST for Optimizely 12<p><a href="https://github.com/adnanzameer/optimizely-seoboost">SEOBOOST for Optimizely 12</a> has recently undergone a significant upgrade tailored for SEO enthusiasts. This enhanced tool comes with a comprehensive set of features and an updated codebase supporting .NET Core 6. Now, developers and editors have the power to shape and control their website's SEO journey.</p><a href="https://www.adnanzameer.com/2024/01/maximizing-seo-potential-with-seoboost.html#more">Read more</a>2024-01-15T18:10:00.0000000ZBlog postUpgrading to Advanced Task Manager for Optimizely CMS 12<div class="bodyDiv">
<p>I am thrilled to announce the release of <strong><a href="https://github.com/adnanzameer/optimizely-advancedtaskmanager." target="_blank">Advanced Task Manager Version 3</a></strong> for Optimizely CMS 12, a
major upgrade from the previous version designed for CMS 11 and .NET Framework 4.7.1. This release marks a
significant step forward, leveraging the power of CMS 12 and .NET Core 6 to provide an enhanced and efficient
experience for CMS editors.
</p>
<h2>Overview</h2>
<p>The <strong>Advanced Task Manager for Optimizely</strong> is a tool designed to empower CMS editors
with advanced oversight of administration tasks related to Awaiting Review in Content Approval and Change
Approval processes.
</p>
<h2>What's New</h2>
<h3>1. Migration to .NET Core 6 and CMS 12</h3>
<p>Advanced Task Manager has undergone a complete rewrite from the ground up, embracing the latest technologies. The
tool is now compatible with .NET Core 6 and Optimizely CMS 12, ensuring optimal performance and compatibility
with the latest platform advancements.
</p>
<h3>2. New User Interface</h3>
<p>The tool features a revamped user interface that not only provides a modern and intuitive experience but also
enhances the overall usability of the Advanced Task Manager. Editors will find it easier and more efficient to
manage tasks within the CMS.
</p>
<h3>3. Bug Fixes and Enhancements</h3>
<p>Version 3 includes several bug fixes and enhancements based on valuable feedback from users of the previous version. I've addressed issues and fine-tuned the tool to deliver a smoother and more reliable user experience.</p>
<h3>4. Optimized for Latest Optimizely API Requirements </h3>
<p>The entire codebase of Advanced Task Manager has been refactored to align with the latest Optimizely API requirements. This ensures seamless integration with Optimizely CMS 12, providing editors with a robust and reliable tool for their daily tasks.</p>
<h2>Installation and Configuration</h2>
<h3>Installation</h3>
<p>To install Advanced Task Manager version 3, simply add the NuGet package using the Optimizely NuGet package
manager:
</p>
<pre><code>dotnet add package AdvancedTaskManager</code></pre>
<h3>Configuration</h3>
<p>Configuration is made easy with the flexibility to adjust settings either in the <code>Startup.cs</code> file or
through the <code>appsettings.json</code> file. Here's an example with available configurations:
</p>
<pre class="brush:csharp">
public void ConfigureServices(IServiceCollection services)
{
services.AddAdvancedTaskManager(o =>
{
o.DeleteChangeApprovalTasks = true; //Default true
o.PageSize = 10; //Default 30
o.AddContentApprovalDeadlineProperty = true; //Default false
o.DeleteContentApprovalDeadlineProperty = true; //Default false
o.WarningDays = 4; //Default 4;
o.DateTimeFormat = "yyyy-MM-dd HH:mm"; //Default "yyyy-MM-dd HH:mm";
o.DateTimeFormatUserFriendly = "yyyy-MM-dd HH:mm"; //Default "MMM dd, yyyy, h:mm:ss tt";
});
OR
services.AddAdvancedTaskManager();
...
}
</pre>
OR
<pre class="brush:xml">
"AdvancedTaskManager": {
"DeleteChangeApprovalTasks": true,
"PageSize": 6,
"AddContentApprovalDeadlineProperty": false,
"DeleteContentApprovalDeadlineProperty": false,
"WarningDays": 4,
"DateTimeFormat": "yyyy-MM-dd HH:mm",
"DateTimeFormatUserFriendly": "MMM dd, yyyy, h:mm:ss tt"
}
</pre><div><br /></div><p>
The settings specified in the <code>appsettings.json</code> file will take precedence over any configurations defined in the Startup.</p><h3>Integrating Advanced Task Manager into the CMS</h3>
<p>The solution seamlessly integrates with Optimizely CMS, automatically adding administration pages to the CMS Admin menu titled <b>Adv. Task Manager</b>. The implementation of the IMenuProvider ensures the effortless inclusion of the Advanced Task Manager pages in the CMS Admin menu.</p>
<h3>Restricting Access to the Admin UI</h3>
<p>Access to the Admin UI is, by default, limited to users with the administrator's role. However, for additional flexibility, access to the <b>Adv. Task Manager</b> menu can be granted to specific roles by configuring the authorization policy during registration.</p>
<p>Example:</p>
<pre class="brush:csharp">services.AddAdvancedTaskManager(o => { },
policy =>
{
policy.RequireRole("MyRole");
});
</pre>
<h3>Overview of Features</h3>
<h4>1. Approve Entire Approval Sequence (Content Approval Only)</h4>
<p>The tool prompts editors to approve the entire Content Approval Sequence for single or multiple contents. A comment in the comment field is mandatory for enhanced communication and is already prefilled to make editors' lives easier.</p>
<h4>2. Publish Content After Approval</h4>
<p>Editors with publishing rights for content approval can now choose to publish selected content after approval, either in bulk or for individual tasks.</p>
<h4>3. Deadline Field for Content Approval Sequence (Optional)</h4>
<p>A new deadline field has been introduced for content approval, allowing editors to assign priority to content with a specified deadline. This ensures that approvers are informed about the urgency before approval.</p>
<h4>4. User Notifications Linked to the Task</h4>
<p>The tool now facilitates reading user notifications linked to the task, providing editors with deeper insights and better control over tasks and notifications.</p>
<h4>5. Task Ordering</h4>
<p>Editors now have the option to sort through all tasks with the status Awaiting Review in various columns, providing a more organized view of tasks.</p>
<h4>6. Information for Change Approval Tasks</h4>
<p>Change Approval tasks now display detailed information in an accordion-style table row, offering a clearer view of security setting changes, content movement, language setting changes, and expiration date setting changes.</p>
<h3>Conclusion</h3>
<p>Advanced Task Manager Version 3 for Optimizely CMS 12 represents a leap forward in providing editors with enhanced oversight and control over Content Approval and Change Approval processes. The new features, improved user interface, and compatibility with the latest technologies make it a valuable tool for optimizing workflows within Optimizely CMS.</p><p>The comprehensive documentation is available on the project's GitHub page <b><a href="https://github.com/adnanzameer/optimizely-advancedtaskmanager">https://github.com/adnanzameer/optimizely-advancedtaskmanager.</a></b></p></div>2024-01-03T13:48:00.0000000ZBlog postQuick Continuous Integration/Deployment (CI/CD) workflow for Episerver DXP using Azure DevOps<div class="bodyDiv"><p>There are a lot of questions on Episerver World on how to quickly deploy the code on Episerver DXP or more specifically how to set up Continuous Integration/Deployment (CI/CD) workflow for Episerver DXP. </p></div><a href="https://www.adnanzameer.com/2021/02/quick-continuous-integrationdeployment.html#more">Read more</a>2021-02-23T12:59:00.0000000ZBlog postSimple Ways to Improve Episerver Websites Security<div class="bodyDiv"> <p>In my previous post, <a href="https://www.adnanzameer.com/2021/02/basic-episerver-coding-best-practices.html" target="_blank">Basic Episerver Coding Best Practices</a> I briefly mentioned the website security. I thought I could go a little bit in details about basic security measure you can take in your ASP.NET website or in particular Episerver website. </p> <p>Each project comes with its own set of security requirements but I usually start from the following list to cover the basics. Keep in mind the list below are just suggestions and you can always opt-out or include other measures to quench your thirst for your website security. </p> <span> </span></div><a href="https://www.adnanzameer.com/2021/02/simple-ways-to-improve-episerver.html#more">Read more</a>2021-02-15T11:04:00.0000000ZBlog postBasic Episerver Coding Best Practices<h2 style="text-align: left;">A. General Coding Conventions</h2><div><h3 style="text-align: left;">Compare strings with “==” operator </h3><div>The standard C# coding practice advises that string comparison should be done with string.Equals() method, because “==” operator compares strings base on reference equality, and that could lead to unexpected behaviours. </div><div>The details can be found here: <a href="https://msdn.microsoft.com/en-us/library/cc165449.aspx">https://msdn.microsoft.com/en-us/library/cc165449.aspx</a> </div><div>Use string.Equals() method. </div><div><br /></div><h3 style="text-align: left;">Remove Unused Using Statements</h3><div> Remove all unused using statements.</div><div><br /></div><h3 style="text-align: left;">Simplify Names</h3><div>Names should be simplified (for example change String -> string, Boolean -> bool, remove leading namespace if the namespace is already declared in using statement).</div><div><ul style="text-align: left;"><li>The naming convention for methods, variables, and parameters </li></ul></div><div>Check all class to make sure the naming follows C# convention. Method and class names should follow Pascal Case, variable and parameter names should follow the Camel Case. Consider changing them for better readability and maintainability. </div><div><br /></div><h3 style="text-align: left;">High Usage of String Concatenation</h3><div>The high number of string concatenations generally leads to poor memory usage because the string is immutable. Every time a string is modified, a new instance is created in the memory and that will lead to too many call to memory allocation. To optimize memory usage on string operations, make use of StringBuilder class if there are more than a few concatenations needed in each code block. </div><div><br /></div><h3 style="text-align: left;">Move hardcoded strings to constants</h3><div>Consider moving hardcoded strings to constant classes or resource files to avoid duplication and centralize their management. Strings to process the program flow should be moved to constant, while strings used to display messages should be moved to resource files to enable localization.</div><div><br /></div><h3 style="text-align: left;">Hardcoded service’s URL and sensitive information </h3><div>There might be some places in the code which have hardcoded strings to store sensitive information like username, password, encryption key and the service’s URL. This information should be moved to the application settings file (web.config) instead. </div><div><br /></div><h3 style="text-align: left;">Move business Logic from Views </h3><div>In the principal domain, logic should go into the model or view model and application logic into the controller. Business logic in views is against MVC principal and it has serious performance implications. </div><div><br /></div><h3 style="text-align: left;">Empty files & classes </h3><div> Empty files & classes (if any) should be removed for better maintainability. </div><div><br /></div><h3 style="text-align: left;">Unused classes & methods </h3><div>Unused classes & methods (if any) should be removed for better maintainability. </div><div><br /></div><h3 style="text-align: left;">Potential code quality issues </h3><div>Special attention needs to be given for code quality issue witch regards to following </div><div><ul style="text-align: left;"><li> Variables with possible ‘System.NullReferenceException’. </li><li> Uses empty general catch class suppresses any errors </li><li> Replace with 'String.IsNullOrEmpty' </li><li> String formatting method problems </li></ul></div><h3 style="text-align: left;">Unused properties</h3><div>Remove unused properties form the blockTypes pageTypes e.t.c </div><div><br /></div><h3 style="text-align: left;">Move static methods to extension classes</h3><div>Static methods which operate on some type of data and placed across the code files and the methods are not related to the business logic of their classes should be organized as extension methods instead. </div><div><br /></div><h3 style="text-align: left;">Use View State to store large information</h3><div>Avoid using view state. Sometimes the website makes use of <a href="http://ASP.NET" target="_blank">ASP.NET</a> View State to store a certain amount of information, sometimes include large objects such as data table. Objects stored in View State are rendered to a hidden field in the HTML output of the web page, and this increases the size of the request. In case the View State gets too large, it could be blocked by proxy servers. </div><div><br /></div><h3 style="text-align: left;">Implement IDisposable</h3><div>Use where required. </div><div><br /></div><h3 style="text-align: left;">JavaScript and CSS code are embedded in razor views (.cshtml) </h3><div>Some performance gains can be achieved by minifying the embedded JavaScript and CSS inside the razor views. </div><div><br /></div><h2 style="text-align: left;">B. Episerver Best Practices</h2><h3 style="text-align: left;">Hide information not used frequently by editors </h3><div>To create pages of type “500 page”, “400 page” and so on is not the daily work for editors. It should be better to just show them to a smaller specific group that is responsible to set up the site. This can be done by restricting the access to create that page type to a certain group of editors or administrators. </div><div><br /></div><h3 style="text-align: left;">Obsolete EPiServer Class/Methods</h3><div>In each major version, old obsolete methods are removed permanently to make sure that the API is kept clean and usable over time, so even if you can postpone fixing warning messages, it is good practice to make sure all warning messages are fixed before upgrading to a major version. </div><div><br /></div><h3 style="text-align: left;">Memory leak due to constructing new DataFactory class</h3><div>DataFactory is a singleton class (which mean one instance for entire application), and it should not be constructed. In fact, EPiServer coding practice does not advice developer to use DataFactory directly, and the developer should use an injected instance of IContentRepository instead. </div><div><br /></div><h3 style="text-align: left;">EPiServer FindPagesWithCriteria problem</h3><div>Due to its lack of developer usability and relatively slow performance it's a method many developers love to hate. Under the hood, FindPagesWithCriteria builds a bunch of SQL statements that query the database directly. There is No caching when you use this. When you use FindPagesWithCriteria, you need to be careful that you don't overuse it or better avoid using FindPageWithCriteria altogether. </div><div><br /></div><h3 style="text-align: left;">Enable ContentOutputCache</h3><div>Caching can dramatically increase the performance of your website. [ContentOutputCache] you can set a much higher duration for your output cache. The cache will be invalidated as soon as an editor change the page and the visitor will see the updated information. ContentOutputCache attribute is commented out in Page controllers.</div><div><br /></div><h3 style="text-align: left;">Use inline Blocks instead of custom properties</h3><div>Its easier to manage and localize blocks instead of custom properties. Create inline Blocks e.g for CTA any settings <b>AvailableInEditMode = false </b></div><div><br /></div><h3 style="text-align: left;">Overuse of ServiceLocator</h3><div> To create objects with the service locator cost more than a normal creation with the “new” operator. So, performance gains can be archived if the ServiceLocator is just used once for a page view. </div><div><b>Example</b></div> <pre class="brush:csharp"> <br />public class DummyBlockController : BlockController<DummyBlock><br />{<br /> public override ActionResult Index(DummyBlock currentBlock)<br /> {<br /> var startPage = ServiceLocator.Current.GetInstance<IContentRepository>().Get<StartPage>(ContentReference.Stat…<br /> var dummySites = ServiceLocator.Current.GetInstance<IContentRepository>().GetChildren<ContentPage>(startPage…<br />…<br /> foreach (var site in dummySites)<br /> {<br /> var careerPages = ServiceLocator.Current.GetInstance<IContentRepository>().GetChildren<SamplePage>(site.C…<br /> </pre> <h3 style="text-align: left;">The Problems with Service Locator</h3><div>Using the snippet of code above is all very good but, in a project, you might have multiple files that need to call IContentRepository. Having this code duplicated also means you will need to write the same tedious set-up code in your unit tests everywhere. </div><div><br /></div><div>EPiServer also provides an alternative way of injecting dependencies into your code, via property injection and constructor injection. Injected<> uses property injection via the IoC container to give you access to your dependencies.</div><div>An example of how to use <b>Injected<> </b>can be seen below:</div><div><pre class="brush:csharp"> <br /> public class DummyExample<br />{<br /> internal Injected<IInterface> interface;<br /> public DummyExample()<br /> {<br /> var implmentation = interface.Service;<br /> }<br />}<br /> </pre> Injected is useful when you need to implement from things like ISelectionFactory or an InitializationModule. If you try to use constructor injection in these types of files, MVC will complain about not having a parameterless constructor. <div><iinterface><br /></iinterface></div><div><iinterface>EPiServer supports constructor injection for controllers. It is possible to inject dependent objects in your EPiServer controllers if you have <a href="/link/8df6f239e3fa44b99f475adb8e5cf26c.aspx" target="_blank">configured it properly</a> - created MVC dependency resolver. </iinterface></div><div><iinterface><br /></iinterface></div><div>Try to minimize the construction of objects when using the ServiceLocator or better use Injected or constructer injection. </div><div><br /></div><h3 style="text-align: left;">Implement EPiServer Schedule Jobs Stop Signal </h3><div>Stop signal in EPiServer Schedule Jobs should be periodically checked (in a loop for example) so that the execution can be terminated a short time after if the stop signal has been received. </div><div>Periodically check the stop signal in the longest-running code block (the loop). Stop the execution if the stop signal has been received.</div><div><br /></div><h3 style="text-align: left;">Overuse of PageTypes</h3><div>Overuse of PageTypes in the system, resulting in code duplication. The ideas of using block types in EPiServer to reduce code duplication and rely on fewer page types. If multiple pages serve the same layout but different content, there should be one-page type and different blocks should be created to serve different content.</div><div>Use abstract class if there is a need for same looking multiple PageTypes.</div><div><br /></div><h3 style="text-align: left;">Unused PageTypes</h3><div>It is important to keep the CMS clean and it is recommended to clean up the system from the unused page and block types. </div><div><br /></div><h3 style="text-align: left;">EPiServer Translation </h3><div>EPiServer platform provides the flexibility of translating the hard-coded strings to multiple languages with resource XML files. Currently, the content type names, property names, descriptions and label texts on the pages are hardcoded with fixed strings. The values should be taken from the resource XML files instead, as this would better support a global website with multiple languages. </div><div><br /></div><h3 style="text-align: left;">Overuse of Block Controllers</h3><div>Simple blocks without processing logic inside their controllers should not have dedicated controllers as this will degrade the performance. </div><div><ul style="text-align: left;"><li><b>Avoid dynamic properties.</b></li><li><b>Register UIDescriptor, where you disable on-page edit and preview views </b></li><li><b>For settings kind of pages, ensure that it will not have a template </b></li><li><b>Use Episerver’s Object Cache instead of .NET’s built-in cache </b></li><li><b>For property (field) names in code, use standard .NET PascalCase. Make sure to set a friendly Display Name and Description </b></li><li><b>Set default values for Content Types’ Properties (if known) </b></li><li><b>For media properties, use the ContentReference type and the appropriate UIHint </b></li><li><b>Use the PropertyFor method to render properties (fields) in ContentType views </b></li><li><b>Use Container Pages for folder nodes, without presentation (if required) use IContainerPage. </b></li></ul></div><div><br /></div><h2 style="text-align: left;"> C. EPiServer Best Practices for Cloud Development & Deployment</h2><h3 style="text-align: left;">Replace log4net with EPiServer.Logging </h3><div>Episerver DXC redirects all Episerver logs into .NET Diagnostic Trace if the code uses the Episerver logging abstraction <a href="/link/55fe410f4f65482cab72fb59d47c7561.aspx?documentId=cms/10/8EBB557B" target="_blank">EPiServer.Logging.LogManager.</a> As the application is using log4net and deploying to DXC, replace log4net with EPiServer.Logging.</div><h4 style="text-align: left;">Reference: </h4><div><a href="https://world.episerver.com/digital-experience-cloud-service/development-considerations/ " target="_blank">https://world.episerver.com/digital-experience-cloud-service/development-considerations/ </a></div><div><a href="https://world.episerver.com/documentation/developer-guides/CMS/logging/logging-into--net-diagnostics-trace/ " target="_blank">https://world.episerver.com/documentation/developer-guides/CMS/logging/logging-into--net-diagnostics-trace/ </a></div><div><br /></div><h3 style="text-align: left;">Keep a look at system requirements</h3><div>Some of the EPiServer Add-ons, features or components are not compatible with Microsoft Azure, and it is recommended to keep a look at the system requirements of EPiServer Azure deployment to select appropriate add-ons, components or to choose a suitable approach of development.</div><div><br /></div><div> Take a look at EPiServer Azure (DXC) system requirements, remove incompatible add-ons, features and components. The system requirements are available at this reference link: <a href="http://world.episerver.com/digital-experience-cloud-service/requirements/ " target="_blank">http://world.episerver.com/digital-experience-cloud-service/requirements/ </a></div><div><br /></div><h3 style="text-align: left;">Avoid code that depends on specific on-premise resources </h3><div> Code that was developed to run on a cloud website should not have any specific dependency on the on-premise resources, such as SMTP server, writing to local files and folders. Session state should be avoided, and if it is impossible to avoid the use of session state, Azure Session Affinity or other optimized session state providers for Azure should be considered.</div><div><br /></div><div>Try to avoid any code that depends on specific on-premise resources, consider alternative options for them in Azure environment (for example, emails can be sent from SendGrid service, any logic which writes to the local files/folders should now use Azure Blob Storage instead) </div><div><br /></div><h3 style="text-align: left;">Security </h3><div>Read the following documentation for the level of security EPiServer provides <a href="/link/87efea613e1d4e0392a8287250315168.aspx">https://world.episerver.com/documentation/developer-guides/CMS/security/</a></div><div> </div><div> It is recommended some level of protection should be there in the website against click-jacking. </div><div><br /></div><div> Install and configure the NuGet package called NWebsec (<a href="https://www.nuget.org/packages/NWebsec">https://www.nuget.org/packages/NWebsec</a>)</div></div></div>2021-02-08T11:28:00.0000000ZBlog postBasic Episerver Coding Best Practices<div class="bodyDiv">This is my first post on Episerver development best practices. In this one, I'll present the best practices that should be followed while working with Episerver - ASP.Net MVC framework. <div>Here are some best practices you should always have in mind:</div><div><br /></div></div><a href="https://www.adnanzameer.com/2021/02/basic-episerver-coding-best-practices.html#more">Read more</a>2021-02-08T11:28:00.0000000ZBlog postAdvanced Task Manager: Gadget for Administration of Awaiting Review Tasks in Episerver<div class="bodyDiv">Currently, the User notification and Tasks (Awaiting Review) are disconnected and provide very basic information to the editors.<br /><br /><img alt="Tasks pane" src="https://github.com/adnanzameer/AdvancedTaskManager/raw/master/assets/docsimages/image001.png" /><br /><br /><img alt="User notification" src="https://github.com/adnanzameer/AdvancedTaskManager/raw/master/assets/docsimages/image003.png" /><br /><br />The idea behind this project is two-fold. The first purpose is to build a more versatile Content Approval Sequence (Awaiting Review) task management gadget to extend the information available to the editors. The second purpose is to combine user notifications with tasks and empower Content Approvers to act on their tasks within a single interface.<br /></div><a href="http://www.adnanzameer.com/2020/01/advanced-task-manager-gadget-for.html#more">Read more</a>2020-01-14T09:55:00.0000000ZBlog postAdvanced Task Manager: Gadget for Administration of Awaiting Review Tasks in Episerver<div class="bodyDiv">Currently, the User notification and Tasks (Awaiting Review) are disconnected and provide very basic information to the editors.<br /><br /><img alt="Tasks pane" src="https://github.com/adnanzameer/AdvancedTaskManager/raw/master/assets/docsimages/image001.png" /><br /><br /><img alt="User notification" src="https://github.com/adnanzameer/AdvancedTaskManager/raw/master/assets/docsimages/image003.png" /><br /><br />The idea behind this project is two-fold. The first purpose is to build a more versatile Content Approval Sequence (Awaiting Review) task management gadget to extend the information available to the editors. The second purpose is to combine user notifications with tasks and empower Content Approvers to act on their tasks within a single interface.<br /></div><a href="http://www.adnanzameer.com/2020/01/advanced-task-manager-gadget-for.html#more">Read more</a>2020-01-14T09:55:00.0000000ZBlog postAdvanced Task Manager: Gadget for Administration of Awaiting Review Tasks in Episerver<div class="bodyDiv">Currently, the User notification and Tasks (Awaiting Review) are disconnected and provide very basic information to the editors.<br /><br /><img alt="Tasks pane" src="https://github.com/adnanzameer/AdvancedTaskManager/raw/master/assets/docsimages/image001.png" /><br /><br /><img alt="User notification" src="https://github.com/adnanzameer/AdvancedTaskManager/raw/master/assets/docsimages/image003.png" /><br /><br />The idea behind this project is two-fold. The first purpose is to build a more versatile Approval Sequence task management gadget (for Content & Change Awaiting Review tasks) to extend the information available to the editors. The second purpose is to combine user notifications with tasks and empower Approvers to act on their tasks within a single interface<br /></div><a href="https://www.adnanzameer.com/2020/01/advanced-task-manager-gadget-for.html#more">Read more</a>2020-01-14T09:55:00.0000000ZBlog post