# Structuring Content in Contentstack ### About this export | Field | Value | | --- | --- | | **content_type** | course | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/structuring-content-in-contentstack | | **language** | en | | **product_area** | Contentstack Academy | | **learning_path** | cms-content-manager-certification | | **course_id** | structuring-content-in-contentstack | | **slug** | structuring-content-in-contentstack | | **version** | 2026-03-01 | | **last_updated** | 2026-06-08 | | **status** | published | | **keywords** | ["Contentstack Academy"] | | **summary_one_line** | This course gives you a clear, practical understanding of how content is structured inside Contentstack—and why that structure is the backbone of scalable digital experiences. You’ll learn how content models act as bluep… | | **total_duration_minutes** | 26 | | **lessons_count** | 6 | | **video_lessons_count** | 6 | | **text_lessons_count** | 0 | | **linked_learning_path** | cms-content-manager-certification | | **linked_assessment_ref** | LMS_UNCONFIGURED_COURSE_ASSESSMENT | | **markdown_file_url** | /academy/md/courses/structuring-content-in-contentstack.md | | **generated_at** | 2026-06-08T14:32:17.820Z | | **intended_audience** | [] | | **prerequisites** | [] | | **related_courses** | [] | > **Academy MD v3** — companion `.md` for Ask AI. Quizzes and graded assessments are **LMS-only**; this file never contains answer keys. ## Course Overview | Metadata | Value | | --- | --- | | Catalog duration | 26m 2s | | Released (if known) | 2026-03-01 | | Product area | Contentstack Academy | ### Description This course gives you a clear, practical understanding of how content is structured inside Contentstack—and why that structure is the backbone of scalable digital experiences. You’ll learn how content models act as blueprints, how content types serve as reusable molds, and how fields shape every entry you create. We’ll cover the essentials: * **Content Types** * **Fields** * **Labels** Through real-world examples like building a blog page, you’ll see how structured content speeds up publishing, improves consistency, and makes collaboration easier across teams. By the end, you’ll understand how content models connect the backend structure with the frontend experience, and how to work smarter with Contentstack—whether you’re a content creator, or editor. ### Learning objectives 1. Follow each lesson in order. 2. Practice in a training stack using placeholders **YOUR_STACK_API_KEY** and **YOUR_DELIVERY_TOKEN** in local `.env` files only. 3. Validate API responses against the official documentation. ### Topics covered Contentstack Academy ## Course structure ```text structuring-content-in-contentstack/ ├── 01-overview-of-content-types · video · 405s ├── 02-understanding-content-type-classification · video · 207s ├── 03-why-labels-matter · video · 244s ├── 04-fields-in-contentstack · video · 317s ├── 05-advanced-fields-in-contentstack · video · 222s ├── 06-why-content-models-matter · video · 167s ``` ## Lessons ### Lesson 01 — Overview of Content Types #### 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. ### Lesson 02 — Understanding Content Type Classification #### Video details #### At a glance - **Title:** Content Type Classification - **Duration:** 3m 27s - **Media link:** https://cdn.jwplayer.com/previews/gIA0aMT1 - **Publish date (unix):** 1755877030 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113821 kbps - video/mp4 · 180p · 180p · 208740 kbps - video/mp4 · 270p · 270p · 279266 kbps - video/mp4 · 360p · 360p · 396402 kbps - video/mp4 · 406p · 406p · 470535 kbps - video/mp4 · 540p · 540p · 692475 kbps - video/mp4 · 720p · 720p · 1087118 kbps - video/mp4 · 1080p · 1080p · 2236361 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/gIA0aMT1-120.vtt` #### Video transcript So, we know how to structure content using content types, but not all content types are created equal. Some are designed for one-off pages like your homepage or privacy policy, and others are built to generate dozens or hundreds of pages using the same layout. And some content types aren't even pages at all. They're just reusable components like headers and footers, or in the case of our blog example, author bios or categories. Understanding how to classify a content type correctly is essential. It impacts not just how you create content, but also how developers build and connect your front end. InStack classifies content types into three categories, single page component, multiple page component, and reusable components, which are set up the same way as a multiple page component, but use a reference field. A single page component is used for one-off pages that each have a unique structure. These pages are standalone. There's only one of them on your site. Again, examples include a homepage, an about us page, or a privacy policy. When you create this type, simply choose single during setup. A multiple page component is built when you need to reuse the same structure across many entries like blog posts or product pages. These pages share the same layout, but the content inside changes. Again, examples include blog pages, product pages, or something like case studies. When creating the content type, select multiple. This tells Content Stack you'll be adding multiple entries under the same schema. Not every content type represents a page. Sometimes you need a reusable piece of content, like an author or category, that can be referenced inside of other entries. These are called multi-reusable components. You still select multiple when creating the content type, but the key difference is that you'll use them in combination with reference fields inside of other types. Examples include author profiles for things like blog posts, or categories for products, or maybe something like testimonials for landing pages. Some quick reference tips to keep in mind. Use single for one-off pages like Home or Contact Us. Use multiple for repeatable pages like blogs or products. And use multiple and the reference field for reusable content like authors or categories. Making the right choice here helps you ensure your content is flexible, scalable, and easy to maintain. Now that you know the different types of content structures, you're ready to start creating smarter, more organized content. #### Key takeaways - Connect **Understanding Content Type Classification** 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. ### Lesson 03 — Why Labels Matter #### Video details #### At a glance - **Title:** Why Labels Matter - **Duration:** 4m 4s - **Media link:** https://cdn.jwplayer.com/previews/Kvlijm90 - **Publish date (unix):** 1755871309 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113846 kbps - video/mp4 · 180p · 180p · 160035 kbps - video/mp4 · 270p · 270p · 191991 kbps - video/mp4 · 360p · 360p · 242102 kbps - video/mp4 · 406p · 406p · 271269 kbps - video/mp4 · 540p · 540p · 358390 kbps - video/mp4 · 720p · 720p · 514461 kbps - video/mp4 · 1080p · 1080p · 940270 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/Kvlijm90-120.vtt` #### Video transcript As your stat grows, so does your list of content types, and before long, finding what you need can feel like scrolling through an endless spreadsheet. Labels are ContentStack's way of keeping things organized. Think of them as like folders, letting you group content types in ways that make sense to your team. Whether you're in marketing, editorial, or product, labels make it easy to navigate, collaborate, and keep content structured across teams. Let's say you've got two teams, marketing with content types for campaigns and pages, and writers with content types for blogs and authors. Instead of dumping everything into one giant list, you can create two labels, marketing and writers, and assign the appropriate content type to each. It's simple but powerful, and it keeps your workspace clean. Here's what labels don't do. They don't affect user permissions, they don't change how your content appears on the front end, and they don't impact your entries directly. But what they do is make it easier to browse, filter, and manage your stack, especially as your content library scales. Let's walk through how to create and apply labels. Notice I'm working in the Compass Travels site. First, navigate to the Content Models section. At the top of the panel, click the plus icon to create a new label. Name this one Page and click Create. Next, we'll apply this label to different content types. I'll select the Landing Page type to enter it. In the top right, I can access the Apply Label menu and I'll select Page. Then I'll save the content type. Returning back to the content types, I'll do this for one more content type. I'll click the Article Listing page and use the same method to apply the page label. Then I'll click Save. Returning back to the content types, notice the Page label on the left. When you click it, the Content Types list gets filtered to show you just the types with that label. But it doesn't stop there. Switch over to the Entry section and you'll notice a Content Type View section on the left. Select the Group by Labels option to see your labels. You can expand that section to see the two content types labeled as Page. Now, what if you want to edit or delete a label? In the Content Models panel, click the Labels Settings icon. From here, you can either create new labels by clicking the plus sign. I'll close out of this for now as I don't want to create a new one. You can modify existing ones by clicking the pencil icon. Or you can delete labels you no longer need by clicking the trash can. Some best practices to keep in mind. Use label names that are intuitive to your team. Align on a shared structure. Don't let every user create their own. You can leverage nested labels for clarity. For example, you could nest blog posts under your Pages label. Keep labels focused on usability, not hierarchy. They're about making things easier to find, not controlling access. Labels don't change how your content works, but they make a huge difference in how you work with the content. #### Key takeaways - Connect **Why Labels Matter** 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. ### Lesson 04 — Fields in Contentstack #### Video details #### At a glance - **Title:** Fields In Contentstack - **Duration:** 5m 17s - **Media link:** https://cdn.jwplayer.com/previews/PVarzwES - **Publish date (unix):** 1755871240 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113524 kbps - video/mp4 · 180p · 180p · 187404 kbps - video/mp4 · 270p · 270p · 240074 kbps - video/mp4 · 360p · 360p · 326582 kbps - video/mp4 · 406p · 406p · 382243 kbps - video/mp4 · 540p · 540p · 539795 kbps - video/mp4 · 720p · 720p · 824768 kbps - video/mp4 · 1080p · 1080p · 1666428 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/PVarzwES-120.vtt` #### Video transcript From simple inputs like URLs, numbers, and booleans, to more complex and powerful options like rich text editors, modular blocks, global fields, and references, there's a field for almost every kind of content you need to manage. Here, we'll take a closer look at the different field types available in ContentStack, how they work, and when to use them. So, what do fields actually do? Fields are the building blocks of your content types. They control what kind of information your content holds, and how it's entered, how it's validated, and how it's reused. Every entry in ContentStack gets its structure from these fields. Each field includes editable properties like display name, which is what the users see, a unique ID, which is used behind the scenes, the default value, help text, and mandatory or optional settings. These controls give you flexibility, not just in what content is captured, but how consistent and user-friendly it is for your team. ContentStack offers all sorts of fields, from basic fields like text numbers, dates, and booleans, to the more complex fields we talked about like rich text editors, modular blocks, references, and custom fields. Now that we've looked at how fields work in general, let's take a closer look at some of the most commonly used ones, starting with some of these simple fields. These are your go-to inputs for basic content, titles, dates, numbers, links, things like that. The single line text box field lets you capture short, plain text. No formatting, no line breaks, just clean, single line input. You'll use this for straightforward values like first name, last name, headline, city, or job title. You can even use multiple text boxes for structured inputs like address line 1 and address line 2. This field also supports editable properties like setting it as mandatory, adding help text, or defining a default value. The multi-line text box is designed for longer blocks of plain text. Think of it as a basic notepad, ideal for content that doesn't need formatting but might span a few sentences or paragraphs. Unlike the single line text box, this one supports line breaks, so it's perfect for internal notes, brief bios, or summaries. Just like before, it's plain text only, no bolding, links, or rich formatting. The boolean value is a simple on-off switch that lets you capture binary choices like show this section, featured post, or enable animation. The default value is false, but you can toggle it to true as needed. It's perfect for quick decisions that influence layout or logic on the front end. The date field lets you pick a specific day or day and time. You'll often see it used for things like published dates, event times, and deadlines. Just click into the field, choose your date from the calendar, and you're set. The file field is exactly what it sounds like. It lets you upload or attach files. This could be an image, a PDF, a video, or any other asset that belongs in your content. Use it when you need to add things like a profile image, a downloadable brochure, or a banner video. Files added here are automatically saved to the asset library in Content Stack. The link field lets you add a clickable link and give it a label. For example, you might create a Learn More button that links to a product page. You just fill in the title, which is what the users will see, and the URL, where it will go. The Select field gives you a dropdown, radio buttons, or checkboxes with predefined choices. You'll see this used for things like picking a size, small, medium, large, or extra large, choosing a region, or selecting a content category. You just click and choose from the list. It's easy. To wrap up, these fields are straightforward, but powerful. They help structure the content you create so it's consistent, organized, and ready to be published anywhere. #### Key takeaways - Connect **Fields in Contentstack** 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. ### Lesson 05 — Advanced Fields in Contentstack #### Video details #### At a glance - **Title:** Advanced Fields In Contentstack - **Duration:** 3m 42s - **Media link:** https://cdn.jwplayer.com/previews/prYXxWQE - **Publish date (unix):** 1755871412 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113949 kbps - video/mp4 · 180p · 180p · 177418 kbps - video/mp4 · 270p · 270p · 221943 kbps - video/mp4 · 360p · 360p · 301616 kbps - video/mp4 · 406p · 406p · 352392 kbps - video/mp4 · 540p · 540p · 496985 kbps - video/mp4 · 720p · 720p · 754439 kbps - video/mp4 · 1080p · 1080p · 1501031 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/prYXxWQE-120.vtt` #### Video transcript So far, we've covered the basics, simple fields like text, links, and images, but Content Stack also gives you a set of advanced fields designed for more dynamic, reusable, or personalized content. These are fields you probably won't create yourself, but you'll definitely interact with them as a content editor. Let's take a quick tour of what these fields are and why they're helpful. The Reference field lets you pull in content from other entries. For example, in a blog post, you might select the author from a list rather than retyping their info every time. It connects your content so you can reuse and manage it more efficiently. The Group field lets you bundle multiple fields together as a unit. Think of things like a carousel, where each slide has a title, image, and a link. Grouping content keeps the structure consistent. Another example might be a navigation menu, where each item needs a label and a link. That's another great use of groups. Modular blocks are all about flexibility. They let content editors choose which components to use and in which order, directly inside the entry. You might use the modular block to build dynamic pages with images, text sections, calls to action, or even personalized content without needing a developer. Again, it's like building with Lego blocks. Select them, rearrange them, and get the layout you want. A Global field is a reusable set of fields that shows up across multiple content types. If your team uses the same SEO setup, a footer layout, or a call to action button over and over, Global fields lets you define it once and reuse it everywhere. Another huge benefit is if you make a change in one place, it'll then update wherever it's used. Content Stack offers two types of rich text editors, a traditional HTML-based editor for basic formatting in inline media, and a modern block-style JSON editor, which structures content in clean, reusable chunks. Both are great for writing articles, adding images, embedding videos, and more. It just depends on how your stack is configured. Some fields only show up when they're relevant, and that's thanks to field visibility rules. For example, if you select Yes to Do You Have Experience, a new field for Years of Experience may appear. Another example is if you choose Mail, it may autofill Mr. before your name. These rules help simplify the editing experience by hiding what you don't need and showing what you do. As an end user, you won't need to set up these fields, but knowing what they do helps you understand what's happening behind the scenes. These advanced tools make your content more modular, more dynamic, and a whole lot easier to manage, especially at scale. #### Key takeaways - Connect **Advanced Fields in Contentstack** 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. ### Lesson 06 — Why Content Models Matter #### Video details #### At a glance - **Title:** Why Content Models Matter - **Duration:** 2m 47s - **Media link:** https://cdn.jwplayer.com/previews/emryHLW9 - **Publish date (unix):** 1755877432 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 113607 kbps - video/mp4 · 180p · 180p · 188067 kbps - video/mp4 · 270p · 270p · 238905 kbps - video/mp4 · 360p · 360p · 324407 kbps - video/mp4 · 406p · 406p · 379950 kbps - video/mp4 · 540p · 540p · 531930 kbps - video/mp4 · 720p · 720p · 803661 kbps - video/mp4 · 1080p · 1080p · 1591403 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/emryHLW9-120.vtt` #### Video transcript Okay, so let's quickly review some content types already configured, so you can see what a final product looks like. I'm using the Compass Travel site, and here I'll enter the CMS, and I'll enter the Compass Travel stack. Now, you can go directly into Content Models to see what's configured, but remember, real-world, these will already have been set up for you, so it might make more sense to see them in context. So let's come over to Entries, which is where you'll be doing more of your work. Here we can click About Us, and you'll notice this is a landing page content type. You can even click Live Preview to get a preview of what this will look like rendered in a browser. Now, it might take a second to load, but when it does, you can expand it. So now we know what this looks like on the front end. I'll go ahead and close it, and now you'll see in the top the name of the content type next to the page title, and if you click it, you'll enter the content type. And here you can see how this content type was built, and you'll even recognize some of the fields we talked about previously. So let's take a step back. At this point, you've seen what content types are, how fields are structured, and how Content Stack makes it all work behind the scenes. But here's the big idea. A content model isn't just a technical setup. It's the foundation of how your content lives, moves, and grows across digital experiences. When content is structured well, it's reusable, it's scalable, it's consistent. That means faster publishing, fewer errors, and content that works across websites, apps, emails, everywhere. And while you may not be the one building the content model, understanding how it works helps you know where to put content and how it will be used, and you can create content that works better for your audience. Think of the model as the blueprint, and your job is to bring it to life. Thank you so much for joining me in learning how Content Stack is structured. See you next time. #### Key takeaways - Connect **Why Content Models Matter** 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. ## Resources & references | Page | Companion Markdown | | --- | --- | | /courses/structuring-content-in-contentstack/overview-of-content-types | /academy/md/courses/structuring-content-in-contentstack/overview-of-content-types.md | | /courses/structuring-content-in-contentstack/understanding-content-type-classification | /academy/md/courses/structuring-content-in-contentstack/understanding-content-type-classification.md | | /courses/structuring-content-in-contentstack/why-labels-matter | /academy/md/courses/structuring-content-in-contentstack/why-labels-matter.md | | /courses/structuring-content-in-contentstack/fields-in-contentstack | /academy/md/courses/structuring-content-in-contentstack/fields-in-contentstack.md | | /courses/structuring-content-in-contentstack/advanced-fields-in-contentstack | /academy/md/courses/structuring-content-in-contentstack/advanced-fields-in-contentstack.md | | /courses/structuring-content-in-contentstack/why-content-models-matter | /academy/md/courses/structuring-content-in-contentstack/why-content-models-matter.md | ## Supplement for indexing ### Content summary This course gives you a clear, practical understanding of how content is structured inside Contentstack—and why that structure is the backbone of scalable digital experiences. You’ll learn how content models act as bluep… This course gives you a clear, practical understanding of how content is structured inside Contentstack—and why that structure is the backbone of scalable digital experiences. You’ll learn how content models act as blueprints, how content types serve as reusable molds, and how fields shape every entry you create. We’ll cover the essentials: Content Types Fields Labels Through real-world examples like building a blog page, you’ll see how structured content speeds up publishing, improves consistency, and makes collaboration easier across teams. By the end, you’ll understand how content models co ### Retrieval tags - Contentstack Academy - structuring-content-in-contentstack - Overview - Content - Types - Understanding - Type - Classification - Why - Labels - Matter - Fields - Contentstack - Advanced ### Indexing notes Chunk at each "### Lesson NN — Title" heading; copy lesson_id and topics from the preceding HTML comment into chunk metadata for RAG filters. Course slug: structuring-content-in-contentstack. Union of lesson topic tokens: Overview, Content, Types, Understanding, Type, Classification, Why, Labels, Matter, Fields, Contentstack, Advanced, Models. Do not embed or retrieve LMS-only quiz items or mastery exam answer keys from this export. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: Overview of Content Types | `https://cdn.jwplayer.com/v2/media/Yo2tjKM4/poster.jpg?width=720` | | Video thumbnail: Understanding Content Type Classification | `https://cdn.jwplayer.com/v2/media/gIA0aMT1/poster.jpg?width=720` | | Video thumbnail: Why Labels Matter | `https://cdn.jwplayer.com/v2/media/Kvlijm90/poster.jpg?width=720` | | Video thumbnail: Fields in Contentstack | `https://cdn.jwplayer.com/v2/media/PVarzwES/poster.jpg?width=720` | | Video thumbnail: Advanced Fields in Contentstack | `https://cdn.jwplayer.com/v2/media/prYXxWQE/poster.jpg?width=720` | | Video thumbnail: Why Content Models Matter | `https://cdn.jwplayer.com/v2/media/emryHLW9/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/` |