Skip to content

Commit 96fc70f

Browse files
committed
Updated Default Document Types article
1 parent 651858e commit 96fc70f

File tree

2 files changed

+35
-43
lines changed

2 files changed

+35
-43
lines changed

14/umbraco-cms/fundamentals/data/defining-content/default-document-types.md

Lines changed: 15 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -6,40 +6,34 @@ description: >-
66

77
# Default Document Types
88

9+
On this page, you will find the default Document Types in Umbraco. If you want to use these Document Types, you can create them in the Settings section.
10+
911
![Create Document Type](../images/CreateDoctype.png)
1012

1113
## Document Type
1214

13-
Creating a Document Type (without a template) defines the content structure and fields that can be used across different content items. You might use document types without templates to create consistent, structured content that doesn't require a predefined page layout. For example blog posts or product listings.
14-
15-
## Document type with template
16-
17-
Creating document types with templates allows you to define both the content structure and the visual presentation of a particular type of content item. It ensures a consistent and cohesive look and feel across your website while also enabling structured content management. This approach helps separate content from design, making it easier to manage and update your website's content and appearance independently through templates.
18-
19-
## Element Type
15+
A Document Type defines the content structure and fields that can be used across different content items. When creating a Document Type without a template, you focus solely on structured content without tying it to a specific design or layout. This is ideal for content that doesn’t require direct front-end rendering, such as reusable blocks or items managed within a headless CMS setup.
2016

21-
An Element Type is a Document Type without a template containing schema configurations for repeating a set of properties. These are for defining schema in the Block List Editor, Block Grid Editor, or other Element Type-based editors.
17+
Use a Document Type without a template for structured, reusable content like metadata schemas, settings, or components such as product details and author profiles.
2218

23-
Element Types cannot be used to create content in the Content tree. When you create an Element type, it automatically sets the **Is Element Type** flag to **True** in the **Settings** tab.
19+
## Document Type with Template
2420

25-
<figure><img src="../../../.gitbook/assets/image.png" alt="Element type"><figcaption><p>Element type</p></figcaption></figure>
21+
A Document Type with a Template combines the content structure with a predefined visual presentation. This approach links your structured content with a specific page design, ensuring a consistent and cohesive look and feel across your site. It allows you to manage content and its appearance separately, which makes updates more efficient.
2622

27-
Element Types are created using the same workflow as regular Document Types but usually contain fewer properties. You can also create Element Types as part of configuring a Block Grid or Block List Data Type.
23+
Use a Document Type with a template for pages like blog posts, landing pages, or services that appear directly on the website.
2824

29-
## Folder
25+
## Element Type
3026

31-
Folders are a special type of Document Type that can be used to organize content in the Content tree. Folders can contain other content items, such as other folders or content nodes. They are useful for organizing content in a logical hierarchy, making it easier to manage and navigate your website's content. They cannot be used to create content displayed on the front end of your website.
27+
An Element Type is a Document Type *without a template* designed for reusabale and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content.
3228

33-
## Compositions
29+
Element Types are not part of the Content tree and cannot render directly on the front end. When created, the **Is an Element Type** flag in the **Permissions** tab is automatically set to **True**.
3430

35-
Compositions provide a way to create reusable sets of properties that can be added to one or more Document Types. This can help simplify the management and consistency of content types across your website. Compositions can be used to define common properties shared across multiple Document Types, such as metadata fields or social media links.
31+
![Element Type](../../../.gitbook/assets/image.png)
3632

37-
To get started with compositions, you have to create the needed Document Types as described above. Later you can take advantage of nesting and use compositions by clicking on "**Compositions**..." option on the Document Type editor. Here you will be able to select the Document Types you want to use as compositions for the current Document Type. The fields of the selected compositions will then be available on the current Document Type.
33+
Use an Element Type when defining building blocks for complex page layouts, such as grid blocks or call-to-action sections. They are an essential part of modular content design.
3834

39-
![Create group](../images/createGroup\_new.png)
35+
## Folder
4036

41-
{% hint style="warning" %}
42-
If you create 2 compositions that contain some common properties it is only possible to pick one of the compositions in a Document Type. If preferred, those compositions that cannot be used can be marked as hidden by check marking the `Hide unavailable options`.
37+
A Folder is a special type of Document Type used solely for organizing content within the Content tree. Folders can contain other content items, such as other folders or content nodes.
4338

44-
<img src="../images/composition.png" alt="Composition" data-size="original">
45-
{% endhint %}
39+
Use a Folder to logically group related content in your Content tree, such as organizing articles by category or grouping assets for better management. This enhances navigation and keeps your content structure clean.
Lines changed: 20 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,41 +1,39 @@
1+
---
2+
description: >-
3+
On this page, you will find the default Document Types in Umbraco. If you want
4+
to use these document types, you can create them in the Settings section.
5+
---
6+
17
# Default Document Types
28

3-
On this page, you will find the default Document Types in Umbraco. If you want to use these document types, you can create them in the Settings section.
9+
On this page, you will find the default Document Types in Umbraco. If you want to use these Document Types, you can create them in the Settings section.
410

511
![Create Document Type](/15/umbraco-cms/fundamentals/data/images/CreateDoctype.png)
612

7-
## Document type
13+
## Document Type
14+
15+
A Document Type defines the content structure and fields that can be used across different content items. When creating a Document Type without a template, you focus solely on structured content without tying it to a specific design or layout. This is ideal for content that doesn’t require direct front-end rendering, such as reusable blocks or items managed within a headless CMS setup.
816

9-
Creating a Document Type (without a template) defines the content structure and fields that can be used across different content items. You might use document types without templates to create consistent, structured content that doesn't require a predefined page layout. For example blog posts or product listings.
17+
Use a Document Type without a template for structured, reusable content like metadata schemas, settings, or components such as product details and author profiles.
1018

11-
## Document type with template
19+
## Document Type with Template
1220

13-
Creating document types with templates allows you to define both the content structure and the visual presentation of a particular type of content item. It ensures a consistent and cohesive look and feel across your website while also enabling structured content management. This approach helps separate content from design, making it easier to manage and update your website's content and appearance independently through templates.
21+
A Document Type with a Template combines the content structure with a predefined visual presentation. This approach links your structured content with a specific page design, ensuring a consistent and cohesive look and feel across your site. It allows you to manage content and its appearance separately, which makes updates more efficient.
22+
23+
Use a Document Type with a template for pages like blog posts, landing pages, or services that appear directly on the website.
1424

1525
## Element Type
1626

17-
An Element Type is a Document Type without a template containing schema configurations for repeating a set of properties. These are for defining schema in the Block List Editor, Block Grid Editor, or other Element Type-based editors.
27+
An Element Type is a Document Type *without a template* designed for reusabale and repeatable set of properties. These are primarily used in editors like the Block List Editor or Block Grid Editor to create structured, nested content.
1828

19-
Element Types cannot be used to create content in the Content tree. When you create an Element type, it automatically sets the **Is Element Type** flag to **True** on the **Permissions** tab.
29+
Element Types are not part of the Content tree and cannot render directly on the front end. When created, the **Is an Element Type** flag in the **Permissions** tab is automatically set to **True**.
2030

2131
![Element type](/15/umbraco-cms/fundamentals/data/images/element-type.png)
2232

23-
Element Types are created using the same workflow as regular Document Types but usually contain fewer properties. You can also create Element Types as part of configuring a Block Grid or Block List Data Type.
33+
Use an Element Type when defining building blocks for complex page layouts, such as grid blocks or call-to-action sections. They are an essential part of modular content design.
2434

2535
## Folder
2636

27-
Folders are a special type of Document Type that can be used to organize content in the Content tree. Folders can contain other content items, such as other folders or content nodes. They are useful for organizing content in a logical hierarchy, making it easier to manage and navigate your website's content. They cannot be used to create content displayed on the front end of your website.
28-
29-
## Compositions
30-
31-
Compositions provide a way to create reusable sets of properties that can be added to one or more Document Types. This can help simplify the management and consistency of content types across your website. Compositions can be used to define common properties shared across multiple Document Types, such as metadata fields or social media links.
32-
33-
To get started with compositions, you will first have to create the needed Document Types as described above. Later you can take advantage of nesting and use compositions by clicking on "**Compositions**..." option on the Document Type editor. Here you will be able to select the Document Types you want to use as compositions for the current Document Type. The fields of the selected compositions will hereafter be available on the current Document Type.
34-
35-
![Create group](/15/umbraco-cms/fundamentals/data/images/createGroup_new.png)
36-
{% hint style="warning" %}
37-
38-
If you create 2 compositions that contain some common properties it is only possible to pick one of the compositions in a Document Type. If preferred, those compositions that cannot be used can be marked as hidden by check marking the `Hide unavailable options`.
37+
A Folder is a special type of Document Type used solely for organizing content within the Content tree. Folders can contain other content items, such as other folders or content nodes.
3938

40-
![Composition](/15/umbraco-cms/fundamentals/data/images/composition.png)
41-
{% endhint %}
39+
Use a Folder to logically group related content in your Content tree, such as organizing articles by category or grouping assets for better management. This enhances navigation and keeps your content structure clean.

0 commit comments

Comments
 (0)