LibrarySites.Banner

Sitecore Standard Template: Layout Section

This blog post contains information about the fields in the Layout section of the standard template in the Sitecore ASP.NET web Content Management System (CMS) and Experience Platform (XP). For more information about the standard template and topics mentioned in this blog post, see the links in the Resources section at the end of this page.

The Layout section of the standard template contains the following fields that control how Sitecore renders an item:

  • __Renderings (Sitecore.FieldIDs.LayoutField): Often defined in standard values for data templates, this is the field in which Sitecore stores shared (unversioned/untranslated) layout details for items.
  • __Final Renderings (Sitecore.FieldIDs.FinalLayoutField): Typically defined in individual items rather than standard values, this is the field in which Sitecore stores the versioned and translated components of layout details.
  • __Renderers (Sitecore.FieldIDs.Renderers): This is the field in which an item can specify renderers (for rendering items in the context of a page generated from another item) for use by the Sitecore.Web.UI.WebControls.ItemRenderer web control or the ItemRenderer MVC renderer.
  • __Controller (Sitecore.Mvc.Names.FieldNames.Controller, which actually provides the name of the field rather than its ID): This field can specify an MVC controller to invoke when a client requests the item.
  • __Controller Action (Sitecore.Mvc.Names.FieldNames.ControllerAction, which also provides the name of the field rather than its ID): This field can specify the name of an action method in the MVC controller to invoke when a client requests the item. A value in this field makes sense only when the __Controller field has a value.
  • __Presets (Sitecore.Web.WebEditUtil.LayoutPresetsFieldId): This field can store references to preconfigured layout details that users can apply to items.
  • __Page Level Test Set Definition (Sitecore.Analytics.AnalyticsIds.PageLevelTestDefinitionField): Manages page-level tests for the item.

I cannot guess what happened to alphabetic order here. *Maybe* these are ordered by something like expected frequency of use.

Resources