# Advanced Fields in Contentstack ### 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/advanced-fields-in-contentstack | | **course_slug** | structuring-content-in-contentstack | | **lesson_slug** | advanced-fields-in-contentstack | | **learning_path_slug** | cms-content-manager-certification | | **markdown_file_url** | /academy/md/learning-paths/cms-content-manager-certification/structuring-content-in-contentstack/advanced-fields-in-contentstack.md | | **generated_at** | 2026-04-28T06:55:50.800Z | > 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:** 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` #### 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. #### Subtitles (WebVTT) ```webvtt WEBVTT 1 00:00:00.000 --> 00:00:08.300 So far, we've covered the basics, simple fields like text, links, and images, but Content 2 00:00:08.300 --> 00:00:17.340 Stack also gives you a set of advanced fields designed for more dynamic, reusable, or personalized 3 00:00:17.340 --> 00:00:18.340 content. 4 00:00:18.340 --> 00:00:23.780 These are fields you probably won't create yourself, but you'll definitely interact 5 00:00:23.780 --> 00:00:26.180 with them as a content editor. 6 00:00:26.700 --> 00:00:32.660 Let's take a quick tour of what these fields are and why they're helpful. 7 00:00:32.660 --> 00:00:38.740 The Reference field lets you pull in content from other entries. 8 00:00:38.740 --> 00:00:45.580 For example, in a blog post, you might select the author from a list rather than retyping 9 00:00:45.580 --> 00:00:48.180 their info every time. 10 00:00:48.180 --> 00:00:54.420 It connects your content so you can reuse and manage it more efficiently. 11 00:00:54.420 --> 00:01:00.020 The Group field lets you bundle multiple fields together as a unit. 12 00:01:00.020 --> 00:01:06.300 Think of things like a carousel, where each slide has a title, image, and a link. 13 00:01:06.300 --> 00:01:10.540 Grouping content keeps the structure consistent. 14 00:01:10.540 --> 00:01:16.540 Another example might be a navigation menu, where each item needs a label and a link. 15 00:01:16.540 --> 00:01:20.220 That's another great use of groups. 16 00:01:20.220 --> 00:01:23.740 Modular blocks are all about flexibility. 17 00:01:23.740 --> 00:01:31.060 They let content editors choose which components to use and in which order, directly inside 18 00:01:31.060 --> 00:01:32.460 the entry. 19 00:01:32.460 --> 00:01:40.060 You might use the modular block to build dynamic pages with images, text sections, calls to 20 00:01:40.060 --> 00:01:45.020 action, or even personalized content without needing a developer. 21 00:01:45.020 --> 00:01:48.660 Again, it's like building with Lego blocks. 22 00:01:48.660 --> 00:01:53.860 Select them, rearrange them, and get the layout you want. 23 00:01:53.860 --> 00:02:01.120 A Global field is a reusable set of fields that shows up across multiple content types. 24 00:02:01.120 --> 00:02:07.660 If your team uses the same SEO setup, a footer layout, or a call to action button over and 25 00:02:07.660 --> 00:02:13.100 over, Global fields lets you define it once and reuse it everywhere. 26 00:02:13.100 --> 00:02:18.900 Another huge benefit is if you make a change in one place, it'll then update wherever 27 00:02:18.900 --> 00:02:21.460 it's used. 28 00:02:21.460 --> 00:02:27.780 Content Stack offers two types of rich text editors, a traditional HTML-based editor for 29 00:02:27.780 --> 00:02:35.460 basic formatting in inline media, and a modern block-style JSON editor, which structures 30 00:02:35.460 --> 00:02:39.300 content in clean, reusable chunks. 31 00:02:39.300 --> 00:02:44.700 Both are great for writing articles, adding images, embedding videos, and more. 32 00:02:44.700 --> 00:02:49.100 It just depends on how your stack is configured. 33 00:02:49.100 --> 00:02:54.940 Some fields only show up when they're relevant, and that's thanks to field visibility rules. 34 00:02:54.940 --> 00:03:02.340 For example, if you select Yes to Do You Have Experience, a new field for Years of Experience 35 00:03:02.340 --> 00:03:04.140 may appear. 36 00:03:04.140 --> 00:03:11.020 Another example is if you choose Mail, it may autofill Mr. before your name. 37 00:03:11.020 --> 00:03:18.140 These rules help simplify the editing experience by hiding what you don't need and showing 38 00:03:18.140 --> 00:03:20.020 what you do. 39 00:03:20.020 --> 00:03:25.740 As an end user, you won't need to set up these fields, but knowing what they do helps 40 00:03:25.740 --> 00:03:30.060 you understand what's happening behind the scenes. 41 00:03:30.060 --> 00:03:37.100 These advanced tools make your content more modular, more dynamic, and a whole lot easier 42 00:03:37.100 --> 00:03:40.340 to manage, especially at scale. ``` ```transcript [00:00] So far, we've covered the basics, simple fields like text, links, and images, but Content [00:08] Stack also gives you a set of advanced fields designed for more dynamic, reusable, or personalized [00:17] content. [00:18] These are fields you probably won't create yourself, but you'll definitely interact [00:23] with them as a content editor. [00:26] Let's take a quick tour of what these fields are and why they're helpful. [00:32] The Reference field lets you pull in content from other entries. [00:38] For example, in a blog post, you might select the author from a list rather than retyping [00:45] their info every time. [00:48] It connects your content so you can reuse and manage it more efficiently. [00:54] The Group field lets you bundle multiple fields together as a unit. [01:00] Think of things like a carousel, where each slide has a title, image, and a link. [01:06] Grouping content keeps the structure consistent. [01:10] Another example might be a navigation menu, where each item needs a label and a link. [01:16] That's another great use of groups. [01:20] Modular blocks are all about flexibility. [01:23] They let content editors choose which components to use and in which order, directly inside [01:31] the entry. [01:32] You might use the modular block to build dynamic pages with images, text sections, calls to [01:40] action, or even personalized content without needing a developer. [01:45] Again, it's like building with Lego blocks. [01:48] Select them, rearrange them, and get the layout you want. [01:53] A Global field is a reusable set of fields that shows up across multiple content types. [02:01] If your team uses the same SEO setup, a footer layout, or a call to action button over and [02:07] over, Global fields lets you define it once and reuse it everywhere. [02:13] Another huge benefit is if you make a change in one place, it'll then update wherever [02:18] it's used. [02:21] Content Stack offers two types of rich text editors, a traditional HTML-based editor for [02:27] basic formatting in inline media, and a modern block-style JSON editor, which structures [02:35] content in clean, reusable chunks. [02:39] Both are great for writing articles, adding images, embedding videos, and more. [02:44] It just depends on how your stack is configured. [02:49] Some fields only show up when they're relevant, and that's thanks to field visibility rules. [02:54] For example, if you select Yes to Do You Have Experience, a new field for Years of Experience [03:02] may appear. [03:04] Another example is if you choose Mail, it may autofill Mr. before your name. [03:11] These rules help simplify the editing experience by hiding what you don't need and showing [03:18] what you do. [03:20] As an end user, you won't need to set up these fields, but knowing what they do helps [03:25] you understand what's happening behind the scenes. [03:30] These advanced tools make your content more modular, more dynamic, and a whole lot easier [03:37] 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. ## Supplement for indexing ### Content summary Advanced Fields in Contentstack. Advanced Fields in Contentstack in Structuring Content in Contentstack (structuring-content-in-contentstack). ### Retrieval tags - Advanced - Fields - Contentstack - structuring-content-in-contentstack - lesson 05 - Advanced Fields in Contentstack - structuring-content-in-contentstack lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "05" and topics: [Advanced, Fields, Contentstack]. 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: Advanced Fields in Contentstack | `https://cdn.jwplayer.com/v2/media/prYXxWQE/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/` |