Defining content structure on MVC sites

The content displayed on MVC sites is represented by content only pages. Ideally, developers (or administrators) set up a page structure and limit where content editors create pages. Content editors then create and model content.

Defining content structure

The structure of pages in Kentico doesn’t represent how the content is displayed on the live site. Developers fully control how content is displayed.

We recommend structuring pages in Kentico so that each page type has its own section. This makes both working with the content in the MVC application and managing and reusing the content simpler. For example:

• Root  
  • Articles
    • Article page
    • Article page
    • …
  • Store
    • Product page
    • Product page
    • …
  • …

Make sure you set up the page structure to take performance limitations into consideration. Each item (page) in the content tree shouldn’t exceed 1000 direct child pages. See general information on structuring content in Kentico.

You can also set up Kentico pages for advanced content modeling.

Limiting where content editors can create pages

You can use the following approaches to limit where in the content tree can content editors create particular content only pages.

• Allowed page type restrictions - by defining which page types content editors can place under the current page type.
• Page scope restrictions - by specifying which page types content editors can use when creating new pages under specified paths.

Using these approaches, you can set up a content structure in which each content only page type will have its own section.