# Overview of Content Types ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/structuring-content-in-contentstack/overview-of-content-types | | **course_slug** | structuring-content-in-contentstack | | **lesson_slug** | overview-of-content-types | | **markdown_file_url** | /academy/md/courses/structuring-content-in-contentstack/overview-of-content-types.md | | **generated_at** | 2026-06-08T14:32:17.833Z | > Part of **[Structuring Content in Contentstack](https://www.contentstack.com/academy/courses/structuring-content-in-contentstack)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** Overview Of Content Types - **Duration:** 6m 45s - **Media link:** https://cdn.jwplayer.com/previews/Yo2tjKM4 - **Publish date (unix):** 1755871196 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113669 kbps - video/mp4 · 180p · 180p · 179691 kbps - video/mp4 · 270p · 270p · 225852 kbps - video/mp4 · 360p · 360p · 299953 kbps - video/mp4 · 406p · 406p · 348427 kbps - video/mp4 · 540p · 540p · 486541 kbps - video/mp4 · 720p · 720p · 736025 kbps - video/mp4 · 1080p · 1080p · 1448038 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/Yo2tjKM4-120.vtt` #### Video transcript Every headline, image, and button you see on a content-stack-powered website has a hidden skeleton. That skeleton is called the content model, the master blueprint of everything your digital experience can show. Inside that model live the content types, individual molds for each kind of page or component. Think of the model as an entire Lego set while each content type is a single brick you can reuse anywhere. When the model is solid and your bricks are well-designed, your content is reusable across channels, faster to publish, consistent for every creator. If you mess up the structure, even the smallest change becomes a headache. That's why before we type a single word or upload a single image, we start with content types. Let's ground this with a simple example, a blog page. Visually, the page shows a title, a description, an image, and a publish date. In ContentStack, we capture that pattern once by building a blog page content type containing a title, which is a text field, a description, which is a multi-line text field, an image, which is an asset field, and a publish date, which is a date field. Save that schema and you've created the mold. Every new blog post is now an entry poured into the same mold, perfectly consistent every time. So creating a content type is like casting a reusable mold. Once the mold exists, anyone, a developer or marketer, can crank out perfectly shaped content without touching code. That's the magic of structured content. While developers typically create new content types, since they also need to build the front end that displays them, it's still valuable for content creators to understand how they work. Just to clarify, the front end refers to the presentation layer, like a web page or an app screen. Without that, a content type is really just a storage structure. It holds the content, but there's no way to display it. Still, knowing how content types are built helps you better understand how ContentStack works, even if you're not writing any code yourself. So let's walk through how to build one. In your stack, open Content Models and click the New Content Type button and from the menu, choose Create New. This will open the Create New Content Type dialog box. Fill in the name as Blog Page, Description, Schema for All Blog Posts, UID, Blog Icon, Blog Underscore Page. Best practice is to use lowercase with underscores, and you'll notice it auto-generates that for you. For type, choose Multiple because you want to use this content type for more than one entry. More on that a bit later. Click Save and proceed. Now let's drop in our four fields for this content type. First, Title, which is there by default, which is a single-line text box, but you're free to modify any of these default settings. Okay, let's add a multi-line text box for the description, and we can add that display name. Also, notice the ID populates for you. We'll leave the rest of the elements, like the placeholder value, instruction value, and help text empty for this demo. If you want more details on what each of those fields represent, you can hover over the question mark to get a tooltip explanation. Next, let's add a File field. Just place your cursor under the Description text field to see the Add element appear. Choose File and label it Image. This will allow us to upload images to our assets. Finally, let's add a Date field so we can capture a date using a date widget, and we can label it Date. Grab the handles on the left to arrange the fields, or click this icon to reopen the properties to make any adjustments. Finally, when you're done, click Save and Close, and then the schema is locked in. The moment we hit Save, Content Stack lets the team start adding entries. Authors focus on words and images, the structure takes care of consistency. So let's just recap some terms and what they mean. First, Field. It's a building block inside a content type, like text, assets, or dates. An asset is any media file you upload, whether it be a JPEG, PDF, or MP4. An entry is a piece of content created from a content type. UID is a unique identifier that keeps everything distinct in the system. A few best practices to keep in mind. UIDs. Keep them lowercase with underscores and under 200 characters. Examples. Use clean, human-readable names like blog page, opposed to blog page without a space. Descriptions. Spell the purpose out so team members know exactly when to use each type. You've now seen how a single content type fits into the larger content model and why that matters for speed, scale, and sanity. Again, this was more about understanding the structure behind the content model so you can better understand how Content Stack operates as you create, modify, and delete content in your stacks. #### Key takeaways - Connect **Overview of Content Types** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ## Supplement for indexing ### Content summary Overview of Content Types. Overview of Content Types in Structuring Content in Contentstack (structuring-content-in-contentstack). ### Retrieval tags - Overview - Content - Types - structuring-content-in-contentstack - lesson 01 - Overview of Content Types - structuring-content-in-contentstack lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "01" and topics: [Overview, Content, Types]. Parent course slug: structuring-content-in-contentstack. Use asset_references URLs as thumbnail hints in search results when present. Never surface LMS quiz content or assessment answers from this file. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: Overview of Content Types | `https://cdn.jwplayer.com/v2/media/Yo2tjKM4/poster.jpg?width=720` | ### External links | Label | URL | | --- | --- | | Contentstack Academy home | `https://www.contentstack.com/academy/` | | Training instance setup | `https://www.contentstack.com/academy/training-instance` | | Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` | | Contentstack documentation | `https://www.contentstack.com/docs/` |