---
title: Advanced content modeling
related:
  - https://docs.kentico.com/k9/developing-websites/defining-website-content-structure/page-types/creating-content-only-page-types.md
  - https://docs.kentico.com/k9/developing-websites/developing-sites-using-asp-net-mvc/developing-mvc-applications/displaying-shared-content-in-mvc-applications.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

You can use Kentico's [content only](https://docs.kentico.com/k9/developing-websites/defining-website-content-structure/page-types/creating-content-only-page-types.md) page types to build an advanced content model. This allows editors to work with shared content (reuse pages) when modeling pages. Individual pages also support [workflow](https://docs.kentico.com/k9/managing-website-content/configuring-the-environment-for-content-editors/configuring-workflows.md), [localization](https://docs.kentico.com/k9/multilingual-websites/editing-the-content-of-multilingual-websites.md) and [page-level permissions](https://docs.kentico.com/k9/managing-users/configuring-permissions/configuring-page-permissions/page-level-permissions-acls.md).

Kentico allows you to define a _Pages_ field on individual page types. Using the _Pages_ field, you can let content editors know that you expect them to reuse different pages when modeling an individual page.

For example, you can create an _Article_ page type that consists of standard fields: _Header_, _Text_, and _Image._ In addition to that, the article will consist of an _Interesting fact_ page and an _Author_ page. Both _Interesting fact_ and _Author_are just pages that editors can use to create the content of this page.

> **Info:** This approach serves mainly for modeling content by editors. If you need to create named, two-sided page relationships between pages, use [standard page relationships](https://docs.kentico.com/k9/developing-websites/loading-and-displaying-data-on-websites/displaying-data-advanced-scenarios/displaying-related-pages-using-named-relationships.md).
>
> Modeling content by adding different pages in the Pages field is not a versioned operation. Changing the model of a page under a workflow immediately reflects the changes on the published version of the page. The individual pages that editors add using the Pages can still be affected by a [workflow](https://docs.kentico.com/k9/managing-website-content/configuring-the-environment-for-content-editors/configuring-workflows.md).

## Setting up content for modeling with related pages

To allow editors to reuse pages, add the **Pages** form control to a page type:

1. In the **Page types** application, **Edit** a page type.
2. On the **Fields** tab, add **New field**:
   - Data type - Pages
   - Form control - Pages
3. Use the **Field caption**, **Field description** and **Explanation text** fields to inform content editors how you intend them to use the field. For example:
   - Field caption - Interesting Fact and Author
4. (Optional) **Select** a **Starting path**. This allows you to specify the section of the site from which editors are able to select pages.
5. **Save**.

Editors can now [use this advanced content modeling technique](https://docs.kentico.com/k9/managing-website-content/working-with-pages/modeling-content-by-reusing-pages.md) to reuse content on the **Form** tab.

Developers can display the content on the live site:

- By [accessing the data](https://docs.kentico.com/k9/developing-websites/developing-sites-using-asp-net-mvc/developing-mvc-applications/generating-classes-for-kentico-objects.md) via generated code. For example in [MVC views](https://docs.kentico.com/k9/developing-websites/developing-sites-using-asp-net-mvc/developing-mvc-applications/displaying-shared-content-in-mvc-applications.md).
- Using [listing web parts](https://docs.kentico.com/k9/developing-websites/loading-and-displaying-data-on-websites/displaying-data-advanced-scenarios/displaying-related-pages-using-named-relationships.md#displaying-related-pages-using-web-parts). The Relationship name is in the Page type (field name) format.