# Content Types

### What are they?

This will be the fist think you do when starting to build your own website. Content Types are blue prints for the content you want to create. They allow you to define the fields (Properties) you want the website editor to complete. 

You will then display this data they have saved, [in your views on the front end of the website](broken://pages/NpZ6A9OgDAgRMm2Vw85s). If this is a new concept, I would highly recommend watching this video via the link below

{% content-ref url="/pages/yoe56LOdeAhC5sfzFIz0" %}
[Website Build Video Tutorial](/zaubercms/creating-a-website/website-build-video-tutorial.md)
{% endcontent-ref %}

### Overview

When you create a content type you are shown a blank content type, all content types must have a name. Think of the name like the name of the Blueprint you would like to use when creating content.

For example, if you are creating a website that has many similar content pages which are just a heading and some text. Then you could maybe create a content type called `Text Page` and then all those pages would use that content type. 

### Tabs

Tabs are a way to organise your properties for the editor, it saves having a long list of properties on the page.

<figure><img src="/files/LLMpiJh8elmvczwNHP6W" alt=""><figcaption><p>Tabs on an existing content type</p></figcaption></figure>

### Properties

Properties (Content Property) are the fields and components you give to an editor to be able to make the pages. Things like textboxes, date pickers, rich text editors etc... You can find the [full list of content properties here,](/zaubercms/creating-a-website/current-content-properties.md) or you can [create your own custom content property!](/zaubercms/extending-zaubercms/custom-content-property.md)

One you have added a property, you have some options in the right hand side, these are as follows

<figure><img src="/files/fsxcE2X7GKA7V6JhS5FG" alt=""><figcaption></figcaption></figure>

### System Tab/Properties

The system tab holds system properties, these are as follows

<table><thead><tr><th width="215">Property</th><th>Description</th></tr></thead><tbody><tr><td>Allowed At Tree Root</td><td>When this is ticked the content can be created at the root of the content tree, typically used for the 'Website' content</td></tr><tr><td>Is Element Type</td><td>When this is ticked is makes the content type an element type, explained below</td></tr><tr><td>Choose Allowed Views</td><td>Choose the views you would like the content page to be able to use. For example, some pages could have multiple views/layouts. Majority only have one</td></tr><tr><td>Enable List View</td><td>If you know this item is likely to have a lot of child content, if you enable a list view it shows the child items in a data grid instead of in the tree. This is a much better UI/UX for the editor than opening a tree with tons of items</td></tr><tr><td>Include Child Content</td><td>If you know you are going to display the child content in your content view, then enable this. It will pull all the children through in a single more efficient DB query than you having to manually fetch the after the page has loaded</td></tr></tbody></table>

### Audit Logs

The audit logs are just simple entries whenever there is a change on the website, so you can see which user has made what changes


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aptitude.gitbook.io/zaubercms/creating-a-website/content-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.