-
Notifications
You must be signed in to change notification settings - Fork 811
Updated Default Document Types article #6700
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.
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
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
42 changes: 20 additions & 22 deletions
42
15/umbraco-cms/fundamentals/data/defining-content/default-document-types.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,41 +1,39 @@ | ||
| --- | ||
| description: >- | ||
| 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. | ||
| --- | ||
|
|
||
| # Default Document Types | ||
|
|
||
| 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. | ||
| 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. | ||
|
|
||
|  | ||
|
|
||
| ## Document type | ||
| ## Document Type | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
| Use a Document Type without a template for structured, reusable content like metadata schemas, settings, or components such as product details and author profiles. | ||
|
|
||
| ## Document type with template | ||
| ## Document Type with Template | ||
|
|
||
| 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. | ||
| 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. | ||
|
|
||
| Use a Document Type with a template for pages like blog posts, landing pages, or services that appear directly on the website. | ||
|
|
||
| ## Element Type | ||
|
|
||
| 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. | ||
| 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. | ||
|
|
||
| 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. | ||
| 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**. | ||
|
|
||
|  | ||
|
|
||
| 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. | ||
| 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. | ||
|
|
||
| ## Folder | ||
|
|
||
| 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. | ||
|
|
||
| ## Compositions | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
|  | ||
| {% hint style="warning" %} | ||
|
|
||
| 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`. | ||
| 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. | ||
|
|
||
|  | ||
| {% endhint %} | ||
| 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. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realize this is not something you've written, but the information about the Folder is wrong.
This type of Folder is used to organize the Document Types, and not content. The Folder cannot be used anywhere else but in the Document Types structure in the Settings section. So, you could create a Folder called "Compositions" and then create all your Composition Document Types within that folder. It will have no effect on the Content what so ever, it will only serve the purpose of organizing the Document Types more neatly.
Not sure why we never caught this before 😅 But it definitely needs to be changed!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've changed the description based on your comment. Can you take a look at it? Also, the Folder section is not mentioned in the v10 and 13 articles, so I've made the changes only to v14 and 15 articles.