Skip to content

Update understand-and-extend.md #7046

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Apr 29, 2025
Merged

Update understand-and-extend.md #7046

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
fe76ead
Update understand-and-extend.md
kmeilander Apr 28, 2025
2266c1b
Update understand-and-extend.md
sofietoft Apr 29, 2025
ad90979
Update understand-and-extend.md
sofietoft Apr 29, 2025
a739142
Trigger GitBook Checks
sofietoft Apr 29, 2025
773b397
Trigger GitBook Checks
sofietoft Apr 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions 15/umbraco-cms/reference/templating/modelsbuilder/understand-and-extend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,9 +110,13 @@ public partial class TextPage : PublishedContentModel, IMetaInfo

### Inheritance

In addition to composition, content types can have a parent-child relationship. In the Umbraco backoffice, a content type appears underneath its parent.
In addition to composition, earlier versions of Umbraco allowed content types to have a parent-child relationship. In the Umbraco backoffice, a content type appears underneath its parent.

By convention, a content type is always **composed of its parent** and therefore inherits its properties. However, the parent content type is treated differently, and the child content type *directly inherits* (as in C# inheritance) from the parent class.
{% hint style="info" %}
The option to add child content types in the backoffice was removed in v14. Migrated sites may still have the child content types set up. New content types can be inherited through Composition.
{% endhint %}

This type of inheritance is treated differently since the content type is always **composed of its parent**. The child content type *inherits directly* (as in C# inheritance) from the parent class.

If `AboutPage` is a child of TextPage, its generated model would inherit directly from `TextPage`:

Expand Down