Skip to main content
Optimizely Academy
End-user eLearning
Events
Certification
Partner training
Community
All Topics

Supporting Governance

  • By Optimizely Education
  • Published: Mar 13, 2026
  • Rating
    Average rating: 0 No reviews

Outline
At a glance
  • Predictability: Using conventions to create a shared mental model for developers and editors.
  • Atomic Design: Building reusable atoms (blocks) and orchestrating them via ContentAreas.
  • Visual Alignment: Syncing components with the Visual Builder paradigm in CMS 13.
  • Scale: Protecting long-term scalability through GUIDs, interfaces, and logical UI grouping.

In the enterprise lifecycle of an Optimizely CMS 13 (PaaS) implementation, the initial launch is only the beginning. The true test of a developer’s skill is the ability to build a system that remains maintainable years after the first line of code is written. Sustainability is achieved through Governance via Conventions.

1. The Component-Based Baseline: Atomic Design in CMS

The transition from Page-centric to Block-centric authoring is the foundation of structural governance. In CMS 13, every functional UI element should be evaluated for its potential as a reusable block. This reduces "Don't Repeat Yourself" (DRY) violations in your codebase and database.

Strategy of Discrete Blocks:

  • Encapsulation: Business logic lives inside the block’s controller or service.
  • UI Reusability: Styling resides in single partial views or display templates.
  • Content Globalism: Shared blocks allow one-to-many updates across the entire site instantly.

2. Optimizely Coding Conventions: The Invisible Guardrails

Conventions are the unwritten laws that ensure project stability. Senior developers must enforce strict naming and identity patterns across the solution to prevent technical debt.

Naming Conventions and Type Safety

Standardizing names allows the CMS to naturally organize itself. Always prefix functional interfaces with "I" and use abstract base classes like SitePageData to host global properties like SEO or tracking IDs.

[ContentType( GUID = "FD32...", DisplayName = "Standard Page", Description = "Core narrative page type.")] public class StandardPage : SitePageData { // GUID is critical for refactoring resilience }

3. Reusable View Strategy: Partials and Tags

Governance extends into the presentation layer. Use Tags to provide multiple layouts for a single data model. This prevents "Content Area Fragmentation" where editors must choose unique blocks just for visual variation.

Implementation Workflow:

  1. Create a default view (Block.cshtml).
  2. Define a tagged view (Block_Narrow.cshtml).
  3. Use [TemplateDescriptor] to register the variation.

4. Property Governance via UI Metadata

How properties are organized in the UI directly impacts editor accuracy. Disorganized tabs lead to "Editorial Blindness." Large sets of properties should be logically grouped using the GroupName parameter.

[Display( Name = "Teaser Image", GroupName = SystemTabNames.Content, Description = "Hover tooltip for editors.", Order = 100)] [UIHint(UIHint.Image)] public virtual ContentReference TeaserImage { get; set; }

5. Visual Builder Alignment in CMS 13

The Visual Builder paradigm shift requires components to be truly composable. Governance here means ensuring that components have high-quality previews and using [AllowedTypes] to control nesting hierarchies within visual layout components.

Design-Dev Handover

Ensure your logical naming in the CMS (e.g. "Hero Heading") matches the Layer names in the Design System (Figma). This creates a "Living Configuration" that reduces editorial onboarding and confusion.

6. Backend Data Governance with Graph

Use the Conventions API in Startup.cs to automate how data is presented to external APIs. This ensures that technical metadata or internal fields are never exposed during headless delivery, maintaining a clean and secure public schema.

Conclusion

Supporting governance in Optimizely CMS 13 is an exercise in technical foresight, requiring developers to build a foundation of reusable components and strict coding conventions that guide editorial behavior without stifling creativity. By mastering strategies such as GUID-based content identification, interface-driven whitelisting, and the application of tagged partial views and display templates, you create a system that is resilient to design shifts and scalable for multi-channel delivery. As you finalize your preparation for the PaaS CMS 13 Developer Certification, recognize that your role as a "Convention-First" developer is vital for ensuring that the CMS remains a high-performance, accessible, and governed source of truth for the entire digital organization.