Documentation Center

Region Schemas and Page Schemas

Use a Region Schema to define what a certain part of your Page, called a Region, can contain. A Page Schema is simply a Region Schema that defines what your entire Page (the top-level Region) can contain.

A Region Schema defines a Region, either a Page itself or a part of the Page. Regions are typically rendered as an area on the published webpage, such as a header, navigation pane, or content area.

A Page is a single top-level Region. If a Region Schema defines an entire Page, that Schema is also known as a Page Schema. The Page Schema is associated with a Page Template, so that all Pages rendered with the same Page Template are based on the same Page Schema. So by selecting a Page Template, you also select the Page Schema for the Page.

You use the Page Schema's metadata definition as the basis of your Page Metadata. The metadata fields defined in the Page Schema become the metadata fields of the Page. Only if you are working with legacy Pages that already have a Metadata Schema associated with them, select not to define metadata in the Page Schema.

The Region Schema defines the following properties of the Region:
  • Which, if any, metadata can the Region contain?
  • Can it contain Components?
  • If it can contain Components, how many can it contain and which Component Schemas and Component Templates (if used) are allowed in the Region?
  • Can it contain nested Regions, and if so, which Region Schema can each nested Region be based on?