Marking Regions on a webpage
By marking Regions on a webpage, you make explicit to Experience Manager which content is allowed where on the webpage. This affects where new Component Presentations can be added, and how users can move Component Presentations around on the webpage.
About this task
For this functionality to work properly, your Page must meet the following requirements:
- Pages with a Page Schema
-
If your Page has a Page Schema, the Page Schema defines the Regions of the Page. In the Page Template, you designate various HTML containers (typically
<div>sections) as corresponding to each of the Regions using thepathproperty. - Pages without a Page Schema
-
If your Page does not have a Page Schema (a deprecated practice), the Page Template must define the Page Regions instead, specifically for Experience Manager. In this setup, the Page Template itself defines each Region, through a title, as well as through a list of one or more Component Presentation types allowed within it. A Component Presentation type is a combination of a Schema and a Component Template. That means that if two Component Presentations are of the same Component Presentation type, the Page Template must place them in the same region. Refer to the templating topics to learn more about organizing Component Presentations by Component Presentation type in your Page Template. You place the title and list of Component Presentation types in the various HTML containers (typically
<div>sections) that you want to represent each of the Regions on your Page.