|
2 | 2 |
|
3 | 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. |
4 | 4 |
|
5 | | - |
| 5 | + |
| 6 | + |
| 7 | +## Document type |
| 8 | + |
| 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. |
6 | 10 |
|
7 | 11 | ## Document type with template |
8 | 12 |
|
9 | 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. |
10 | 14 |
|
11 | | -## Document type |
| 15 | +## Element Type |
12 | 16 |
|
13 | | -Creating a Document Type (without a template) is about defining the content structure and fields that can be used across different content items. You might use document types without templates for creating consistent, structured content that doesn't require a predefined page layout. For example blog posts or product listings. |
| 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. |
14 | 18 |
|
15 | | -## Compositions |
| 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. |
16 | 20 |
|
17 | | -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. |
| 21 | + |
18 | 22 |
|
19 | | -When using a mixed setup, you can take advantage of nesting and use compositions by clicking on "**Compositions**..." option. |
| 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. |
20 | 24 |
|
21 | | - |
22 | | -{% hint style="warning" %} |
| 25 | +## Folder |
23 | 26 |
|
24 | | -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 checkmarking the `Hide unavailable options`. |
| 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. |
25 | 28 |
|
26 | | - |
27 | | -{% endhint %} |
| 29 | +## Compositions |
28 | 30 |
|
29 | | -## Element Type |
| 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. |
30 | 32 |
|
31 | | -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. |
| 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. |
32 | 34 |
|
33 | | -Element Types cannot be used to create content that resides in the Content tree. When you create an Element type, it automatically sets the **Is Element Type** flag to **True** on the **Permissions** tab. |
| 35 | + |
| 36 | +{% hint style="warning" %} |
34 | 37 |
|
35 | | - |
| 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`. |
36 | 39 |
|
37 | | -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. |
| 40 | + |
| 41 | +{% endhint %} |
0 commit comments