# Understanding Content Type Classification ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/learning-paths/cms-content-manager-certification/structuring-content-in-contentstack/understanding-content-type-classification | | **course_slug** | structuring-content-in-contentstack | | **lesson_slug** | understanding-content-type-classification | | **learning_path_slug** | cms-content-manager-certification | | **markdown_file_url** | /academy/md/learning-paths/cms-content-manager-certification/structuring-content-in-contentstack/understanding-content-type-classification.md | | **generated_at** | 2026-04-28T06:55:50.797Z | > Lesson in **[Structuring Content in Contentstack](https://www.contentstack.com/academy/learning-paths/cms-content-manager-certification/structuring-content-in-contentstack)** within the **cms-content-manager-certification** learning path on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### 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` #### 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. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:07.560 So, we know how to structure content using content types, but not all content types are 2 00:00:07.560 --> 00:00:09.440 created equal. 3 00:00:09.440 --> 00:00:16.440 Some are designed for one-off pages like your homepage or privacy policy, and others are 4 00:00:16.440 --> 00:00:23.160 built to generate dozens or hundreds of pages using the same layout. 5 00:00:23.160 --> 00:00:27.520 And some content types aren't even pages at all. 6 00:00:27.520 --> 00:00:35.600 They're just reusable components like headers and footers, or in the case of our blog example, 7 00:00:35.600 --> 00:00:38.920 author bios or categories. 8 00:00:38.920 --> 00:00:43.640 Understanding how to classify a content type correctly is essential. 9 00:00:43.640 --> 00:00:49.840 It impacts not just how you create content, but also how developers build and connect 10 00:00:49.840 --> 00:00:52.040 your front end. 11 00:00:52.040 --> 00:00:59.200 InStack classifies content types into three categories, single page component, multiple 12 00:00:59.200 --> 00:01:04.760 page component, and reusable components, which are set up the same way as a multiple page 13 00:01:04.760 --> 00:01:07.680 component, but use a reference field. 14 00:01:07.680 --> 00:01:14.840 A single page component is used for one-off pages that each have a unique structure. 15 00:01:14.840 --> 00:01:17.040 These pages are standalone. 16 00:01:17.040 --> 00:01:20.240 There's only one of them on your site. 17 00:01:20.240 --> 00:01:27.960 Again, examples include a homepage, an about us page, or a privacy policy. 18 00:01:27.960 --> 00:01:33.960 When you create this type, simply choose single during setup. 19 00:01:33.960 --> 00:01:40.480 A multiple page component is built when you need to reuse the same structure across many 20 00:01:40.480 --> 00:01:44.800 entries like blog posts or product pages. 21 00:01:44.800 --> 00:01:49.760 These pages share the same layout, but the content inside changes. 22 00:01:49.760 --> 00:01:58.880 Again, examples include blog pages, product pages, or something like case studies. 23 00:01:58.880 --> 00:02:02.880 When creating the content type, select multiple. 24 00:02:02.880 --> 00:02:08.680 This tells Content Stack you'll be adding multiple entries under the same schema. 25 00:02:08.680 --> 00:02:12.160 Not every content type represents a page. 26 00:02:12.160 --> 00:02:19.240 Sometimes you need a reusable piece of content, like an author or category, that can be referenced 27 00:02:19.240 --> 00:02:21.200 inside of other entries. 28 00:02:21.200 --> 00:02:25.560 These are called multi-reusable components. 29 00:02:25.560 --> 00:02:31.200 You still select multiple when creating the content type, but the key difference is that 30 00:02:31.200 --> 00:02:38.520 you'll use them in combination with reference fields inside of other types. 31 00:02:38.560 --> 00:02:44.600 Examples include author profiles for things like blog posts, or categories for products, 32 00:02:44.600 --> 00:02:49.460 or maybe something like testimonials for landing pages. 33 00:02:49.460 --> 00:02:53.200 Some quick reference tips to keep in mind. 34 00:02:53.200 --> 00:02:57.520 Use single for one-off pages like Home or Contact Us. 35 00:02:57.520 --> 00:03:02.760 Use multiple for repeatable pages like blogs or products. 36 00:03:02.760 --> 00:03:10.160 And use multiple and the reference field for reusable content like authors or categories. 37 00:03:10.160 --> 00:03:16.440 Making the right choice here helps you ensure your content is flexible, scalable, and easy 38 00:03:16.440 --> 00:03:18.000 to maintain. 39 00:03:18.000 --> 00:03:23.080 Now that you know the different types of content structures, you're ready to start creating 40 00:03:23.080 --> 00:03:26.080 smarter, more organized content. ``` ```transcript [00:00] So, we know how to structure content using content types, but not all content types are [00:07] created equal. [00:09] Some are designed for one-off pages like your homepage or privacy policy, and others are [00:16] built to generate dozens or hundreds of pages using the same layout. [00:23] And some content types aren't even pages at all. [00:27] They're just reusable components like headers and footers, or in the case of our blog example, [00:35] author bios or categories. [00:38] Understanding how to classify a content type correctly is essential. [00:43] It impacts not just how you create content, but also how developers build and connect [00:49] your front end. [00:52] InStack classifies content types into three categories, single page component, multiple [00:59] page component, and reusable components, which are set up the same way as a multiple page [01:04] component, but use a reference field. [01:07] A single page component is used for one-off pages that each have a unique structure. [01:14] These pages are standalone. [01:17] There's only one of them on your site. [01:20] Again, examples include a homepage, an about us page, or a privacy policy. [01:27] When you create this type, simply choose single during setup. [01:33] A multiple page component is built when you need to reuse the same structure across many [01:40] entries like blog posts or product pages. [01:44] These pages share the same layout, but the content inside changes. [01:49] Again, examples include blog pages, product pages, or something like case studies. [01:58] When creating the content type, select multiple. [02:02] This tells Content Stack you'll be adding multiple entries under the same schema. [02:08] Not every content type represents a page. [02:12] Sometimes you need a reusable piece of content, like an author or category, that can be referenced [02:19] inside of other entries. [02:21] These are called multi-reusable components. [02:25] You still select multiple when creating the content type, but the key difference is that [02:31] you'll use them in combination with reference fields inside of other types. [02:38] Examples include author profiles for things like blog posts, or categories for products, [02:44] or maybe something like testimonials for landing pages. [02:49] Some quick reference tips to keep in mind. [02:53] Use single for one-off pages like Home or Contact Us. [02:57] Use multiple for repeatable pages like blogs or products. [03:02] And use multiple and the reference field for reusable content like authors or categories. [03:10] Making the right choice here helps you ensure your content is flexible, scalable, and easy [03:16] to maintain. [03:18] Now that you know the different types of content structures, you're ready to start creating [03:23] 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. ## Supplement for indexing ### Content summary Understanding Content Type Classification. Understanding Content Type Classification in Structuring Content in Contentstack (structuring-content-in-contentstack). ### Retrieval tags - Understanding - Content - Type - Classification - structuring-content-in-contentstack - lesson 02 - Understanding Content Type Classification - structuring-content-in-contentstack lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "02" and topics: [Understanding, Content, Type, Classification]. 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: Understanding Content Type Classification | `https://cdn.jwplayer.com/v2/media/gIA0aMT1/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/` |