<h1>Meet the Composable Heroes</h1>Meet the Composable Heroes' Development Team Lead, Cyber Surge. She and her developers can easily create websites using any available technology but are missing an&nbsp;efficient way to create and manage content.
 <img src="https://learnupon.s3.eu-west-1.amazonaws.com/575809/original/c6fb0372-67aa-4cd6-8bf1-f6d6a95e5ca2-Screenshot_2023-05-05_at_1.48.20_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575810/original/a4412fe3-9d4b-4480-adfa-6622604fcdc5-Screenshot_2023-05-05_at_1.54.50_PM.png" width="100"/> The Lightning Excavator,&nbsp;head of Marketing and Sales, identified that Contentstack could assist Cyber Surge in improving its content management process. However, the team needs assistance understanding how to leverage Contentstack's features to address their challenge. You must learn and demonstrate how Contentstack can assist the Composable Heroes in accomplishing their goals.In this episode, you'll learn the basics&nbsp;of Contentstack and delve into its features and higher-level entities.<h1>What is a Headless and Composable CMS?</h1>A Headless CMS(Content Management System) is a CMS without the head, which means it provides all the backend tools needed to create and publish content via API. The "head" is the final presentation layer that is provided to a user when they visit a site.A&nbsp;Composable CMS is a CMS that helps to integrate several technology vendors and services, providing omnichannel content delivery and limitless integration.MACH architecture is&nbsp;a modern approach to building software systems that emphasizes flexibility, scalability, and interoperability, while also ensuring that a&nbsp;technology stack remains future-proof. It stands for Microservices-based, API-first, Cloud-native SaaS, and Headless.<h1>How is Contentstack Headless and Composable?</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575816/original/314331c7-8d61-4380-a1e6-13c05382c3f6-Screenshot_2023-03-28_at_3.21.45_PM.png" width="100"/>Take into consideration the concept of a "Body" which operates as the backend repository, and a "Head" which functions as the presentation layer or frontend. Note that the Head and Body are independent of each other, and the deployment/publishing of content takes place through APIs.Moreover, Contentstack facilitates seamless third-party integrations through its <a href="https://www.contentstack.com/docs/developers/marketplace-apps/">Marketplace</a> apps. You can conveniently integrate various categories of service vendors such as Translations, Video, DAM (Digital Asset Management), Analytics, Commerce, Search, and more.Examples of a few of the Integration Channels that Contentstack supports:<ul><li>Translations - XTM, SDL, Smartling, and many more.</li><li>DAM - Brandfolder, Cloudinary, Bynder, and many more.</li><li>Video - Youtube, Brightcove, Vimeo, and many more.</li><li>Analytics - Google, Adobe, Mixpanel, and many more.</li><li>Commerce - BigCommerce, Salesforce commerce, Commercetools, and many more.</li><li>Search - Elasticsearch, Algolia, and many more.</li></ul>While these are just some of the integrations you can achieve through the marketplace, as long as a service has an API, it can be connected with Contentstack.Contentstack supports Automation&nbsp;functionality&nbsp;which enables the creation of&nbsp;a workflow that connects multiple&nbsp;web apps or services, including Contentstack. To achieve this, Contentstack has&nbsp;introduced&nbsp;<a href="https://www.contentstack.com/docs/developers/automation-hub-guides/about-automation-hub/">Automation Hub</a>, a visual builder&nbsp;for no-code/low-code workflows using an automation-based trigger and action system.Contentstack also provides <a href="https://www.contentstack.com/blog/all-about-headless/announcing-contentstack-launch-composable-is-now-even-easier/">Launch</a> as a platform that can help you host your website/app, thus providing a convenient solution for end-to-end content creation and management. Using Automation Hub together with Launch and Marketplace apps, Contentstack can serve as the nucleus where you can integrate and automate a&nbsp;whole ecosystem, while the various integration channels act as the electrons referencing necessary information. This unique capability is&nbsp;what makes Contentstack both an efficient and composable CMS.In summary, Contentstack is a composable,&nbsp;API-based, headless content management platform that allows developers to speed up delivery and development time&nbsp;while simultaneously enhancing the content managers' ability to create and manage their content independently.<h1>Real World Use Cases</h1>You need a marketing or e-commerce page that can serve&nbsp;content on different channels like a kiosk, web, and mobile for various experiences and campaigns.&nbsp;It should handle&nbsp;several&nbsp;frontend technology frameworks, and be able to manage additional localized content to be served in other countries and languages. Combined with MACH architecture, Contentstack&nbsp;can help solve this real-world scenario.&nbsp;<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/cms-guides/headless-cms/">What is a Headless CMS?</a></li><li><a href="https://www.contentstack.com/cms-guides/what-is-composable-architecture/">What is a composable architecture?</a></li></ul>

Headless and Composable Contentstack

<h1>What are Organizations and Stacks?</h1>An Organization is the top-most entity in the hierarchy of entities in Contentstack. Users, stacks, and the other resources within the stacks are part of an Organization and are managed from a single administrative panel.A Stack is a repository or a container inside an organization that holds all the content/assets of your site. It allows multiple users to create, edit, approve, and publish their content within a single space.<h1>Understanding with an example</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575817/original/606ed1a9-971d-4081-a416-bef22c132317-Screenshot_2023-03-29_at_4.58.31_PM.png" width="100"/>Consider a 'Shelf' which consists of a 'Stack of Books.'&nbsp;The shelf helps organize the books. A book can contain content, including text, and images. There can be multiple shelves with different stacks of books. Projects within Contentstack work similarly, where an Organization represents the&nbsp;shelf, and&nbsp;Stacks represent the books.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575818/original/6dffcd04-1818-49e4-b3ad-a969be7ebea2-Screenshot_2023-03-27_at_4.34.06_PM.png" width="100"/>An Organization can consist of one or more Stacks. Depending on your team's plan, Contentstack also allows you to create multiple organizations with their own stacks(as shown in the diagram above).<h1>Organization and Stacks - Working with Contentstack</h1>The following video shows you how to log&nbsp;into Contentstack for the first time and provides&nbsp;an overview of accessing&nbsp;your Organization and Stacks within&nbsp;Contenstack's UI.<h1>Exercise 1 Video</h1>Follow along with the video to practice accessing your Organization and Stack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/pbnTewOr-b769H14u.html" width="100" height="100" frameborder="0" scrolling="auto" controls="true" title="01 - Organization And Stack" style="position: absolute;" allowfullscreen=""></iframe></div>Quick Tips: The maximum number of Organization records retrieved in a single GET&nbsp;API call&nbsp;is 100. The maximum number of Stack records retrieved in a single GET&nbsp;API call is 200.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/organization/about-organizations/">More About Organizations</a></li><li><a href="https://www.contentstack.com/docs/developers/set-up-stack/about-stack/">More About Stacks</a></li></ul>

Organization and Stacks

Cyber Surge wishes to create two pages;&nbsp;the&nbsp;"Hall&nbsp;of Heroes"&nbsp;which is a gallery that showcases the Composable Heroes with their images, names, and a&nbsp;brief summary, and the other, "Hero Details&nbsp;Page"&nbsp;which displays detailed information about them, their powers, and the message that they wish the people to read when someone clicks and opens one of the heroes.In response to Cyber Surge's request, The Lightning Excavator&nbsp;is eager to learn how Contentstack can assist them in creating content structures or schemas that can hold the above content.They require a tailored and efficient solution that includes:<ul><li>The ability to create content dynamically without requiring multiple schemas or website code changes.</li><li>Ensures that best practices are followed.</li><li>Allows for organizing&nbsp;and filtering content based on its structure.</li></ul>In this episode, you'll learn how to create and organize the content structure needed for content creation.<h1>What is a Content Type?</h1>A Content Type is the structure or blueprint of a page or section your web or mobile property will display. You define the overall schema of this blueprint by adding fields and setting its properties.Creating a content type is like building a mold or cast that lets you create several objects (content&nbsp;entries) of that exact nature and pattern.<h1>Video: How to create a Content Type</h1>The following videos will walk you through the necessary steps to locate, create, and configure your Content Types in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/LTKtVWmq-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="02 - Content Type" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Consider a ‘Blog page’ which consists of a ‘Title,’ ‘Description,’ ‘Image,’ and ‘Published Date.’Its respective content type would contain:&nbsp;<ul><li>Title as a text field</li><li>Description as a multiple-line text field</li><li>Image as an Asset field</li><li>Published Date as a Date field.’</li></ul>Once you create a content type, you can create entries.The following diagram serves as an example:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575819/original/6fd376b2-a414-4dce-8e2a-adba7ea47661-Screenshot_2023-03-27_at_4.42.30_PM.png" width="100"/>Terminology&nbsp;to get familiar with:<ul><li>Fields - These are the building blocks/components of your structured content. You can control which data you want to add by configuring fields and their properties in a content type.</li><li>Entry - After you define a content type, you can use it to create an&nbsp;entry, then&nbsp;add data and publish it.</li><li>Asset - Any media file such as; .jpg, .pdf, or .mp4 you&nbsp;upload in an entry is added as an asset.</li><li>UID&nbsp;- A UID is a unique code that is assigned to something, like a person or a file, so that it can be easily identified and distinguished from other things that might have similar names or characteristics to&nbsp;ensure that the object is recognized&nbsp;and can be easily found in a system or database.</li></ul><h1>Best Practices To Use</h1><ul><li>It is always recommended to use&nbsp;a lowercase naming convention separated by an underscore for the Content Type UID. &nbsp;
 Examples: &nbsp;blog_page, about_us, hero_biography.</li><li>Provide meaningful, human-readable Titles to ensure your content types are user-friendly.
 Examples:&nbsp;'Blog Page'&nbsp;instead of Blog or&nbsp;blogpage.&nbsp;'Hero Biography'&nbsp;instead of HeroBio or&nbsp;herobio&nbsp;etc...</li><li>Provide a meaningful and intuitive description of your content type&nbsp;and what it&nbsp;is&nbsp;used for.</li></ul>
 Potential Use Case:<ul><li>If you want to create a simple blog page on your site, you will define a ‘Blog Page’ content type with ‘title,’ ‘date,’ ‘body,’ and ‘author’ fields.&nbsp;</li><li>If you want to create the homepage of your site, you will define a ‘Home Page’ content type with a ‘header,’ ‘footer,’ ‘banner-image,’ ‘title,’ and ‘body’ fields.</li></ul>Quick Tips:
 The maximum character length of a Content Type UID is 200.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/about-content-types/">More&nbsp;About Content Types</a></li><li><a href="https://www.contentstack.com/docs/developers/create-content-types/unique-id/">About&nbsp;Unique IDs</a></li></ul>

Building the Content Structure

<h3>What are the types of Content Type?</h3>Contentstack allows you to customize a content type to meet various business requirements, you can create a webpage(s), the partials of your webpage (header, footer, or menu), or experiences in your mobile application.Contentstack classifies Content Types into three types:<ul><li>Single Page Component/Content Type</li><li>Multiple Page Component/Content Type</li><li>Multi-Reusable Component/Content Type</li></ul><h1>Video: Different Types of Content Types&nbsp;</h1>The following video shows you how to change a Content Type type and&nbsp;some examples of the different types.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/0dvSF7gP-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="03 - Content Type Classification" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Exercise 2 Video</h1>Follow along with the video to practice building Content Types.<iframe src="https://www.youtube.com/embed/NP3k1v8LnPs" allowfullscreen="" frameborder="0"></iframe><h1>Understanding with an example</h1><ul><li>Single Page Component/Content Type - If you want to create one-off pages that have a unique content type structure, you must make them as ‘Single Page Component/Content Type.’ Select&nbsp;‘Single’&nbsp;while creating the content type to achieve this. The below diagram gives you an illustration of the same.
 Example:&nbsp;Home Page, About Us Page, Privacy Policy Page, etc. All these pages are one-off pages on a website.</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575820/original/ebf3e8a5-e298-4f5b-aff8-f8812d0e6083-Screenshot_2023-04-13_at_5.18.03_PM.png" width="100"/><ul><li>Multiple Page Component/Content Type - If you want to create multiple pages using the same content type structure, you must create them as a&nbsp;‘Multiple Page Component/Content Type.’ Select&nbsp;‘Multiple’&nbsp;while creating the content type to achieve this. Refer to the diagram below for an example.
 Example:&nbsp;Blog Pages, Product Pages, etc.</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575821/original/91677768-34dc-49d3-b6ca-aba073a881ca-Screenshot_2023-04-13_at_5.18.13_PM.png" width="100"/><ul><li>Multi Reusable Component/Content Type - If you need to make multiple entries that are not pages and can be referred to or used as partial components, you should create them as a 'Multi Reusable Component/Content Type.'&nbsp;Select the type ‘Multiple’ while creating the content type, then use&nbsp;it as a ‘Reference’&nbsp;in any&nbsp;Content Type that contains a reference field. The below diagram illustrates this.
 Example:&nbsp;Authors(for the Blog Pages), Categories(for the Product Pages), etc…</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575822/original/5bcb3136-5e62-4f78-821e-a430510bf7f9-Screenshot_2023-04-13_at_5.18.24_PM.png" width="100"/>Quick Tips:
 If you want to create a single page entry for your content type&nbsp;like a&nbsp;‘Home Page’ or ‘Contact Us Page,’ always go for type ‘Single.’
 If you want to create multiple page entries for your content type like a ‘Blog Pages’ or ‘Product Pages,’ always go for type ‘Multiple.’<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/about-content-types/">About Content Types</a></li><li><a href="https://www.contentstack.com/docs/developers/create-content-types/reference/">About References</a></li></ul>

Content Type Classification

Labels allow you to categorize and organize the existing content types of your stack.You can create and apply labels to group content types for easy access. Labels provide a convenient way of classifying content types based on specific criteria.<h1>Video: How to create and manage Labels</h1>The following video shows how to create and manage labels and how to&nbsp;navigate content types and entries using such labels.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/A3ClCuPW-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="05 - Labels" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575872/original/b8be98fa-5cb5-4a35-9805-79d741214479-Screenshot_2023-03-30_at_2.31.47_PM.png" width="100"/>Consider that we have two teams, 'Marketing' and 'Writers,' each with content types, as shown in the diagram above. If you want to organize these content types into groups/folders, create two labels, 'Marketing' and 'Writers,' and apply these labels to the content types of each respective team.Thus, labels provide a convenient way of classifying content types based on specific criteria. Also, labels are not private. The labels you create for a particular stack are visible to all the users, so make sure you discuss with your team how you would like to produce labels.Potential Use Case:<ul><li>Labels are the best option for organizing content entries based on Labeling and creating an easy way to navigate filtered entries.</li><li>Nested Labels allow the creation of a hierarchy for entities for quick navigations to filtered entries.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/developers/create-content-types/about-labels/">About Labels</a></div></li><li><div><a href="https://www.contentstack.com/docs/developers/create-content-types/create-and-apply-labels/">How to create and apply Labels</a></div></li><li><div><a href="https://www.contentstack.com/docs/developers/create-content-types/manage-labels/">Manage Labels</a></div></li></ul>

Labels

Fields are the building blocks for structured content. The type and order of the fields you add to a content type decide how the content will be presented. All the content you will add to create an entry goes into the fields.Each field possesses specific properties, such as:<ul><li>Display Name</li><li>Unique ID</li><li>Default Value</li><li>Help Text</li><li>Mandatory&nbsp;</li></ul>and so on. These properties are editable and provide flexibility to customize the nature of the field.<h1>Video: Content Type Fields Example;&nbsp;Blog Entry</h1>In this video, we look at&nbsp;the different fields used by the "Blog Entry" example Content Type.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/ZIuqUkgY-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="04 - Content Type Example" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575823/original/2881dcaf-2868-4bbd-b1fc-d5e4108efa64-Screenshot_2023-03-27_at_4.42.30_PM.png" width="100"/>Consider a 'Blog page' which consists of a 'Title,' 'Description,' 'Image,' and 'Published Date.' Its respective content type will contain fields like 'Title = text field,' 'Description = multiple line text field,' 'Image = Asset field,' and 'Published Date = Date field.'In Contentstack, the 'Title' field is a default text field that is mandatory and unique whenever you create a content type. It accepts single-line text and provides no formatting options or line breaks. The entry's title is the value entered in this field while making an entry.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575824/original/d3efe4db-b1fb-451d-9d89-c1046d76786a-Title_Field.png" width="100"/>Contentstack classifies Fields into two types:<ul><li>Simple Fields</li><li>Advanced Fields</li></ul>The following diagram depicts the types of fields:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575825/original/4496163f-99c1-4013-95c7-d9cfbeb2e93b-Screenshot_2023-03-30_at_3.29.34_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575826/original/b7f5c10f-4a07-44e3-90bc-0cfd6cd7fa1e-Screenshot_2023-03-30_at_3.29.51_PM.png" width="100"/>We will look at the above fields in detail in the upcoming episodes.Quick Tips:
 While you can add a maximum of&nbsp;100 fields to a content type by default, having large number of fields can increase complexity and impact authoring experience.&nbsp;<h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/developers/create-content-types/about-fields/">More About Fields</a></div></li><li><div><a href="https://www.contentstack.com/docs/developers/create-content-types/about-field-properties/">About Field Properties</a></div></li></ul>

Fields

The Single Line Textbox field enables users to type in single-line arbitrary text. When you add this field in content type, you will see a single-line textbox on the entry page to enter plain text only.This field does not provide any formatting options or line breaks.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575827/original/17c86b08-3113-4d72-852e-9aa517087dad-single_line_text_field.png" width="100"/><h1>Understanding with an example</h1><ul><li>If you want to add an Author’s First Name and Last Name, you can use two different Single Line Textbox fields.</li><li>You can use two Single Line Textbox fields to capture an Author’s Address Line 1 and a second Address Line 2.</li></ul>This field has specific properties you can change anytime per your needs.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575828/original/eda7cb50-327c-47c8-935c-08e123b0818a-Screen_Shot_2023-04-27_at_5.44.31_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575829/original/893a5e80-3ea0-4890-800b-1c5056dbef47-Fields-advanced.png" width="100"/>The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Placeholder Value</li><li>Instruction Value</li><li>Help Text</li></ul></li><li>Advanced<ul><li>Number of Characters</li><li>Validation (Regex)</li><li>Validation Error Message</li><li>Default Value</li><li>Options<ul><li>Mandatory</li><li>Unique</li><li>Multiple</li><li>Non-localizable</li></ul></li></ul></li></ul>Quick Tips:
 It's a good practice to use this field for brief text that doesn't require any formatting or line breaks.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/single-line-textbox/">About Single Line Textbox Fields</a>&nbsp;</li></ul>

Single Line Textbox Field

The Multi-Line Textbox field enables users to enter the multi-line arbitrary text as content. When you add this field in the content type, it displays a text area on the entry page to enter a large chunk of data.This field does not provide any formatting options but does provide line breaks. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/575830/original/c8e7333a-228a-4e7f-9500-0492d8cc109b-multi-line_textbox.png" width="100"/><h1>Understanding with an example</h1><ul><li>You can use a Multi-Line Textbox field to capture the entire address in one go with line breaks, for example, an Author’s Address.</li></ul>This field has specific properties you can change anytime per your needs.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Placeholder Value</li><li>Instruction Value</li><li>Help Text</li><li>Number of Characters</li><li>Validation (Regex)</li><li>Validation Error Message</li><li>Default Value</li><li>Options<ul><li>Mandatory</li><li>Unique</li><li>Multiple</li><li>Non-localizable</li></ul></li></ul></li></ul>Quick Tips:
 Use this field if you don’t need any text formatting options but require multiple lines of text such as a paragraph description.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/multi-line-textbox/">About Multi-Line Text Box Fields</a></li></ul>

Multi-Line Textbox Field

The URL field enables you to define a relative path for where you want to publish content.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575831/original/6352f5e9-1fa8-4b4c-beaa-08bbcf651768-URL_Field.png" width="100"/><h1>Understanding with an example</h1><ul><li>If your page is a&nbsp;Blog Page, you should provide a relative path/URL like '/blog'.</li></ul>The use of the URL field will vary based on the content type you have created.If the type of content type is 'Single':<ul><li>You cannot set properties for the URL field.</li><li>The only property that you can modify is '<a href="http://www.contentstack.com/docs/developers/multilingual-content/non-localizable-field/">Non-localizable</a>.'</li></ul>If the type of content type is 'Multiple':<ul><li>You can modify the 'Non-localizable' property in the 'Advanced' tab.</li><li>The basic properties in the 'Basic' tab will allow you to set the default URL Prefix Pattern. You can either manually input the URL Pattern to specify the prefix or choose from one of the following options -</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575832/original/5a0a8ebc-4141-4b7e-9308-22e578e1a434-URL_properties.png" width="100"/><ol><li>Title - When you select this option, a prefix using the value inside the 'Title' field will be automatically populated within the URL field.
 Examples:&nbsp;If the title field is 'About Us,' the URL field will automatically populate the value as '/about-us' in the entry.</li><li>Date and Title - When you select this option, a prefix with the current date followed by a value inside the 'Title' field will be automatically populated within the URL field.
 Examples:&nbsp;If the title field has a value of 'About Us' and the current day is '2023/03/30', the URL field will automatically populate the value as '/2023/03/30/about-us' in the entry.</li><li>Month and Title - When you select this option, a prefix with the current month and year followed by the value inside the 'Title' field will be automatically populated in the URL field.
 Examples:&nbsp;If the title field has a value as 'About Us' and the current month and year is '2023/03', the URL field will automatically populate the value as '/2023/03/about-us' in the entry.</li><li>Disable - When you select this option, the relative path will be kept blank by default. You can then enter a URL while creating the entry.</li><li>Custom - This option lets you set a custom URL pattern by using available variables, custom text, or a combination of both.

 The variables available for the custom pattern field are given as follows:</li></ol><ul><li>:title - Displays the title of the entry in the URL.
 Example:&nbsp;If the title field is 'About Us,' the URL field will automatically populate the value as '/about-us' in the entry.</li><li>:unique_id - Displays the unique ID of the entry in the URL.
 Example:&nbsp;The URL field will automatically populate a unique random id like '/asbd866478c'.</li><li>:year - Displays the year of creation (numeric) in the URL.
 Example:&nbsp;The URL field will automatically populate the current year like '/2023'.</li><li>:year_short - Displays the short version of the year of creation (numeric) in the URL.
 Example:&nbsp;The URL field will automatically populate the current year like '/23'.</li><li>:monthname - Displays the name of the month of creation in the URL.
 Example:&nbsp;The URL field will automatically populate the current month name like'/march'.</li><li>:monthname_short - Displays the short version of the month name in the URL.
 Example:&nbsp;The URL field will automatically populate the current month name in short, like'/mar'.</li><li>:day -Displays the day (numeric) of the creation in the URL.
 Example:&nbsp;The URL field will automatically populate the current day, like'/30'.</li><li>:year-:month-:day - Displays the year/month/date of creation.
 Example:&nbsp;The URL field will automatically populate the current date like '/2023-03-30'.</li></ul>Potential Use Case:
 Auto-generate SEO Friendly URLs based on a title field value.
 Set up a preview URL for&nbsp;an entry so that an editor can easily navigate to the web pages and preview changes.Quick Tips:
 Use this parameter for&nbsp;your content types that delivers a page rather than a partial component or is a referenced content.
 If you have selected Single as your content type, we will be unable to set settings for the URL field.<h1>Further Reading</h1><ul><li><div><a href="http://%E2%80%8Bhttps://www.contentstack.com/docs/developers/create-content-types/url/">About URL Fields</a></div></li></ul>

URL Field

The Number field enables users to enter numeric data.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575833/original/7a48a9b8-c92b-42ec-a96f-2dabd00240a3-number_field.png" width="100"/><h1>Understanding with an example</h1><ul><li>You can use a Number field to capture data like a Phone Number or a Zip Code.</li></ul>This field has specific properties you can change anytime per your needs.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Placeholder Value</li><li>Instruction Value</li><li>Help Text</li></ul></li><li>Advanced<ul><li>Range<ul><li>Min</li><li>Max</li></ul></li><li>Default Value</li><li>Options<ul><li>Mandatory</li><li>Unique</li><li>Multiple</li><li>Non-localizable</li></ul></li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575834/original/eb393098-b2aa-482b-98e4-e5ba4e8e6675-Number_Advanced.png" width="100"/><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/number/">About Number Fields</a></li></ul>

Number Field

The Boolean input field enables users to input a ‘true’ or ‘false’ value in an entry. When you add this field in the content type, it is displayed as an on/off toggle switch on the entry page.The default value is always ‘false.’<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575835/original/f69740ec-ece9-4abe-80cb-7ee2dc4c4dee-boolean_field.png" width="100"/><h1>Understanding with an example</h1><ul><li>Consider a website with a form with the terms and conditions or privacy policies of your company's legal agreement. On this form is a clickwrap field labeled 'I Agree' to obtain consent from the users. The users will have the option to agree or disagree with your company's policies. In such cases, you will be using a Boolean field.</li></ul>The following diagrams depict how a boolean field will look in the entry:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575836/original/b90d4030-f847-473c-a61c-de011fd46aaa-Screenshot_2023-03-30_at_5.50.19_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575837/original/7cb4985c-5e7a-4a0f-a8f4-818eccd71ee6-Screenshot_2023-03-30_at_5.50.26_PM.png" width="100"/><ul><li>You can easily toggle the switch to set the value to 'false' or 'true.'</li><li>The Default Value option helps you to set pre-define state&nbsp;of the boolean field. The value selected here will appear by default when an entry for this content type is created.</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575838/original/c53029c6-1280-40bd-b13f-5b416c03c08e-boolean_properties.png" width="100"/><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/boolean/">More About Boolean Field</a></li></ul>

Boolean Field

The Date field accepts a date in the *ISO format. When you add this field in the content type, it renders a calendar to select the date and time on the entry page.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575839/original/c060bf02-732f-484d-9b2e-abb6665f77d9-date_field.png" width="100"/>You can deactivate the time field using the ‘Hide Time’ option under its properties.(*ISO format - The International Organization for Standardization (ISO) date and time format is a standard way to express a numeric calendar date -- and optionally time -- in a format that eliminates ambiguity between entities.)<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575840/original/6bba7e0c-5362-4d51-9674-5b56dde89d30-date_properties.png" width="100"/><h1>Understanding with an example</h1><ul><li>You can use a Date field to capture something like a Published Date of a Blog post.</li><li>If you want to capture a Date and Time for a Purchase Order, you can use a Date field along with Time.</li></ul>This field has specific properties you can change anytime per your needs.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li></ul></li><li>Advanced<ul><li>Default Value<ul><li>Created Date</li><li>Custom Date</li></ul></li><li>Options<ul><li>Mandatory</li><li>Hide Time</li><li>Set Date Range<ul><li>Start Date</li><li>End Date</li></ul></li><li>Multiple<ul><li>Max Limit</li></ul></li><li>Non-localizable</li></ul></li></ul></li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/date/">About Date Field</a></li></ul>

Date Field

The File field enables users to upload and use files in an entry.When you add this field to the content type, it shows the following options:<ul><li>Choose a file - &nbsp;This lets you select an existing file(s) stored under <a href="https://www.contentstack.com/docs/content-managers/author-content/about-assets/">ASSETS</a>.</li><li>Upload a new file - This lets you upload any file from your local system.</li></ul>Every file you upload via the Upload new file option gets stored as an asset in Contentstack.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575841/original/ff4a0d6f-adc8-48bd-8dfe-cc5901b6c865-Screenshot_2023-05-03_at_11.06.09_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>If you want to have the ability to upload an Image like an &nbsp;Author’s Image for a Blog post, you can use a File field.</li><li>If you want to have the ability to upload a Featured Image for a Blog post, you can use a File field.</li><li>If you want to have the option to upload a Video, like a Banner Video for the Home Page, you can use a File field.</li><li>If you want to have the option to upload a PDF file, you can use a File field for something like a Product Brochure that any user can download.</li></ul>This field has specific properties you can change anytime per your needs.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li></ul></li><li>Advanced<ul><li>Options<ul><li>Mandatory</li><li>Multiple</li><li>Non-localizable</li><li>Allow images only</li></ul></li><li>Allowed file types(s)</li><li>File size limit(MB)<ul><li>Min</li><li>Max</li></ul></li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575842/original/27776cb7-172b-42ca-b1f2-ac6ae74dc50e-Screenshot_2023-05-03_at_11.11.34_AM.png" width="100"/>Quick Tips:
 You can upload files as large&nbsp;as is 700 MB, which is the default max file size.
 For optimization purpose the default Image input size is capped at&nbsp;50 MB.
 If you have selected Single as your content type, you cannot&nbsp;set settings for the URL field.
 The following characters cannot be used in the Filename or URL of the assets (stacks v3.2 and above) are `#%^+\/?\*:|"'&lt;&gt;\s{}=,_. Restricted characters will be replaced by an underscore (_) automatically.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/file/">About File Field</a></li></ul>

File Field

The Link field enables users to add a link(s) to their entry page.This field possesses two subfields:<ul><li>Title - This lets you specify the display text for the corresponding link.</li><li>Link - This enables you to set a static or relative (to the site’s root URL) URL for the related title.</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575843/original/b8301ed1-859c-4679-b3a2-ba7646fc0e91-Screenshot_2023-05-03_at_11.13.16_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>You can choose a Link field if you want to create a link for a ‘Learn More’ button to visit and read more about a Product’s Detail. The ‘Title’ would be ‘Learn More’ and ’‘Link’ will contain the actual link to the destination page/article.</li><li>You can use a Link Field to create a Header menu containing menus like Blogs, About Us, Products, etc.</li><li>You can use a Link Field to create a Footer link containing links like Privacy Policy, Contact Us, etc.</li></ul>This field has specific properties you can change anytime per your needs.The properties that can be modified are:<ul><li>Basic<ul><li>Display&nbsp;Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li></ul></li><li>Advanced<ul><li>Default Value<ul><li>Title</li><li>URL</li></ul></li><li>Options<ul><li>Mandatory</li><li>Multiple</li><li>Non-localizable</li></ul></li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575844/original/5df36bd4-6a9e-44c5-ad64-40b60723069f-Screenshot_2023-05-03_at_11.14.21_AM.png" width="100"/>Quick Tips:
 Always use this field to assign a Title and Link to any component on a page/entry.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/link/">About Link Field</a></li></ul>

Link Field

The Select field allows users to choose one or more options from predefined choices. Configure this field as a Radio button, Checkbox, or Dropdown menu.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575845/original/844456cc-29aa-4e89-a7ba-7fd72bbba7f6-Screenshot_2023-05-03_at_11.15.39_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>Single-value choices - You can add options containing simple values.
 Example:&nbsp; For eCommerce, allow someone to pick a shirt size from XS, S, M, L, or XL.</li><li>Key-value pair choices - You can enable the Key-value pairs option and add key-value pairs separated by a colon (:). A comma separates every choice. Only the key name is displayed on the entry page, while the value is stored in the backend database for reference.
 Example:&nbsp;You might want to specify a state's code while defining choices in a government website so that we can specify key-value pairs such as New York:NY, Texas:TX, and Dubai:DBX.</li></ul>This field has specific properties you can change anytime per your needs.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li><li>Selection Type</li><li>The limit&nbsp;for Multiple Choices</li><li>Display Type</li><li>Choice Data Type</li><li>Add Choices</li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575846/original/23118f4d-0ec0-4ae3-9841-f2d37b867e27-Screenshot_2023-05-03_at_11.17.00_AM.png" width="100"/><ul><li>Advanced<ul><li>Mandatory</li><li>Non-localizable</li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575847/original/b010a290-f9c7-4f27-84f0-8db0b1e65c3f-Screenshot_2023-05-03_at_11.17.17_AM.png" width="100"/>Quick Tips:
 You can add up to a max default count of 100 choices for a single dropdown menu.
 A key-value pair option can contain a maximum of 100 characters in length.
 Enabling or disabling the Enable key-value button erases your existing choices. Proceed with caution to avoid any loss of data.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/select/">About Select Field</a>&nbsp;</li></ul>

Select Field

The Reference field allows you to create references to entries of the same or another content type(s). It lets you access and use entries of other content types as input within your field.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575848/original/a94312b6-db00-482c-b24f-a48ccee905a5-Screenshot_2023-05-03_at_11.21.36_AM.png" width="100"/><h1>Understanding with an example</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575849/original/18439acb-6a79-41ea-9fcf-18d9b582af18-Screenshot_2023-04-03_at_10.17.37_AM.png" width="100"/>Consider a 'Blog page,' for example. There can be multiple blogs, each with the same or different authors. In such use cases, we will create two content types to avoid repeatability and create reusable components. The first content type will be 'Blog Page,' which consists of fields such as 'Title,' 'Description,' 'Image,' 'Author,' and 'Published Date.' The second content type will be 'Authors,' consisting of fields such as 'Title,' 'Description,' and 'Image.'Now you can add the 'Author' content type as a reference field in the 'Blog Page' content type. When you create an entry for the 'Blog Page' content type, you will refer to one of the entries from the 'Author' content type for the 'Author' field. When the page is rendered using <a href="https://www.contentstack.com/docs/developers/apis/">Contentstack APIs</a>, the final Blog Page will contain all the content, including the Author details.Referencing can be classified into ' Self Referencing' and 'Include Referencing.' We can further classify 'Include Referencing' into two more sub-types: ' Single Content Type Referencing' and 'Multiple Content Type Referencing.'Let's have a look at each of these with examples:<ul><li>Self-Referencing - This refers to creating references of the same content type.
 Example:&nbsp;If a user buys a mobile phone belonging to XYZ brand, they should get recommendations of headsets, chargers, or mobile phone covers of the same brand. In this case, you can create a 'Product' content type with a field named 'Recommendations' as a reference to the same content type 'Product.'</li><li>Include Referencing - This refers to creating references of another content type(s).</li></ul><ol><li>Single Content Type Referencing - Here, the Reference field allows you to create references to entries of a single content type.
 Example:&nbsp;The Blog page and Author example you have seen above best suit this. The 'Author' field in the 'Blog Page' content type references the 'Author' content type. When you create an entry for the 'Blog Page' content type, you will refer to one of the entries from the 'Author' content type for the 'Author' field.</li><li>Multiple Content Type Referencing - Here, the Reference field allows you to create references to entries of various content types.
 Example:&nbsp;For an e-commerce site, you may have primary items like Clothes, Shoes, and Bags, and you want to create a page that displays all the products of a selected brand. First, you would create content types like 'Clothes,' 'Shoes,' and 'Bags' and their entries. Then, you would make the 'Brand' content type with the necessary fields and add a 'Reference' field named 'Products' that refers to the three content types 'Clothes,' 'Shoes,' and 'Bags.' When you create an entry for the 'Products,' you can select the entries from the three referenced content types.</li></ol>The Reference&nbsp;field possesses specific properties you can change anytime per your requirements.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li><li>Referenced Content Type</li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575850/original/fdb8f91b-c33e-438e-a7e9-77aceee0f275-Screenshot_2023-05-03_at_11.21.56_AM.png" width="100"/><ul><li>Advanced<ul><li>Options<ul><li>Mandatory</li><li>Multiple</li><li>Non-localizable</li></ul></li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575851/original/a50cd537-b21b-4d40-84a8-833bc826633a-Screenshot_2023-05-03_at_11.22.04_AM.png" width="100"/>Potential Use Case:<ul><li>A reference field can be used to add links between two entries. In the Blog Entries page, the Author can be a reference entry with a separate Author Page, and it's easy to update Author details in one place in the Author content type entry due to referencing instead of each blog article of that Author.</li><li>Categories are another use case of reference where we can create a separate content type and add them as a reference in articles.</li><li>In the Navigation Menu, instead of a static link, we can add entry pages as reference menu items for each menu.</li></ul>Quick Tips:
 It's advised to limit content reference depth levels to 3 for better visibility and governance of content.
 Also, the maximum number of content types should be limited to 20 in a reference field.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/reference/">About Reference Field</a></li></ul>

Reference Field

The Group field enables users to group multiple fields. When set to ‘Multiple,’ users can create various iterations of a Group field while creating entries.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575852/original/dad0620a-7e80-4538-b915-ae9da62eec3c-Screenshot_2023-05-03_at_11.25.04_AM.png" width="100"/><h1>Video:&nbsp;Group Fields on Entries</h1>The following video provides an example of an entry that uses group fields.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/agyFGCZh-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="06.1 - Entries With Group Fields" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575853/original/b7353518-d1ab-480f-9271-bbad9048e553-Screenshot_2023-04-03_at_12.23.47_PM.png" width="100"/>Consider a 'Site Header' example. A site header may contain menus such as 'Blogs,' 'About Us', 'Features,' and 'Program.' These menus have a similar structure and serve a similar purpose. Each of these menus can be grouped using a 'Group Field' as 'Multiple,' consisting of fields like 'Link Field' that can capture the 'Title' and 'Link' of the menu items.Another typical use case for group fields is when you are tasked with creating a 'Carousel' on a page. A carousel generally contains images and some information about them. So, we can group them using the 'Group Field' as 'Multiple,' consisting of fields like 'Image,' 'Title,' 'Description,' and the 'Link Field.'The following diagram provides an example:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575854/original/27f5e2fe-ff3a-434b-b191-79394aa385fb-Screenshot_2023-04-03_at_12.35.50_PM.png" width="100"/>The Group field possesses specific properties you can change anytime per your requirements.The properties that can be modified are:<ul><li>Basic<ul><li>Display Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li></ul></li><li>Advanced<ul><li>Multiple</li><li>Non-localizable</li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575855/original/bfaff1ca-c58e-433c-8c79-659db6162481-Screenshot_2023-05-03_at_11.25.44_AM.png" width="100"/>Potential Use Case:<ul><li>FAQ is one of the real-world use cases for Group fields where editors need to create multiple combinations of questions and answers.</li><li>Group fields can be used to dedicate a section of your website for specific purposes.
 Example:&nbsp; Survey Forms where you can incorporate all the existing fields Contentstack offers to create a questionnaire. Apart from survey forms, you can also generate an online polling system, quizzes, or even a rating system.</li></ul>Quick Tips:
 You can add up to a maximum of 100 fields(including nested fields) in a group field.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/group/">About Group Field</a></li></ul>

Group Field

A Modular Block is a field that allows content managers to dynamically create and modify components of a page or app on the go.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575856/original/f851c61e-9689-480c-a295-3db3c801f42b-Screenshot_2023-05-03_at_11.27.38_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575857/original/cce5b0bb-3cd2-4005-94eb-cd9521f33326-Screenshot_2023-05-03_at_11.27.56_AM.png" width="100"/><h1>Video: Modular Block Fields on Entries</h1>The following video provides&nbsp;an example of an entry that uses modular block&nbsp;fields.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/g35Mr4US-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="06.2 - Entries With Modular Blocks" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Refer to the below diagram to better understand the concept of Modular Blocks:Consider a ‘Blog Page’ content type allowing users to create multiple entries or blog pages. Each author may have a content structure that serves content in a different order.Consider a ‘Blog Page 1 Layout’ which has fields in the order:<ul><li>Title</li><li>Description</li><li>Asset</li><li>Description</li><li>Asset</li><li>Asset</li></ul>There may be another blog, ‘Blog Page 2 Layout,’ which has fields in the order:<ul><li>Title</li><li>Asset</li><li>Description</li><li>Description</li><li>Asset</li><li>Description</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575858/original/1056b719-029b-4a25-bbbc-6c79a187d947-Screenshot_2023-04-03_at_12.50.52_PM.png" width="100"/>Both layouts use the same content type structure, ‘Blog Page,’ but the selection and order of the fields change dynamically. In such cases, you can make use of Modular Blocks. Modular blocks allow a user to publish content dynamically without any code pushes, meaning that the developer does not have to make any code changes regarding the fields on the front end.Potential Use Case:<ul><li>Dynamic Component-based content pages, e.g., Blog articles, can have different templates and content blogs with different ordering.</li><li>To show the end user something different based on their physical location (IP address), you can do so by using Modular Blocks in Contentstack.</li><li>Create Navigation with Menu items blocks for external, internal, and custom links schema fields.</li><li>Pick and choose page structure of predefined components&nbsp;for editors without relying on developers for dynamic page structuring.</li><li>Nested Blocks to create component hierarchy</li></ul>Quick Tips:<ul><li>Modular Blocks field can take&nbsp;20 blocks max by default and you can add up to 5&nbsp;Modular Blocks fields&nbsp;in a single content type.</li><li>If you have selected Single as your content type, we will be unable to set settings for the URL field.</li><li>While depth of nested blocks is 2&nbsp;the maximum number of blocks that&nbsp;can be added within a nested Modular Blocks field is 20.</li><li>The maximum number of fields that can be added to a content type is 100. When you add a Modular Blocks field to a content type, each Modular Blocks field is counted as a field, each block within the Modular Blocks field is counted as a field, and each field within a block is calculated too.</li></ul>Example:&nbsp;A content type with one Modular Blocks field that contains two blocks, each block with two fields each, will be counted as a total of 7 fields.<h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/modular-blocks/">About Modular Blocks</a></li></ul>

Modular Blocks Field

A Global field is a reusable field (consisting of a group of fields) that you can define once and reuse in any content type within your stack.This field saves the time and effort of adding the same set of fields (and their settings) in multiple content types of a stack.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575859/original/f577e226-5e89-476d-9af6-972f29a89d89-Screenshot_2023-05-03_at_11.30.39_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>If you want to capture SEO information for your website, you can do this using the Global field. You will create a Global field consisting of fields like ‘SEO Title,’ ‘SEO Description,’ etc. You can then reuse this on any page. You can select ‘Global Field’ in that respective content type.</li><li>You can use the Global field to create a Button-Link structure that can be reused across the website. You will create a Global field consisting of a ‘Link Field’ where the ‘Title will be ‘Button Title’ and ’‘Link’ will contain the actual link of the destination page/article. You can then use this button on any page or section. This field has specific properties you can change anytime per your needs.</li></ul>The properties that can be modified are:<ul><li>Basic<ul><li>Select Global Field</li><li>Display Name</li><li>Unique ID</li><li>Instruction Value</li><li>Help Text</li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575860/original/b66ab778-c7be-449a-abfe-3f1dd32cef75-Screenshot_2023-05-03_at_11.30.53_AM.png" width="100"/><ul><li>Advanced<ul><li>Multiple</li><li>Non-localizable</li></ul></li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575861/original/b10851fb-82ea-4f73-b8d5-e52e882837e3-Screenshot_2023-05-03_at_11.31.16_AM.png" width="100"/>Potential Use Case:<ul><li>Reusable SEO group field inside the global field to reuse in multiple content types and maintain.</li><li>For reusable components like Banner, CTA, and FAQs.</li></ul>Quick Tips:<ul><li>Like the number of fields in a content type is limited to&nbsp;100, same also applies for Global fields.</li><li>And you can up to 25 Global fields in a content type.
 Example:&nbsp;As we know, only 100 fields are allowed per content type. If a content type already contains two fields and if we try to include a global field containing 100 fields in this content type, then this content type field will exceed 100 and will not be allowed.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/global/">About Global Field</a></li></ul>

Global Field

The HTML Rich Text Editor (RTE) field enables users to input different types of content, such as text, images, videos, and so on. Adding an HTML-based RTE field in a content type displays a text area with editing and formatting options on the entry page.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575862/original/ace049f5-5d23-46ce-baec-2064d10b0da0-Screenshot_2023-05-03_at_11.35.19_AM.png" width="100"/> <img src="https://learnupon.s3.eu-west-1.amazonaws.com/575863/original/161d1081-347f-4507-9134-832d6d5529dd-Screenshot_2023-05-03_at_11.37.03_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575864/original/914d4373-9bac-4f85-80a1-e9af17dcb4d0-Screenshot_2023-05-03_at_11.37.17_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575865/original/aea52378-1345-42ed-9779-3c189b5aab7f-Screenshot_2023-05-03_at_11.37.45_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>If you want to capture and format a description that includes text and images for the definition of a Blog Page or any Article, you can use HTML-based Rich Text Editor.</li></ul>The HTML-based Rich Text Editor (RTE) &nbsp;stores content as strings in HTML format.This field allows you to edit and format content entered in the field without using HTML tags (however, you can use HTML tags in the HTML mode, if needed).Besides choosing between the Basic and Advanced editors, developers can choose the Custom editor when adding the HTML-based RTE field to content types.The Custom editor allows you to choose from various formatting options and control what will be available in the HTML-based RTE toolbar for content managers.<h1>Best Practices To Use</h1><ul><li>Use this to embed entries and assets within the HTML-based Rich Text Editor, which are automatically updated within the Rich Text Editor field whenever the source entry or asset is updated. You can do this by checking the ‘Embed Objects’ in the ‘Advanced’ section of the HTML-based Rich Textor Editor.</li></ul>Potential Use Case:<ul><li>Embed entry inline - To pass in some value from a linked entry that might be dynamic, such as a working title or a link that opens a modal popup.</li><li>Embed entry as a block - To add descriptive image carousels, survey forms, or product listings.</li><li>Embed entry as a hyperlink - To add a hyperlink in the RTE that changes dynamically whenever any updates are made.</li><li>Displayable embedded images - Such assets are dynamically updated in the front end whenever you change the source item in the asset manager.</li><li>Downloadable Images or Files - Such items are usually PDFs or other reference file formats with a handy download link.</li></ul>Quick Tips:<ul><li>At any given time, you can&nbsp;combine&nbsp;a total of 100 entries and assets to&nbsp;be embedded inside a single RTE field.</li><li>A maximum default count of 10 content types can be selected for a Single RTE as a reference&nbsp;including&nbsp;embedded assets.</li><li>Any references within the embedded entry will not be resolved.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/rich-text-editor/">About Rich Text Editor Fields</a></li></ul>

HTML-based Rich Text Editor Field

The JSON Rich Text Editor (RTE) field is a block-style rich text editor that enables users to add different types of content. It stores content in structured JSON blocks containing text, images, videos, etc.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575866/original/9500b714-ea91-46ac-ab3e-126db2d7fcba-Screenshot_2023-05-03_at_11.40.37_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575867/original/9e40b4ae-1b98-4e0f-83a8-0748393f9408-Screenshot_2023-05-03_at_11.40.51_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575868/original/40be8d36-2f8f-435a-a019-e236a3d3f589-Screenshot_2023-05-03_at_11.41.11_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575869/original/60cace29-e294-44f5-8a7f-185859898a2e-Screenshot_2023-05-03_at_11.41.28_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>If you want to capture and format a description that includes text, and images, say, for the description of a Blog Page or any Article, you can use JSON Rich Text Editor.</li></ul>JSON Rich Text Editor stores content in structured JSON blocks containing text, images, videos, etc.Adding a JSON RTE field in a content type displays a text area with editing and formatting options on the entry page. This field allows you to edit and format content entered in the field without using HTML tags.Besides choosing between the Basic and Advanced editors, developers can choose the Custom editor when adding the JSON RTE field to content types.The Custom editor allows you to choose from the various formatting options and control what will be made available in the JSON RTE toolbar for content managers.You can type in the forward slash ("/") in your JSON Rich Text Editor to open a list of formatting options to style your content.Contentstack also includes the 'JSON RTE Comments'&nbsp;feature that allows you to add comments within the JSON Rich Text Editor. This feature helps you collaborate efficiently with other Contentstack users during content creation and review processes. We will take a look a this in our next video.Potential Use Case:<ol><li>It provides built-in syntax formatting for more than 60 programming languages.
 Examples:&nbsp;JavaScript, HTML, Python, etc.</li><li>You can create custom plugins or use existing marketplace apps like Aprimo, Cloudinary, etc., which will be available as an option in the formatting panel.</li></ol><h1>Real World Use Cases</h1><ul><li>Compared to HTML RTE, JSON RTE response can be in JSON format, which is easy to configure on different devices.</li><li>Formatting content is easy for editors.</li><li>Embed entry inline - To pass in some value from a linked entry that might be dynamic, such as a working title or a link that opens a modal popup.</li><li>Embed entry as a block - To add descriptive image carousels, survey forms, or product listings.</li><li>Embed entry as a hyperlink - To add a hyperlink in the RTE that changes dynamically whenever any updates are made.</li><li>Displayable embedded images - Such assets are dynamically updated in the front end whenever you change the source item in the asset manager.</li><li>Downloadable Images or Files - Such items are usually PDFs or other reference file formats with a handy download link.</li></ul>Quick Tips:<ul><li>You can add 10 JSON RTEs&nbsp;per content type and 100 Entries embedded to one.</li><li>The maximum JSON RTE field data size limit (in bytes) is 30000 (30 KB).</li><li>A maximum of 15 content types can be selected as references for a single JSON RTE.</li><li>The maximum number of instances for JSON RTEs marked as "Multiple" is 100.</li><li>During migration, both the HTML-based and JSON RTEs should be at the same level of field depth to migrate content successfully.</li><li>If the JSON RTE is marked as "Multiple" and HTML RTE is of "Single" type, you won't be able to migrate content.</li><li>The HTML RTE and JSON RTE should allow embedded entries from the same referenced content types during migration. If the referenced content types differ, you cannot migrate content between the RTEs.</li><li>You can have multiple discussions within the JSON Rich Text Editor.</li><li>One active discussion can be associated with each selected content block, text, and image within the JSON RTE.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/json-rich-text-editor/about-json-rich-text-editor/">About JSON Rich Text Editor</a></li></ul>

JSON Rich Text Editor Field

Field Visibility&nbsp;Rules allow you to display or hide fields on an entry page based on the value entered.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575870/original/9f82ed57-3531-4228-b636-082613605e4f-Screenshot_2023-05-03_at_11.45.50_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575871/original/92114afa-9a42-4821-9d82-e7c0059daccb-Screenshot_2023-05-03_at_11.46.02_AM.png" width="100"/><h1>Understanding with an example</h1><ul><li>While checking out from an online shopping site, selecting the ‘The Same as Shipping Address’ field hides the ‘Billing Address’ field automatically.</li><li>When you select Gender as Male, it automatically adds ‘Mr.’ before the First Name field and hides the ‘Ms./Mrs.’ title.</li><li>While filling out a job form, if you answer the ‘Do you have any prior experience?’ field as ‘Yes,’ it shows the ‘Years of experience’ field while selecting ‘No’ does not.</li></ul>You can define Field visibility rules while creating or editing a content type. Only the stack owner, admins, and users assigned ‘Developer’ roles have the right to make a Field visibility rule in the stack.The list of operators that can be used to set the visibility rules can be found <a href="https://www.contentstack.com/docs/developers/create-content-types/operand-fields-and-supported-operators/">here</a>.Quick Tips:<ul><li>While you could easily add up to 10 rules per content type, with max of 5 conditions per rule.</li><li>And target as many as 5 fields for each rule.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/about-field-visibility-rules/">About Field Visibility&nbsp;Rules</a></li></ul>

Field Visibility Rules

Get ready to witness the incredible abilities of our esteemed content creators! Meet Lightning Bolt, the unrivaled master of speed and creativity, Thunder Monarch, the precise and skilled Grammarian, and Demo Almighty, the media mogul from Composable Heroes. Together, they are about to unleash the full potential of Contentstack, utilizing its powers to create captivating content for the Hall of Heroes and the Hero Details Page.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575811/original/21008db9-1900-47cf-9158-6bfbce43d630-Screenshot_2023-05-05_at_1.49.00_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575812/original/ee4c84cc-c689-4564-a83f-b227b8bb2dab-Screenshot_2023-05-05_at_1.48.42_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575813/original/f58ea62b-7139-4474-bb90-3b75fa5ae7b0-Screenshot_2023-05-05_at_1.50.00_PM.png" width="100"/> The goal is to produce content for:<ul><li>Hall of Heroes (with images, names, and brief information about them)</li><li>Hero Details Page (includes detailed information about the heroes, their powers, and the message)</li></ul>In their quest to reach a global audience, our talented creators will craft captivating content in multiple languages. They will showcase mesmerizing images, heroic names, and intriguing information in the Hall of Heroes while providing detailed insights into each hero's powers and message on the Hero Details Page. With their expertise in managing multiple content versions, they will navigate the ever-changing content landscape. Embark on an exhilarating journey of content creation, management, and localization with Contentstack as your guiding companion. Unleash your creative superpowers and join these extraordinary content creators!In this episode, you'll learn how to create, manage and localize the content.

Building the Content

In Contentstack, any files (images, videos, PDFs, audio files, and so on) that you upload get stored in your repository for future use. This repository of uploaded files is called Assets.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575874/original/f98cec82-de2a-4fe0-81ee-aa4473eb72d1-Screenshot_2023-05-03_at_11.54.41_AM.png" width="100"/><h1>Video: How to Use Assets in Contentstack</h1>The following video shows how to manage assets in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/tBpN3sUE-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="07 - Assets" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Exercise 3 Video</h1>Follow along with the video to practice using Assets.<iframe src="https://www.youtube.com/embed/w_BJ5gkGX80" allowfullscreen="" frameborder="0"></iframe><h1>Understanding with an example</h1><ul><li>If you want to upload an Author's Image for a Blog post, you can upload the image in the assets. You can then use or reference the asset in any entries with a field for assets.</li></ul>Once you upload a file to your Assets repository, you can attach it to any entry. This is especially useful when using certain assets in multiple entries.You can perform the following actions on assets:<ul><li>Upload assets to your stack.</li><li>Update asset details.</li><li>Delete assets permanently from your stack.</li><li>Publish assets to a specific environment(s) and locale(s).</li><li>Unpublish assets from the particular environment(s) and locale(s).</li><li>Locate assets easily using filters.</li></ul>To organize assets, you can create folders in the ASSETS section of Contentstack. You can maintain your assets in a nested folder structure, creating folders within folders with a maximum depth of five levels.An asset has the following metadata associated with it:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575875/original/305ac26d-8451-4490-b276-1d03ada433ed-Screenshot_2023-04-04_at_11.13.04_AM.png" width="100"/><ul><li>Title - Defines the Title for the image and will initially be the file's name that gets uploaded. You do have the option to change the Title.</li><li>Description and Tags - Both of these fields are optional. You can provide a basic description of the image while adding tags helps to search/filter the image based on tag names.</li><li>Filename - Defines the name of the file that gets uploaded to the assets.</li><li>Unique ID - Defines the unique identifier for the image.</li><li>File URL - Defines the URL of the image stored in assets and can be used to serve the image on your website. Clicking on the URL copy's the URL text, which you can use to open the image.</li><li>Permanent URL - Create a permanent URL by specifying a custom name for the image name in the URL.</li><li>File Location - Change the location of an image in the assets by clicking on the 'Change' option.</li><li>Type, File Size, Resolution, Created By, Created At, Last Modified By, Modified At - These are the basic properties that define the metadata of an image.</li><li>Referenced In - Provides information about which Content-Type and Locale the image are referenced.</li></ul><h1>Real World Use Cases</h1><ul><li>Contentstack provides a digital asset management feature with the Asset module to help manage assets and easily reference them on web pages.</li><li>Editors can organize assets in folders and filter based on the type of assets.</li></ul>Quick Tips:<ul><li>For ease of management a folder can have default max of 500 asset.</li><li>And a multi level hierarchy of 5 levels.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/content-managers/author-content/about-assets/">About Assets</a></div></li><li><div><a href="https://www.contentstack.com/docs/faqs/#assets-faqs">Assets FAQ</a></div></li></ul>

Assets

<h2>Hello folks!&nbsp;</h2>Now that you have a good hold over the major entities in Contentstack, it's time to try some of those immediately.<ul><li>Download the images in the next module. (You can choose any random video for the video portion)</li><li>Navigate to the Assets area.</li><li>Create a new FOLDER &nbsp;to upload assets. The name of the folder should be New Heroes.</li><li>Upload new ASSETS for&nbsp;the following heroes.</li></ul><ol><li>One Image&nbsp;for a Hero 'Wild West Warrior'</li><li>ONE Video for a Hero&nbsp;'Royal Defender'</li><li>ONE Image for a Hero 'Royal Defender'</li></ol><ul><li>Open the image related to the hero 'Wild West Warrior' and change the TITLE and GENERATE PERMANENT URL. Save the changes.</li><li>Open the video related to the hero&nbsp;'Royal Defender' and replace the video with the image provided for the hero 'Royal Defender' using the Replace button. Make sure to upload the image in the same folder.</li></ul>Bingo! You have completed this&nbsp;exercise successfully. Go ahead to submit the output&nbsp;of your practice.

Assets Exercise

An entry is an actual piece of content that you want to publish. You can only create entries with existing content types.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575873/original/d334c764-4a91-4792-b1b2-250528907abf-Screenshot_2023-05-03_at_11.52.10_AM.png" width="100"/>Once an entry is created(saved), a new version is generated. We will take a look at the versioning in the upcoming episodes.<h1>Video: Entries</h1>The following video&nbsp;provides an overview of Entries in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/XhKsfeWl-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="06 - Entries" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Exercise 4&nbsp;Video</h1>Follow along with the video to practice using Entries and Content Types.<iframe src="https://www.youtube.com/embed/68RuzSsLX6c" allowfullscreen="" frameborder="0"></iframe><h1>Understanding with an example</h1><ul><li>If you have created a content type, ‘Blog Page,’ you can create a new entry for this content type.</li></ul>The number of entries that can be created depends on the content type you have made. If the type is ‘Single’ for a content type, you can only create a single entry. You can create multiple entries if the type is ‘Multiple’ for a content type.Once an entry has been created, you can find the basic information/metadata about that entry on the right sidebar.The metadata includes information such as the following:<ul><li>Entry ID&nbsp;- Defines the unique ID for an entry.</li><li>Content Type ID&nbsp;- Defines the unique Content Type ID for an entry.</li><li>Created By&nbsp;- Defines the name of the user who created the entry.</li><li>Created At&nbsp;- Defines the date and time when the entry is made.</li><li>Modified By&nbsp;-&nbsp;Defines the name of the user who modified the entry.</li><li>Modified At&nbsp;- Defines the date and time when&nbsp;the entry is modified.</li></ul>Apart from these, you can learn about ‘In which Content Type this entry is referenced’ and its ‘Localization Status.’ We will be looking at metadata in the video walkthrough below.You can perform the following actions on entries:<ul><li>Create and Update entries.</li><li>Delete entries permanently from your stack.</li><li><a href="https://www.contentstack.com/docs/content-managers/author-content/publish-an-entry/">Publish entries</a> to a specific environment(s) and locale(s).</li><li><a href="https://www.contentstack.com/docs/content-managers/author-content/unpublish-an-entry/">Unpublish entries</a> from the particular environment(s) and locale(s).</li><li>Locate entries easily using search and labels.</li></ul>Entry Comments:Contentstack’s ‘<a href="https://www.contentstack.com/docs/content-managers/author-content/about-entry-comments/">Comments</a>’ feature allows you to add comments to fields in the entry editor and collaborate with other Contentstack users across the content creation and review processes. You can add a comment or mention other users using the “@” character.Entry Tags:&nbsp;Contentstack provides a ‘<a href="https://www.contentstack.com/docs/developers/how-to-guides/reference-field-vs-select-field-vs-tags-field/#tags">Tag Field</a>’ default entry field. Whenever you create a new entry, you can add tags to that entry. The applied tags are visible on the entry list page. It is best to use tags if you plan to search entries using Contentstack’s Advanced Search. This is not recommended if you wish to retrieve entries (by filtering) using APIs.Quick Tips:<ul><li>While the max query limit is 100 for the Reference field.</li><li>You can Tag up to 50 tags per Entry.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/content-managers/author-content/about-entries/">About Entries</a></div></li></ul>

Entries

<h2>Hello folks!&nbsp;</h2><ul><li>Create new&nbsp;ENTRIES for the 'Character' Content Type&nbsp;with the following heroes.</li></ul><ol><li>Royal Defender</li><li>Wild West Warrior</li></ol><ul><li>In the above entries, add appropriate content like Name, Description, Powers, etc.&nbsp;(Make sure you fill all the fields)</li><li>ADD the appropriate ASSETS that you uploaded in&nbsp;Assignment 1.</li><li>SAVE the entries.</li><li>Navigate to the&nbsp;'Composable Heroes'&nbsp;entry (Super Hero Gallery Page Content Type).</li><li>In the Character field, click Choose Existing Entry&nbsp;and select&nbsp;the character entries 'Royal Defender' and 'Wild West Warrior' to reference them.</li><li>Click add selected references.</li><li>SAVE the entry.</li><li>Navigate to the&nbsp;'Composable Heroes Landing Page'&nbsp;entry (Super Hero Landing Page Content Type). &nbsp;</li><li>Add the&nbsp;modular block named 'Hero Banner' and fill in the details.</li><li>SAVE the entry.</li></ul>Bingo! You have completed the exercise successfully.&nbsp;Go ahead to submit the output of your practice.

Entries Exercise

Contentstack allows users to create multiple entry and asset versions of the content.<h1>Video: Versioning</h1>The following video provides an overview of how versioning works in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/YnZtuFYE-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="08 - Versioning" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Entry Versioning:<ul><li>It helps users to view, manage, and compare the content of the required versions.</li><li>By default, entry versions are identified with numbers. For each new version created (upon entry save), the version is incremented &nbsp;(e.g., Version 1, Version 2, and so on).</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575880/original/ca83a76b-d7d7-4e2b-8673-6925acfab959-Screenshot_2023-05-03_at_12.00.08_PM.png" width="100"/>Asset Versioning:<ul><li>When you update an asset by changing the file, title, description, or tags, Contentstack creates a new asset version. This allows you to view the asset's previously saved/published versions, get the publishing details (who published it, when, and where), consider the older version, and restore the earlier version if required.</li><li>By default, asset versions are identified with numbers (e.g., Version 1, Version 2).</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575881/original/d6f85b5a-fb55-4964-9a05-3278bf645ba8-Screenshot_2023-05-03_at_11.59.53_AM.png" width="100"/>For easy identification, you can re-assign/rename a version name (e.g., Christmas Sale, Production Ready, Do Not Edit) to an entry/asset version.Potential Use Case:<ul><li>Versioning is a great feature to keep track of all content update history and is helpful for editors to hassle-free roll back to previous versions.</li><li>Users can assign proper names to each version, according to their choice, for easy identification.
 Example: You can set ‘Friday Sale’ as a version name for entry with Content of Promotion which could be scheduled for a specific duration and can be rollback to the previous version.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/content-managers/author-content/understanding-entry-versions/">About Entry Versions</a></li><li><div><a href="https://www.contentstack.com/docs/content-managers/author-content/about-asset-versioning/">About Asset Versions</a></div></li></ul>

Versioning

Contentstack has a sophisticated, multilingual content capability. It allows you to create and publish entries in any language. When creating entries in other languages, they inherit data initially from the fallback language until they are localized.Contentstack comes with over <a href="https://www.contentstack.com/docs/developers/multilingual-content/list-of-supported-languages/">200 pre-configured locales</a> and their respective language codes. Further locales can be added through the Contentstack interface.Every Stack has a master language as default while creating the Stack. And once we add languages to our Stack, localization can be added to an entry.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575876/original/c3cfe553-1b76-4202-878c-d923367e2f4c-Screenshot_2023-05-03_at_12.02.51_PM.png" width="100"/><div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/MdoxfEpV-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="09 - Localization" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Video: Localization in Contentstack</h1>The following video&nbsp;provides an overview of&nbsp;how to work with localization in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/MdoxfEpV-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="09 - Localization" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Consider a stack whose Master or Default language is English(United States). We can add multiple other languages to the stack, such as French(France), French(Belgium), Spanish(Spain), Spanish(Mexico), etc.&nbsp;While adding a new language, you should select its fallback language.Take a look at the diagrams below to better understand how languages and fallback languages work in Contentstack:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575877/original/e251abb5-335e-4142-a8c8-323f81dba2e7-Screenshot_2023-04-06_at_3.51.21_PM.png" width="100"/>Fallback language:A fallback language is the parent language from which a given language inherits data. It need not necessarily be the Master or Default language.
 Example:&nbsp;In the diagram below, English(United States) is a fallback language of French(France), and French(France) is a fallback language of French(Belgium). Suppose an entry is created in English(United States). When you try to switch this entry to French(France), and it is unlocalized, it will fetch the entry content from English(United States). Similarly, when you switch this entry to French(Belgium), and it is unlocalized, it will fetch the entry content from French(France), which is subsequently brought from English(United States).Localization:Consider a scenario where a ‘Blog Webpage’ wants to fetch published content from the English(United States) language. The content is brought from the ‘Blog Entry’ English(United States). Now, consider another scenario where the ‘Blog Webpage’ wants to fetch published content from the French(France) language, but the entry has not yet been localized for the French(France). In this case, the content is fetched from its fallback language, i.e., English(United States). Also, it will serve the same version of entry as that of English(United States).<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575878/original/1492763c-be61-41e7-90ab-0648b9854d41-Screenshot_2023-04-03_at_4.06.29_PM.png" width="100"/>Now, consider another scenario where the ‘Blog Webpage’ wants to fetch published content from the French(France) language, and the entry has been localized for the French(France). In this case, the content is fetched from French(France), and it will cease to bring entry from its fallback language, i.e., English(United States). Also, it will create a new version for that entry.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575879/original/58d17717-53f5-47f1-b3cc-8057f721aa0b-Screenshot_2023-04-03_at_4.20.47_PM.png" width="100"/>
 Potential Use Case:<ul><li>Localization is a great feature to solve a use case where we need multiple copies of the same content in different languages and countries.</li><li>Using the Custom Locale feature, you can achieve some use cases where you want to copy content for a specific country irrespective of language.</li></ul>Quick Tips:<ul><li>Contentstack&nbsp;allows one level of data inheritance for fallback languages and limits from&nbsp;adding a fallback language (other than the master language) for the language that is already set as a fallback for another language.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/developers/multilingual-content/about-localization/">About Localization</a></div></li><li><div><a href="https://www.contentstack.com/docs/developers/multilingual-content/about-fallback-languages/">About Fallback Languages</a></div></li></ul>

Localization

<h3>Publishing Power</h3>"A Knowledge Assimilated without Application is of no Use"&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;-&nbsp;The Technomancer (Wisdom weaver from Composable Heroes)Understanding the significance of serving content from Contentstack to the website is crucial. Just as Technomancer carefully chooses the perfect commander for each role, he has assembled a team of Content Managers led by Royal Sanctuary. Together, they are eager to delve into the world of previewing and serving content, seeking to expand their knowledge in this realm.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575814/original/51009665-c79d-42a8-b331-f83020cefe15-Screenshot_2023-05-05_at_2.04.58_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575815/original/7800472c-eb10-406d-bcdb-ad0322848bde-Screenshot_2023-05-05_at_1.49.43_PM.png" width="100"/> The team requires assistance in:<ul><li>Previewing content changes before they are served on the website</li><li>Managing multiple content types&nbsp;at the same time</li><li>Removing content from the website as needed</li></ul>The Technomancer can foresee&nbsp;that it's time to make the content available to the general public.In this episode, you'll learn how to publish, unpublish and track the same for content.<h1>What are Environments?</h1>A publishing environment refers to one or more deployment servers or a content delivery destination (webpage address) where you will publish your content (entries or assets).An environment allows users to publish their content on the destination URL. After you create an entry, you will publish it on an environment.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575882/original/65f39d59-4066-4433-8ab6-b331740e148a-Screenshot_2023-05-03_at_12.07.06_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575883/original/c7470feb-b6eb-4c34-a78e-c0cc69a8678b-Screenshot_2023-05-03_at_12.07.24_PM.png" width="100"/><h1>Understanding with an example</h1>In a real-world scenario, Developers may publish their content to the ‘Development’ environment to test their changes before handing it over to the QA team. The QA team can test the content on a separate ‘QA’ environment. A client can try the same on their own ‘UAT(User Acceptance Testing)’ environment before publishing it onto the Production environment.Each environment may serve the same or different versions of content.The most common publishing environments used are development, staging, and production.The diagram below provides an example:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575884/original/bfaab628-646a-4896-8eb4-c918e47ed73d-Screenshot_2023-04-03_at_4.52.28_PM.png" width="100"/>Potential Use Case:<ul><li>By setting up Testing, Staging, and Production environments, content changes can go through multiple checkpoints before its released&nbsp;to production to mitigate any breaking changes.</li><li>Environments help segregate&nbsp;content for platforms or devices(Mobile/Desktop).</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/developers/set-up-environments/about-environments/">About Environments</a></div></li></ul>

Environments

Live Preview allows content managers to preview content without publishing it to an environment or saving the changes made. The content changes you make reflect in the preview pane in real-time.You can also preview your content changes across multiple channels, such as mobiles, tablets, and desktops. This flexibility allows you to ensure website content looks precisely how you intended and thus helps achieve omnichannel content delivery.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575885/original/38d93834-57f9-4ba1-8df7-53e58eb17e94-Screenshot_2023-05-03_at_12.09.52_PM.png" width="100"/><h1>Video: Contentstack's Live Preview</h1>The following video&nbsp;demonstrates the Live Preview feature.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/47pShahE-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="17 - Live Preview" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Content managers always preview their content before deploying it on production. With the Live Preview feature, you can edit your content and view the changes you make in real-time without saving or publishing to a live website.To do this, perform the following steps:<ul><li>Once the developer has configured Live Preview for your stack, you can preview entry content across all entries of your stack. Click on the Live Preview icon in the right sidebar of the entry editor page to open the preview window for your entry.</li><li>While hovering over blocks in the preview pane, you will see an Edit button. If you need to edit any block, click on this edit button to be redirected to the corresponding field on your entry page.</li><li>If a block of content is referenced from another entry, when you click the Edit button, you will be redirected to the corresponding field within the specific entry. Make changes to the field and watch them reflect in the preview pane in real-time.</li><li>Once you know the changes, you can publish your content to the production site.</li></ul>We will be looking into publishing in the upcoming episodes.Potential Use Case:<ul><li>Live Preview is an excellent feature for editors to preview content changes hassle-free and quickly while editing any field content in a side-by-side panel without saving and publishing to reduce overall time to audit changes.</li><li>Live Preview also allows some amount of device specific previews like Desktop and Mobile view.</li></ul>Quick Tips:<ul><li>Live Preview feature can be configured&nbsp;for websites build with&nbsp;Contentstack's REST APIs integration and does not work for websites that use a third-party website builder or CMS to generate HTML.</li><li>Currently Live Preview&nbsp;not compatible with native mobile applications and the preview&nbsp;websites must be hosted over HTTPS.</li><li>You can configure&nbsp;tight User Access and Roles around Live Preview to decide what user role have permission to a specific environment or language in which the entry has been published to access to Live Preview.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/content-managers/author-content/about-live-preview/">About Live Preview</a></div></li><li><div><a href="https://www.contentstack.com/docs/content-managers/author-content/live-preview-real-world-scenarios/">Live Preview Scenarios</a></div></li></ul>

Live Preview

Once you create an entry/asset and have environments in place, you can publish to them. By publishing, you get the content served in that particular environment.<h1>Video: Publishing Content in Contentstack</h1>The following video&nbsp;demonstrates how to publish content in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/pLd6IcJj-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="10 - Publishing" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1><ul><li>If you have a ‘Blog entry’ that you want to display on your website, you will need to publish it to make it available on your website. Once you publish it on a particular environment like ‘development,’ you can fetch that entry using the API on your website.</li></ul>While publishing, the following options will appear:<ul><li>The environment - You can select the environment(s) to which you want to publish the entry.</li><li>The language - You can select which language to publish the entry.</li><li>The time of publishing(Now/Later) - You can choose the time to publish the entry. If you choose ‘Now’ and proceed, the entry will be published immediately. If you choose ‘Later,’ you will be asked to select the date and time. Once you set the date and time and proceed, the entry will get published on the specific date and time.</li><li>With or without the references attached to the entry - When you complete selecting the above options, you will be prompted to ask to proceed with ‘With References’ or ‘Without References.’ Suppose your entry consists of any referenced entries and assets. In that case, you can select ‘With References,’ which will publish the main parent entry and its references and assets. However, you can choose and select ‘Without References,’ which will only publish the main parent entry.</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575886/original/3ef0c8db-9a21-4ed7-b0af-acc2d594ae2d-Screenshot_2023-05-03_at_12.17.21_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575887/original/43c3a113-a4a4-41b7-b92d-8100850ce578-Screenshot_2023-05-03_at_12.12.25_PM.png" width="100"/>Similarly, you can Unpublish the published entries and assets using the ‘Unpublish’ option in an entry and asset. When you unpublish the content, it will cease to serve the content on your website for that particular environment and language.Potential Use Case:<ul><li>Publishing is a feature to make content available for&nbsp;the presentation layers to specific environments or languages.</li><li>To schedule publishing and unpublishing of content for a timed Business need, like a holiday promotion banner or&nbsp;a new product launch notice where you need a certain content on the website for a specific duration.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/content-managers/publish-content/">About Publishing Content</a></div></li></ul>

Publishing

When the Content Manager publishes an entry and asset, the system puts the action into a publish queue.Publish/unpublish activities in this queue are performed one at a time, almost at high speed. This eliminates waiting for an entry to be published before moving on to the next item. You can keep publishing items and let the system manage the queue.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575888/original/57258ff5-b803-4072-9909-9d140c0d5736-Screenshot_2023-05-03_at_12.19.46_PM.png" width="100"/><h1>Video: The Publishing Queue</h1>The following video&nbsp;provides an overview of&nbsp;the publishing queue.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/LmSs8X5n-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="11 - Publish Queue" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1><ul><li>If you publish an entry for a Blog post/article, the entry and all its referenced entries and assets are sent for publishing, which can be tracked in the Publish Queue.</li></ul>Whenever you publish an entry or an asset, Contentstack attaches a publish status icon to the corresponding publishing environment for that item on the entries list page. This publish status icon either appears as an ‘i’ icon or a ‘clock’ icon.The ‘i’ icon either appears in green or orange color.Each color indicates specific information about the publishing status of the entry or asset in that particular environment.Let’s understand what the different colors of the publish status icon (i) stand for:<ul><li>Green - Indicates that the latest version of the entry has been published to the specified environment.</li><li>Orange - Indicates that an older version of the entry has been published to the specified environment.</li><li>The ‘clock’ icon appears&nbsp;gray and indicates that an entry has been scheduled for publishing later.</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575889/original/d6adc9ea-7be7-4ed6-b037-1607ba04f24b-Screenshot_2023-05-03_at_12.21.32_PM.png" width="100"/><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/content-managers/publish-content/view-publish-status-of-entries-assets-in-publish-queue/">About Publish Queue</a></div></li></ul>

Publish Queue

You can define a ‘Release’ as a set of entries and assets that must be deployed (published or unpublished) simultaneously to a particular environment.This is useful, particularly at the time of an event or announcement, or product update.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575890/original/9b0cd042-d663-45af-b1f6-38352c048828-Screenshot_2023-05-03_at_12.24.38_PM.png" width="100"/><h1>Video: Releases in Contentstack</h1>The following video&nbsp;shows how to manage releases in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/mQ3RYpaQ-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="12 - Releases" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Exercise 5 Video</h1>Follow along with the video to practice publishing in Contentstack.<iframe src="https://www.youtube.com/embed/WjG-XKgtJe8" allowfullscreen="" frameborder="0"></iframe><h1>Understanding with an example</h1><ul><li>If you have a product launch, press release, or sales promotion and you have to publish multiple entries/assets at one go without consuming more time, you can create a ‘Release,’ add those entries/assets to the release, and ‘Deploy’ it at the specified time that you need.</li><li>You can even schedule the release action(publish/unpublish).</li></ul>You can create a new ‘Release’ from the release page by clicking on the left sidebar, ‘Release Icon.’ Once the release is created, you can add the entry and assets from an entry page. After you open an entry, you can click on the ‘Three Dots’ at the bottom right and click ‘Add To Release’ which will prompt you with a dialog box to select the &nbsp;‘Release’ and choose to add it to the ‘Publishing’ or ‘Unpublishing’ action. You can also create a new ‘Release‘ from the dialog box by clicking on ‘Create New Release.’You can deploy the release from the release page by clicking on ‘Deploy’ and selecting the environments and time to deploy.Contentstack also allows you to update items (assets and entries) in a release to their latest versions. This feature helps you publish up-to-date content whenever you deploy the release to an environment. You can collectively update all items in the release to their latest versions and choose not to update any particular item individually.You cannot update the release items under the following scenarios:<ul><li>If the release is locked(A release gets locked when you deploy it at least once).</li><li>If the updated version of an entry has new references, the references are not automatically added to the release. You need to add them manually.</li><li>If the latest version of an entry is in the in-progress state, you cannot update the entry.</li></ul><h3>Best Practices To Use</h3><ul><li>Always use this to address events that need to do the bulk publish/unpublish activity.</li></ul>Potential Use Case:<ul><li>Always use this to address events that need to do the bulk publish/unpublish activity like&nbsp;bulk publish content for specific promotions where all editor's teams add and review entries to a release before publishing.</li><li>Promotions are a good use case where we can create a release of entries and assets and set promotion content for a specific duration using scheduled publishing and unpublishing release items.</li></ul>Quick Tips:<ul><li>The Release title can be up to 50 character&nbsp;long.</li><li>The maximum number of items that can be added to a Release is 500 and in a single instance via API, is 25.</li><li>The 'Update release items to their latest versions'&nbsp;this option does not automatically update new references and needs to be done manually and don't update the release entries with the latest in-progress version.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/content-managers/create-and-manage-releases/about-releases/">About Releases</a></div></li></ul>

Releases

<h2>Managing Processes</h2>The Lightning Excavator is concerned about the content available for&nbsp;all Composable Heroes. Initially, he had assigned a few users to the Stack, but it appears that more users will be required as more content is created.The next challenge is ensuring all users adhere to a streamlined content delivery process. Royal Sanctuary will lead this operation. It's time for you to delve into Contentstack's&nbsp;management capabilities to provide solid content organization.Goals that must be attained:<ul><li>Add new users to the account.</li><li>Create an order of steps to manage the content delivery process.</li><li>Examine the content and make suggestions for improvements.</li></ul>The entire Composable Heroes team is eager to harness this power.In this episode, you'll learn how to add and manage users and user roles, content workflow, and other content management tools.<h1>What are User and User Roles?</h1>All accounts registered with Contentstack are known as Users. A stack can have many users with varying permissions and roles. Users with the required permissions can invite others to collaborate on a stack.User Roles prescribe what information the Authorized User can access, use, and disclose within the Contentstack.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575891/original/9f97cafa-05c6-4705-b45f-7affdb6107d1-Screenshot_2023-05-03_at_12.58.50_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575892/original/ec74686d-922b-4f45-8da7-c51f9813082a-Screenshot_2023-05-03_at_12.58.56_PM.png" width="100"/><h1>Video: Users, Roles and Permissions in Contentstack</h1>The following video&nbsp;shows&nbsp;how to add users and&nbsp;roles, and how to manage permissions in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/pOaHUNPa-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="13 - Users And Custom Roles" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1>Contentstack provides four user roles out of the box, namely:<ul><li>Owner&nbsp;-&nbsp;Each stack can have only one Owner. Creating a stack in Contentstack makes you the Owner of the stack.</li><li>Admin&nbsp;-&nbsp;The Admin role has more rights than a Developer and fewer than the Owner.</li><li>Developer&nbsp;-&nbsp;A Developer&nbsp;is a person who creates the site's structure or defines the way content will appear on the site.</li><li>Content Manager -&nbsp;A Content Manager&nbsp;is a user who works with/on the content of a stack.</li><li>Custom Role -&nbsp;In addition to the predefined system roles,&nbsp;you can add custom roles by defining specific permissions and assigning these roles to the users of a stack. You have fine-grained control over permissions. You can set permissions at the entry, field, and asset levels.
 Examples:</li></ul><ol><li>The&nbsp;'Content Writer' role can WRITE only entries of a content type.</li><li>The 'SEO Expert' role can EDIT only the SEO fields for entries of a content type.</li><li>The 'Content Publisher' role can READ and PUBLISH only entries of a content type.</li></ol>The diagrams below depict the User Role Privileges:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575893/original/59a724b2-87f8-4702-a703-74cb1ec28d50-Screenshot_2023-04-06_at_1.00.42_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575894/original/9d744d74-529d-4556-865f-48d9abbb3786-Screenshot_2023-04-03_at_5.44.38_PM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575895/original/28fbdf5e-bfcb-4887-8954-ea8ff4e60514-Screenshot_2023-04-03_at_5.48.59_PM.png" width="100"/>Potential Use Case:<ul><li>User Roles are essential to set up accessibility across the stack based on usage and user tasks. Content Editors need access to entry but not content modeling.</li><li>Custom roles can be used to set up:</li></ul><ol><li>Entry-level Permissions -&nbsp;All permissions to the “Products” content type entries.</li><li>Field-level permissions -&nbsp;CANNOT EDIT the Description field of the Products entry.</li><li>Asset-level permissions -&nbsp;Specific permissions on specific assets or assets folders.</li><li>Language-level permissions -&nbsp;Translation role to perform translation activity to a specific language with certain permissions.</li><li>Environment</li></ol>Quick Tips:<ul><li>The default maximum number of users that can be added in an organization is 1000.</li></ul><h1>Further Reading</h1><ul><li><div><a href="https://www.contentstack.com/docs/developers/invite-users-and-assign-roles/about-stack-users/">About Stack Users</a></div></li><li><div><a href="https://www.contentstack.com/docs/developers/invite-users-and-assign-roles/types-of-roles/">Different Types of Roles</a></div></li></ul>

Understanding the Management Tools

A workflow lets you define your team's content creation and review process. This enables users to maintain a systematic approach to reviewing and approving content.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575896/original/60e1a46a-d9cd-4599-86bc-9aa5f24830b4-Screenshot_2023-05-03_at_1.01.36_PM.png" width="100"/><h1>Understanding with an example</h1>Let's understand this using the below diagram:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575897/original/554f560d-1158-460c-8e37-6bffd050b860-Screenshot_2023-04-04_at_12.44.05_PM.png" width="100"/>The core part of creating a workflow is defining the stages of content creation. Once you have added these stages and enabled the workflow, the stages will be visible on every entry page of the corresponding content types of the stack. Workflows let content managers know the current content stage and allow them to control the stages of an entry.We first need to understand a simple use case or scenario to create the stages.The Scenario:We need to create, review, and publish Blog posts/articles to ensure that the whole process happens smoothly without any intervention from users.To accomplish this, we can create custom roles like:<ul><li>Content Writer - Will only be able to create and update the entry of Blog posts/articles.</li><li>Content Reviewer - Will only review the content.</li><li>Content Publisher - Will only publish the content.</li></ul>Based on these roles, the order of steps in the workflow should be as follows:<ul><li>Step 1 - The 'Content Writer' creates a draft of the content(creates entry). The 'Content Writer' then assigns it to the 'Content Reviewer' for review.</li><li>Step 2 - If the 'Content Reviewer' approves of the quality, they should be able to assign it to the 'Content Publisher' for publishing.</li><li>Step 3 - The 'Content Publisher' publishes the content.</li></ul>If the content is unsatisfactory, the 'Content Reviewer' should be able to assign it back to the 'Content Writer' for changes. The 'Content Writer' will make the required changes and again assign it to the 'Content Reviewer' for approval.The Stages:Based on the above steps, we can define the stages for the workflow in Contentstack as follows:<ul><li>Draft Stage - This is the stage where Step 1 will be executed. The 'Content Writer' can then update the stage to 'Review.'</li><li>Review Stage - This is the stage where Step 2 will be executed. The 'Content Reviewer' can then update the stage to 'Publish.'</li><li>Publish Stage - This is the stage where Step 3 will be executed.</li></ul>The number of stages and the users/user roles may vary depending on the use case. For more control, you can also configure options to restrict user roles from switching between stages.While changing the stages, the respective users/user roles can do the following activities:<ul><li>Switch to any of the available roles.</li><li>Set the Due date for the task(the task the user/user role must perform at the particular stage.&nbsp;Example:&nbsp;Review the Content).</li><li>Assign the task to the users/user roles.</li><li>Notify via email(When enabled, the information about the task is sent via email to the assigned users/user roles)</li><li>Comments(To add any specific comments for the assigned users/user roles)</li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/575898/original/bc6ebe14-a6f6-4713-9b25-cdf30cdc9730-Screenshot_2023-05-03_at_1.05.24_PM.png" width="100"/>Additionally, workflow <a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/about-workflow-tasks/">tasks</a> l allow you to track pending tasks assigned to users. We will review this in the next episode.Potential Use Case:<ul><li>In a typical media company's content creation and publishing process where we need all entries should go through multiple teams like Draft, Translation, SEO, and Review stages to add all necessary checks to verify before it gets published to production.</li></ul>Quick Tips:<ul><li>You can configure 10 workflows per Stack by default.</li><li>While a minimum of 2 stages are required per workflow, the maximum number of stages a workflow can have is 20.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/about-workflows/">About Workflows</a></li><li><div><a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/about-workflow-stages/">Workflow Stages</a></div></li></ul>

Workflows

Tasks or The Workflow Tasks page is a collection of all your pending tasks. Whenever someone assigns you to work on a workflow stage on an entry or if someone sends you an entry for publishing or unpublishing approval, it is added to your Tasks page. Each stack has a separate Tasks section.This enables you to get an overview of the approval requests specific to the content of your stack.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575899/original/66a4e09d-f08b-495c-b9f8-11cc0c239abd-Screenshot_2023-05-03_at_1.10.03_PM.png" width="100"/><h1>Video: Workflows &amp; Tasks in Contentstack</h1>The following video describes how workflow tasks are assigned and how to access them in Contentstack.<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/6B4sZrUM-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="14 - Workflows And Tasks" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Understanding with an example</h1><ul><li>When The ‘Content Writer’ creates a draft of the content(creates an entry) and assigns it to the ‘Content Reviewer’ for review, the ‘Content Reviewer’ gets notified about this task in the left sidebar option under the &nbsp;‘Tasks’ icon.</li></ul>Key points to remember:<ul><li>Stack owners and administrators can view all the tasks assigned to different users.</li><li>Content managers and other custom roles with limited privileges cannot view the entire task list.</li><li>They can only view their tasks list. The docs link can include steps for getting to the Tasks section.</li></ul>Potential Use Case:<ul><li>If someone has assigned you to work on a workflow stage of an entry, this task will remain in your Tasks section until you work on the stage and assign it to some other user. This task section helps users to keep track of all assigned tasks with due dates and filters.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/about-workflow-tasks/">About Workflow Tasks</a></li></ul>

Tasks

Publish Rules are conditions that you define for your content publishing. They allow you to govern whether entries can be published with or without someone’s approval, or only when the content is at a particular stage.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575900/original/3e94f0fd-9666-4a26-81fa-e694b99fe25b-Screenshot_2023-05-03_at_1.11.57_PM.png" width="100"/><h1>Exercise Video</h1>Follow along with the video to practice governance, workflows, and permissions.<iframe src="https://www.youtube.com/embed/KXLMEKLPWrQ" allowfullscreen="" frameborder="0"></iframe><h1>Understanding with an example</h1><ul><li>You can define a publishing rule in which every entry first needs to be approved by a particular user, such as John Smith. Unless John Smith approves it, the entry cannot be published. Alternatively, if you define that the Stage should be Complete to be published, the entry will not be published unless the Complete Stage is reached.</li></ul>Only the stack owner, the administrator, or the developer can define the Publish Rules.Publish Rules are made up of two parts:<ul><li>Parameters - &nbsp;For every publish rule, you need to define the following parameters:</li></ul><ol><li>Environment - The environment for which the publish rule will be applicable.</li><li>Content type - The content type to which the publish rule will be applied.</li><li>Action - Whether the publishing rule is for publish or unpublish (or both) action.</li><li>Language - The language for which the rule is applicable.</li></ol>Once you define the parameters, define a condition.<ul><li>Conditions - You can use either or both of the following conditions for your publishing rule.</li></ul><ol><li>Approver - Use this condition if you want to add an approver to all the entries that are being published or unpublished. Add the user(s)/role(s) who should be authorized to approve the publishing or unpublishing of an entry.
 Example:&nbsp;If you assign 'John Smith' as the Approver, every entry sent for publishing or unpublishing (and meets the required parameters) will go to John Smith for approval. The entry cannot be published or unpublished unless John approves it. And, if you assign a role, let's say 'Content Approver,' as the Approver, every entry sent for publishing or unpublishing and meets the required parameters will go to every user assigned this role for approval. The entry cannot be published or unpublished unless any user assigned the 'Content Approver' role approves it.</li><li>Stage - Use this condition to allow the publishing or unpublishing of an entry only if it has reached a particular workflow stage. When this condition is defined, an entry cannot be published or unpublished unless it comes to the defined Stage while creating content.
 Example:&nbsp;If you have selected 'Complete' here, an entry (that matches the parameters defined above) cannot be published unless it reaches the Complete Stage.</li></ol>Key points to remember:<ul><li>Setting up publish rules is optional.</li><li>You must choose at least one condition (Approver(s) or Stage) for a publishing rule. You can select both if required, but at least one is mandatory.</li><li>A publishing rule with Approver (s) as the condition can work independently of workflows. This means you can add one or more publish rules (with Approver (s) under conditions) even if you have not added any workflows for your stack.</li></ul>However, you will need at least one workflow to use the Stage condition for your publishing rule. Once a rule is in place, whenever a content manager attempts to publish or unpublish an entry on the specified environment, Contentstack will either send the entry for approval (if approvers are added as a condition) or check if the entry has reached the specified Stage (if the Stage is added as a condition). It will then return the response accordingly.Potential Use Case:<ul><li>Publish Rules are helpful to set up specific rules for any entry to be published in a particular environment or language with appropriate approvals.</li><li>You can setup a Publish Rule that no entry is allowed to be published on production till it does not reach an approved stage in the workflow.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/about-publish-rules/">About Publish Rules</a></li><li><a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/about-publish-rule-components/">About Publish Rule Components</a></li></ul>

Publish Rules

Contentstack provides features to comment on the entry fields and start discussions.The ‘Comments’ feature allows you to add comments to fields in the entry editor and collaborate with other Contentstack users across the content creation and review processes. You can add a comment or mention other users using the “@” character to start a discussion.The ‘Discussion’ feature is a conversation you can have with other users of Contentstack over the content of a particular field.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/575902/original/943cc14b-2b08-45a1-9c25-1415dfe8f831-Screenshot_2023-05-03_at_1.17.53_PM.png" width="100"/> <img src="https://learnupon.s3.eu-west-1.amazonaws.com/575903/original/7e484ce3-8e37-44f9-8a5b-5fe1adea4a7c-Screenshot_2023-05-03_at_1.18.03_PM.png" width="100"/> <img src="https://learnupon.s3.eu-west-1.amazonaws.com/575904/original/8e5960c5-ff87-452b-bb48-e679d1d7cbb4-Screenshot_2023-05-03_at_1.18.23_PM.png" width="100"/><h1>Understanding with an example</h1>You start a discussion when you add your first comment to a field in an entry. A discussion can consist of multiple comments. Each localized version of an entry can have multiple discussions running simultaneously. However, you cannot have discussions for unlocalized or older entry versions. You can view all the discussions that have taken place over the fields of an entry, whether active or resolved, under the Discussions section on the right sidebar.To manage the discussions, you can perform the following actions:<ul><li>Resolve a Discussion - When a discussion has served its purpose, you can resolve it, which marks it as done.</li><li>Reopen a Discussion - You can always reopen a resolved or deleted discussion from the Discussions tab in the right sidebar if you would like to continue the discussion.</li><li>Relink a Discussion - Some discussions are unlinked from their fields due to recent changes to the content type or the entry. This usually happens under the following scenarios:</li></ul><ol><li>Mark fields as multiple and vice versa - Fields such as “Group,” “Modular Blocks,” or “Global” are constituted by grouping various fields. You can create discussions for each of their subfields. However, when you mark the parent field as “Multiple,” the discussion fails to recognize which subfield it was linked to. The same occurs when you revert a parent field set as “Multiple” to “Single.”</li><li>Metadata not provided via API(For Developers) - You must pass the _metadata parameter in the API request to identify each instance of a field marked as “Multiple.” When you do not pass the _metadata parameter, the discussion fails to recognize the field instance it was linked to.

 When a discussion is unlinked from a field, it moves to the ‘Active’ section in the right sidebar. The discussion continues to appear in the Unlinked state.</li></ol><ul><li>View Discussions Timeline - Under the Timeline section, you can view all the discussions that have taken place over the fields of an entry, whether active or resolved.</li></ul>Apart from this, Contentstack also provides the ‘Comments’ feature for the JSON RTE. It allows you to add comments within the JSON Rich Text Editor. This feature helps you to collaborate with other Contentstack users across the content creation and review processes efficiently. You can tag/mention other users or roles using the “@” character within your comments. You can edit, resolve, view, and delete comments like that in other entry fields.Potential Use Case:<ul><li>Comments and Discussion is a powerful feature for editors to collaborate with Entry fields and, during the review process, to share review pointers for specific field content and tag User or User Roles so that they get notified via emails and easy navigation to commented Entry field.</li></ul>Quick Tips:<ul><li>While each field allows only one active discussion, but the JSON Rich Text Editor allows multiple active discussions.</li><li>One active discussion can be associated with each selected content block, text, and image within the JSON RTE.</li><li>The maximum number of active discussions allowed per entry, per locale, is 100 and 1000 comments per discussion.</li><li>The maximum message length allowed for each comment is 500 characters and 20 users/roles in a single comment..</li><li>While&nbsp;discussions or comments do not get export while exporting the entries; we&nbsp;cannot view comments for unlocalized or older entry versions.</li><li>You can only add comments to the subfields of ‘Group’ and ‘Global Fields,’ not the parent field as a whole. Similarly, you can only add comments to the fields inside each block of a “Modular Blocks” field, not to the parent field as a whole.</li></ul><h1>Further Reading</h1><ul><li><a href="https://www.contentstack.com/docs/content-managers/author-content/about-entry-comments/">About Entry Comments</a></li><li><a href="https://www.contentstack.com/docs/content-managers/author-content/about-discussions/">About Discussions</a></li></ul>

Comments and Discussions

Thank you for completing the End User Training course and taking your first step to be a Composable Hero.Through this course, you have learned the fundamentals of working with Contentstack. You should now be able to effectively navigate the Contentstack UI, manage and create content, comprehend how to publish, understand how to utilize permissions and workflows, make use&nbsp;of the advanced search, and have a foundational grasp of some&nbsp;additional features. Before you leave, please ensure to fill out the end-of-course survey in the next module. Your feedback is crucial to improving our learning experience for our users.

EUT Summary

Welcome, brave and ambitious learners, to the End User Training course! You have taken the first step towards unleashing your inner Composable Hero and becoming a master of the Contentstack platform.With the power of MACH, you will learn how to develop and manage content&nbsp;that is not bound by the constraints of traditional systems. Instead, you will be able to create dynamic, headless websites that offer exceptional flexibility and versatility. By mastering the fundamentals, you will be equipped with the tools to rescue businesses from outdated and cumbersome systems and guide them toward a brighter future of agility and innovation.&nbsp;First, you must&nbsp;embark on a crucial mission to help the Composable Heroes team spread the powerful message of MACH to people across the globe. Your challenge is to learn and&nbsp;harness the powers&nbsp;within Contentstack&nbsp;so that you can transform&nbsp;the way content is managed and lead your team&nbsp;to success. Are you ready to accept this challenge and join the ranks of the Composable Heroes? Let the journey begin!You can also install a training instance by visiting our Legacy Academy. Click the&nbsp;<a href="https://www.contentstack.com/academy-old">Create Training Instance</a>&nbsp;button on the home page.

Opengraph_B.png

Contentstack End User Training (EUT)

enduser.svg

Discord: <a href="https://discord.com/invite/NyWJ68gdDw">https://discord.com/invite/NyWJ68gdDw</a>

Personalize w/Code

Implementing Personalize with Code

personalize-with-code.png

Using Personalize with Code

About Personalize

Creating a Personalize Project and Experiences

Working with Attributes

Creating Audiences

Creating Events for A/B Tests

Adding Audiences to Experiences

Working with Entry Variants

A/B Testing and Audience Impersonation

In the&nbsp;Personalize Foundations&nbsp;course, you will explore the essentials of delivering tailored content to your audience through Contentstack's personalization features. The course covers the challenges of personalization, such as scalability and complexity, and presents a solution that balances simplicity and flexibility. You'll learn how to set up projects, configure segmented experiences, run A/B tests, and leverage attributes and audiences to deliver the right message at the right time. With practical guidance on creating dynamic user experiences, this course aims to improve engagement, conversions, and customer loyalty through effective personalization.

Learn the fundamentals of Contenstack Personalize

Personalize Foundations

personalize-foundations.png

Understanding Releases

Understanding Releases in Contentstack is critical when it comes to scheduling content publishing.

releases.jpg

<h2>A Foundation for Organized and Efficient Content Management</h2>In this module, we begin by defining&nbsp;<a href="https://www.contentstack.com/docs/developers/content-modeling">content modeling</a>&nbsp;and its&nbsp;significant benefits. Next, we will address the pitfalls of improper modeling and guide you through the necessary steps to ensure a sound content model to&nbsp;avoid&nbsp;common mistakes. Additionally, we will provide an overview of the core components involved in content creation;&nbsp;content types, assets, and entries.&nbsp; We close with a brief example of how to analyze your site or&nbsp;wireframe for effective modeling. By understanding the key concepts, following best practices, and implementing a well-structured content model, you can optimize your content management process and deliver a seamless user experience.<h2>What Is Content Modeling?</h2>Content modeling means defining the structure and organization of your content at&nbsp;a granular level.&nbsp;It involves identifying content types, their fields, and their relationships to create an optimized and reusable framework for managing and presenting content.&nbsp;If you have experience in database design, content modeling bears similarities. The goal of content modeling is to construct content types and structures that facilitate reuse, accommodate multiple channels, and are user-friendly for content contributors/editors. In <a href="https://www.contentstack.com/docs">Contentstack</a>, content modeling begins during the design stage and should be the first step in a successful project. Errors in content modeling can impact the structure of your web/app page. It is important to consult with your content team to validate the content model, review fields, and create entries using established content types. Some metadata fields may not be visible on a page, so the content team should help define them. Each section/component of your website or app should have a suitable content model that aligns with its actual content. <h2>Unlocking Success: The Vital Importance of Content Modeling for Structured, Reusable, and Efficient Content Management</h2> Content modeling is a vital aspect of successful content management. By structuring content, enabling reusability, and fostering efficient creation, it empowers content creators while enhancing user experiences. Its benefits include organized content, consistent presentation, streamlined workflows, and adaptability to future changes. Additionally, content modeling ensures seamless multichannel delivery, collaborative management, and effective SEO practices. Embracing content modeling sets a strong foundation for content governance and control, ensuring data integrity. Ultimately, content modeling is a strategic investment that propels digital content delivery to greater heights. Some of the key benefits include: <ul><li>Structured Content Organization:&nbsp;Content modeling helps organize content into structured and well-defined content types. Each content type represents a specific type of content with its own set of fields, ensuring consistency and easy categorization of content.</li><li>Reusability and Consistency:&nbsp;By defining content types and fields, content can be reused across multiple entries and pages. This reusability ensures consistent presentation and branding throughout the website or application.</li><li>Efficient Content Creation:&nbsp;Content modeling allows content editors to create content using predefined templates or blueprints. This speeds up content creation by providing a clear framework for entering content without the need to design the layout from scratch each time.</li><li>Flexibility and Scalability:&nbsp;Content modeling enables flexibility in managing different types of content, including text, images, videos, and other media. As the website or application grows, content modeling provides scalability to adapt and expand content types to meet changing needs.</li><li>Multichannel Content Delivery:&nbsp;With well-structured content, it becomes easier to deliver content to various channels and platforms, such as websites, mobile apps, voice assistants, or IoT devices. Content modeling helps separate content from presentation, making it adaptable to different channels.</li><li>Collaborative Content Management:&nbsp;Content modeling allows different teams or content contributors to work independently on their assigned content types. This division of content responsibilities facilitates collaborative content management and improves overall efficiency.</li><li>Easy Updates and Maintenance:&nbsp;When changes need to be made to the content, content modeling enables updates to be applied systematically across all relevant entries, reducing the chances of inconsistencies and errors.</li><li>SEO and Searchability:&nbsp;Well-structured content is more search engine-friendly, leading to improved SEO performance and better discoverability of content on the web.</li><li>Content Governance and Control:&nbsp;Content modeling allows content administrators to define content structures, fields, and access controls. This ensures proper content governance and maintains data integrity.</li><li>Future-Proofing:&nbsp;By modeling content in a structured manner, content remains adaptable to future changes and advancements in technology without requiring significant overhauls to the content management system.</li></ul><h2>The Perils of Improper Content Modeling: Avoiding Inconsistencies and Maximizing Efficiency</h2> Conversely, not modeling content properly can lead to several pitfalls and challenges in content management. Some of the key pitfalls include: <ul><li>Inconsistent Content:&nbsp;Without proper content modeling, there is a higher risk of inconsistent content presentation across the website or application. Inconsistent formatting, layout, and styling can create a disjointed user experience and negatively impact the brand's image.</li><li>Content Duplication:&nbsp;In the absence of structured content types, content creators may duplicate content manually across various pages or sections. This redundancy can lead to difficulties in managing updates, as changes need to be applied separately to each duplicated instance.</li><li>Data Integrity Issues:&nbsp;Improper content modeling may result in missing or incomplete data, leading to data integrity issues. This can adversely affect the accuracy and reliability of the information presented to users.</li><li>Difficult Content Updates:&nbsp;Without a well-defined content model, updating content becomes challenging. Content editors may struggle to find the right fields and sections to modify, leading to errors and inconsistencies in content updates.</li><li>Inefficient Workflow:&nbsp;Lack of content modeling can lead to inefficient content creation and approval workflows. Content contributors may face difficulties in understanding the content structure, resulting in delays and miscommunications.</li><li>Limited Reusability:&nbsp;Without structured content types, content reuse becomes limited. This means content creators may need to recreate similar content from scratch, wasting valuable time and effort.</li><li>Poor SEO Performance:&nbsp;Unstructured content can negatively impact search engine optimization (SEO) efforts. Search engines prefer well-organized content, and without proper modeling, search engines may struggle to interpret and rank the content correctly.</li><li>Scaling Challenges:&nbsp;As the website or application grows, managing unstructured content becomes more complex and difficult to scale. Scaling without proper content modeling can lead to an inconsistent user experience and management challenges.</li><li>Difficulty in Multichannel Delivery:&nbsp;Unstructured content may not be easily adaptable to different platforms and channels. This can hamper multichannel content delivery and diminish the brand's ability to reach a broader audience.</li><li>Limited Content Insights:&nbsp;Properly modeled content allows for better content analytics and insights. Without a structured content model, tracking and analyzing content performance may become limited or challenging.</li></ul> In summary, not modeling content properly can result in a host of issues, including inconsistent content, data integrity problems, inefficiencies in content workflows, and difficulties in scaling and managing content. To avoid these pitfalls, investing in content modeling is essential for a seamless and effective content management process.<h2>Is Your Content Model Sound? Steps for Effective Content Management</h2> Ensuring a sound content model is crucial for effective content management. Keep in mind that there is no single right way to build a model, but there are general best practices you can follow. Here are some steps to ensure your content model is well-structured and meets your requirements: <ul><li>Define Content Objectives:&nbsp;Clearly define the objectives of your content and understand the types of content you want to create and manage. Consider the different elements, data types, and relationships that need to be represented in your content.</li><li>Analyze Content Types:&nbsp;Identify the various types of content you will be working with (e.g., articles, products, events) and break them down into individual content types. Determine the fields and data structures needed for each content type.</li><li>Organize Content Fields:&nbsp;Group related fields together within each content type to create a cohesive and organized content model. This helps content creators understand how different pieces of information relate to each other.</li><li>Consider Content Relationships:&nbsp;Determine the relationships between different content types. For example, a blog post may be associated with an author, category, and tags. Use reference fields or modular blocks to establish these relationships.</li><li>Anticipate Future Needs:&nbsp;Design your content model to be flexible and scalable, accommodating future changes and additions. Consider potential content types or fields that may be required as your website or application grows.</li><li>Seek Feedback and Input:&nbsp;Involve content creators, editors, and stakeholders in the content modeling process. Gather feedback and input from the team to ensure the content model aligns with their needs and workflow.</li><li>Evaluate Content Solutions:&nbsp;Deciding between building or integrating an application is crucial in content modeling. While common third-party solutions like DAM or e-commerce vendors offer standardized features, bespoke functionality ensures tailored efficiency and adaptability, impacting content management's future scalability.</li><li>Test Content Creation and Management:&nbsp;Create test entries and content to ensure that the content model functions as expected. Validate that the content can be easily created, edited, and managed within the defined content types.</li><li>Address Performance and SEO:&nbsp;Consider how your content model may impact website performance and search engine optimization. Optimize your content model to ensure fast loading times and SEO-friendly content structure.</li><li>Document Your Content Model:&nbsp;Create comprehensive documentation for your content model, including content type definitions, field descriptions, and content relationships. This documentation will serve as a reference for content creators and developers.</li><li>Iterate and Refine:&nbsp;Content modeling is an iterative process. Continuously gather feedback, monitor content performance, and make adjustments to your content model as needed to improve its effectiveness.</li></ul> By following these steps and regularly reviewing your content model, you can ensure that your content is well-structured, easily manageable, and aligned with your content objectives and business goals. A sound content model sets the foundation for successful content management and helps deliver a seamless and consistent user experience.<h2>Module Summary:&nbsp;&nbsp;The Essential Importance of Content Modeling</h2> Content modeling involves defining the structure and organization of content, facilitating efficient content management and presentation. It empowers content creators, enhances user experiences, and enables multichannel delivery. Proper content modeling offers benefits such as organized content, consistent presentation, streamlined workflows, and adaptability to future changes.Improper content modeling can lead to pitfalls like inconsistent content, duplication, data integrity issues, and scalability challenges. Effective content management requires defining objectives, analyzing content types, organizing fields, considering relationships, anticipating needs, seeking feedback, testing, addressing performance and SEO, and documenting the model.Contentstack's foundational components are Content Types, Entries, and Assets, which structure content and facilitate its management and delivery. Content modeling is a strategic investment that ensures successful content governance and propels digital content delivery across platforms. Learn more:<ul><li><a href="https://www.contentstack.com/docs/developers/content-modeling/about-content-modeling">Content Modeling</a></li><li><a href="https://www.contentstack.com/docs/developers/content-modeling/content-modeling-best-practices">Content Modeling Best Practices</a></li></ul>

Understanding Content Modeling

Core Content Structures

Publishing Environments

Boolean, Date, File, and Number Fields

Reference Fields

Select Fields

In this lesson, we explore the advantages and scenarios of using Contentstack's <a href="https://www.contentstack.com/docs/developers/create-content-types/rich-text-editor">HTML RTE (Rich Text Editor)</a>. The HTML RTE empowers content creators with enhanced formatting options and flexibility to embed multimedia elements, creating engaging content. Its customization capabilities allow tailored content creation, while seamless code integration enables dynamic features. We also examine common pitfalls, including formatting discrepancies and security risks. To overcome challenges, we present best practices, including user training, content governance, accessibility compliance, and performance optimization. By leveraging the HTML RTE effectively, content creators and developers can craft compelling and consistent content experiences for diverse digital platforms. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/645026/original/2c547a65-816e-42ce-8fc7-d8b81b3d15d5-html_Medium.png" width="100"/><h2>Exploring the Capabilities of Contentstack's HTML RTE</h2> From enhanced formatting options and seamless code integration to accessibility and SEO benefits, we will discover how this powerful tool elevates content creation for responsive and user-engaging experiences across various platforms. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/645024/original/270f31cf-4307-41db-8fdc-edadfaa2b732-Screenshot_2023-08-17_at_4.10.17_PM.png" width="100"/>Contentstack's HTML RTE&nbsp;offers a range of advantages for content creators and developers:<ul><li>Enhanced Formatting: The HTML RTE enables users to apply rich formatting options like bold, italics, headings, lists, and more, enhancing content presentation.</li><li>Flexibility: With HTML, users can effortlessly embed multimedia elements, such as images, videos, and interactive components, elevating user engagement.</li><li>Customization: The HTML RTE allows for advanced customization, empowering users to create bespoke content tailored to their specific requirements.</li><li>Seamless Code Integration: Developers can easily integrate custom code snippets and scripts to add interactive elements or dynamic features to the content.</li><li>Accessibility: HTML content is generally more accessible to assistive technologies, ensuring a better experience for users with disabilities.</li><li>Responsive Design: The HTML RTE facilitates the creation of responsive content, ensuring optimal viewing across different devices and screen sizes.</li><li>SEO-Friendly: Properly structured HTML content can enhance search engine visibility, contributing to better search rankings.</li><li>Cross-Browser Compatibility: HTML content is widely supported across various web browsers, ensuring consistent performance and display.</li><li>Version Control: Contentstack's HTML RTE often includes version control features, enabling users to track changes and revert to previous versions as needed.</li><li>Future-Proofing: HTML is a standard language for the web, making it a reliable and future-proof choice for content creation.</li></ul>In conclusion, Contentstack's HTML RTE empowers users with the flexibility and functionality needed to create engaging and dynamic content for diverse digital platforms.*Note: Always be cautious when allowing custom HTML input to avoid potential security risks and ensure content consistency.<h2>Creative Applications of Contentstack's HTML RTE</h2> Let's explore the diverse applications of Contentstack's HTML RTE (Rich Text Editor). From content creation and email campaigns to landing pages, user documentation, and interactive content, we discover how this versatile tool is utilized across various scenarios for crafting visually appealing and engaging content. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/645025/original/6f175aed-4080-4aca-a2b8-6b2358f0e2f8-html-rte.png" width="100"/> Some common scenarios where Contentstack's HTML RTE&nbsp; are commonly used: <ul><li>Content Creation: Authors and content creators use the HTML RTE to draft and format blog posts, articles, product descriptions, and other web content.</li><li>Email Campaigns: Marketing teams leverage the HTML RTE to design and customize email newsletters, ensuring visually appealing and engaging content.</li><li>Landing Pages: Web developers and marketers use the HTML RTE to create captivating landing pages with rich media and interactive elements.</li><li>User Documentation: Technical writers utilize the HTML RTE to create and format user guides, manuals, and documentation with images, code snippets, and more.</li><li>Knowledge Base Articles: Customer support teams use the HTML RTE to craft comprehensive and visually enhanced knowledge base articles for self-help resources.</li><li>Social Media Posts: Content marketers format and style social media posts using the HTML RTE to make them stand out and capture users' attention.</li><li>Press Releases: PR professionals use the HTML RTE to format press releases with headings, bullet points, and multimedia elements.</li><li>Web Page Content: Web developers and content creators use the HTML RTE to manage and update the content of various web pages on their websites.</li><li>Announcements and Notices: Organizations use the HTML RTE to create visually appealing announcements, event notices, and news updates for their audiences.</li><li>Interactive Content: Developers integrate custom JavaScript or other scripts using the HTML RTE to create interactive elements such as quizzes, surveys, or calculators.</li></ul>These are just a few examples of how Contentstack's HTML RTE and similar Rich Text Editors are utilized in various scenarios to create and manage content across different digital platforms.<h2>Common Challenges&nbsp;of the HTML RTE&nbsp;</h2> While using HTML RTE (Rich Text Editor) offers numerous benefits, it can also present some challenges and issues that content creators and developers need to be aware of. Observe these typical setbacks faced when using the HTML RTE: <ul><li>Content Formatting Discrepancies: Different web browsers and email clients may interpret HTML formatting differently, leading to inconsistencies in how the content appears to end-users.</li><li>Security Risks: Allowing users to input custom HTML can create security vulnerabilities, such as cross-site scripting (XSS) attacks, if not properly sanitized and validated.</li><li>Complexity for Non-Technical Users: The flexibility of the HTML RTE can be overwhelming for non-technical content creators, leading to difficulties in using and formatting content correctly.</li><li>Content Fragility: Directly embedding custom HTML code can make the content more fragile, as small syntax errors can cause content failures or improper rendering.</li><li>Accessibility Concerns: Improperly structured HTML content can hinder accessibility for users with disabilities, leading to compliance issues with accessibility standards.</li><li>Performance Impact: Excessive use of complex HTML elements and scripts can negatively impact page load times and overall website performance.</li><li>Version Control Challenges: Versioning HTML content can be more complex, especially when updating specific components within the content.</li><li>Cross-Browser Compatibility: Ensuring consistent rendering and functionality across different web browsers can be challenging due to varying browser support for HTML features.</li><li>Data Integrity: If users have the ability to input raw HTML, there is a risk of improperly formatted code that may affect the data integrity of the content.</li><li>Content Governance: Allowing extensive customization with HTML RTE might lead to inconsistencies and deviations from the brand's style guidelines.</li><li>Limited WYSIWYG Editing: HTML RTE might lack certain visual editing features present in traditional WYSIWYG editors, making it challenging for users to visualize content changes in real-time.</li></ul> In this lesson, we explored challenges of using the HTML RTE (Rich Text Editor), including content formatting discrepancies, security risks, complexity for non-technical users, accessibility concerns, performance impact, and issues with version control and cross-browser compatibility.<h2>Effective Use of the HTML RTE Field</h2> Essential strategies for harnessing the full potential of HTML RTE&nbsp; include user training and input validation to accessibility compliance and performance optimization. Below we will&nbsp;discover how to create consistent, secure, and engaging content while mitigating common challenges. Here are some strategies and best practices to overcome such challenges.: <ul><li>User Training and Support: Provide comprehensive training and documentation for non-technical users on how to use the HTML RTE effectively and safely. Offer ongoing support to address any questions or difficulties they may encounter.</li><li>Input Sanitization and Validation: Implement strict input sanitization and validation to prevent security vulnerabilities like XSS attacks. Use a robust HTML sanitizer to ensure only safe and allowed tags and attributes are used.</li><li>Content Governance and Style Guidelines: Establish clear content governance policies and style guidelines to maintain consistency and adherence to the brand's visual identity and formatting standards.</li><li>Use of Templates and Components: Utilize predefined templates and reusable components to streamline content creation, ensuring consistent styling and structure across different pages.</li><li>Accessibility Compliance: Follow web accessibility guidelines (e.g., WCAG) to ensure HTML content is accessible to all users, including those with disabilities.</li><li>Content Versioning and Review Process: Implement a version control system and review process to track changes and maintain content integrity while collaborating with multiple stakeholders.</li><li>Performance Optimization: Optimize HTML code and scripts to improve page load times and overall website performance. Minimize unnecessary elements and prioritize performance.</li><li>Browser Testing: Regularly test the HTML content across various web browsers and devices to ensure consistent rendering and functionality.</li><li>Automated Testing: Employ automated testing tools to identify potential issues, such as broken links, missing tags, or performance bottlenecks in the HTML content.</li><li>Limit Customization Options: If appropriate, limit the extent of HTML customization available to content creators, balancing flexibility with the need for consistency and security.</li><li>Debugging and Error Handling: Develop robust error-handling mechanisms to detect and address syntax errors and content failures effectively.</li><li>Collaboration and Communication: Foster open communication and collaboration between content creators, developers, and other stakeholders to address challenges and find optimal solutions together. </li></ul>In summary, organizations should implement proper content governance, security measures, and user training to mitigate issues. Additionally, leveraging templates and predefined styles can help create consistent and secure content. Regular audits and testing across various browsers and devices can also help identify and address potential rendering discrepancies and performance concerns.Walkthrough Lesson: Integrating an HTML RTE Field to the "News Article" Content Type in Contentstack<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/pPkRXW33-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Cm-implementing Html Rte" style="position: absolute;" allowfullscreen=""></iframe></div>Objective: Equip yourself with the knowledge to incorporate the HTML RTE (Rich Text Editor) field into a Contentstack "News Article" content type, thereby enhancing the visual appeal and interactivity of news articles. Step 1: Introduction to HTML RTE<ul><li>Kick off with an overview of the Rich Text Editor (RTE) in Contentstack and its pivotal role in transforming traditional news articles into immersive multimedia experiences.</li></ul>Step 2: Scenario Setup<ul><li>Scenario: Imagine you're the digital editor for "Daily Insights," a news portal. While your articles are informative, they lack visual elements and interactive content, leading to decreased reader engagement. To address this, you decide to revamp the "News Article" content type by integrating rich text capabilities, allowing journalists to embed images, videos, and utilize advanced text formatting.</li></ul>Step 3: Accessing Your "News Article" Content Type<ul><li>Log into your Contentstack account.</li><li>Head over to the "Content Models" section.</li><li>Find and select the "News Article" content type.
 </li></ul>Step 4: Incorporating the HTML RTE Field<ul><li>Tap on the "+ Add Field" button.</li><li>From the dropdown menu, opt for "Rich Text Editor."</li><li>Name the field "Article Content" or something similar.</li><li>Optionally, provide a brief guideline for journalists, such as "Craft the core content of the article, embedding relevant images, videos, and using rich text formatting for better reader engagement."</li></ul>Step 5: Tailoring the HTML RTE<ul><li>Within "Properties," select the formatting tools that align with your portal's style guide.</li><li>Set validation rules if needed, like ensuring certain tags are used or setting a character limit for consistency.
 </li></ul>Step 6: Save and Test<ul><li>Click "Save" to finalize the HTML RTE field's addition to your "News Article" content type.</li><li>Navigate to the "Entries" section and pick "News Article."</li><li>Create a new entry or edit an existing one. You should now spot the "Article Content" field, equipped with the rich text editor toolbar.</li><li>Test its functionality by drafting a sample news piece, embedding multimedia elements, and experimenting with different formatting tools.</li></ul>Step 7: Conclusion<ul><li>By seamlessly integrating the HTML RTE field into your "News Article" content type, you've empowered your journalists to craft compelling, multimedia-rich articles, ensuring that "Daily Insights" offers a modern and engaging reading experience.</li></ul>Note: For comprehensive details and any updates related to the HTML RTE functionalities, it's advisable to refer to the&nbsp;<a href="https://www.contentstack.com/docs/developers/create-content-types/rich-text-editor">documentation</a>.<h2>Module Summary:&nbsp;Optimizing&nbsp;HTML RTE Field Implementation</h2>
 In this comprehensive lesson, we explored the versatility of Contentstack's HTML RTE and its advantages for content creators. We delved into common scenarios where HTML RTE is widely used, from content creation to interactive elements. However, challenges, such as formatting discrepancies and security risks, should not be overlooked. To overcome these hurdles, we presented best practices like user training, input validation, and accessibility compliance. By adhering to content governance and collaborating effectively, content creators can elevate their work, ensuring consistent and engaging experiences for users across digital platforms. Learn more:<ul><li><a href="https://www.contentstack.com/docs/developers/json-rich-text-editor/html-rte-vs-json-rte">HTML RTE vs JSON RTE</a></li></ul><h2>Optional Exercise: Implementing the HTML RTE in 'Product Listing' Content Type&nbsp;
 </h2>Objective: Learn how to integrate the HTML RTE (Rich Text Editor) into the 'Product Listing' content type to enhance content creation and formatting capabilities. Scenario: You're managing an online store's content on Contentstack. To provide detailed descriptions for products, you decide to implement the HTML RTE, allowing for rich text formatting and embedding of multimedia elements.
 Step 1: Accessing the 'Product Listing' Content Type<ul><li>Navigate to your Contentstack dashboard.</li><li>Locate and select the existing 'Product Listing' content type.</li></ul> Step 2: Integrating the HTML RTE to 'Product Listing'<ul><li>Click on "+ Add Field" and select the "Rich Text Editor" field.</li><li>Label it "Product Details".</li><li>In the properties section, enable the "Allow HTML" option to utilize the HTML RTE capabilities.</li><li>Save the changes to the 'Product Listing' content type.
 </li></ul>Step 3: Creating or Editing Entries with HTML RTE<ul><li>Navigate to the 'Entries' section and select 'Product Listing'.</li><li>Click on "+ New Entry" or select an existing entry to edit.</li><li>In the "Product Details" field, you can now utilize the HTML RTE to format text, embed multimedia, and input custom HTML.</li><li>Save and publish the entry.</li></ul> Conclusion: By integrating the HTML RTE into the 'Product Listing' content type, you've empowered content creators with enhanced text formatting and multimedia embedding capabilities. This ensures richer and more engaging content for your online store's audience.

HTML RTE Field

Group Fields

Global Fields

Custom Fields

Modular Blocks

Languages & Localization

The Contentstack Content Models are a blueprint or schema of a content type that defines the structure, fields, and relationships of the content. It is a visual representation of the content type and helps content editors and developers to create and manage content in a structured and organized manner. If you haven't already installed a training instance, you can do so by visiting our Legacy Academy. Click the <a href="https://www.contentstack.com/academy-old">Create Training Instance</a> button on the home page.

This course provides you the necessary information to effectively content model within the Contentstack CMS.

Opengraph_A.png

Content Modeling with Contentstack

content-modeling-cs.png

<h1>Developer Onboarding Course - Introduction</h1> Welcome to our exciting new course on developing web applications with Contentstack! If you're looking to build powerful, scalable, and customizable web applications, then you're in the right place. In this course, we'll guide you through the fundamentals of Contentstack, including content modeling, API and SDK usage, and more. We'll also cover advanced topics such as extending a NextJS app, enabling localization, and optimizing your content delivery. With our easy-to-follow tutorials and hands-on exercises, you'll quickly gain the skills and knowledge needed to build stunning web applications that meet the needs of your clients and users. So, whether you're a seasoned developer or just starting out, join us on this exciting journey and take your web development skills to the next level with Contentstack!The main tasks in the course are:<ol><li>Create a new detail page (new content type, new NextJS Component, new CD API query)</li><li>Create a new gallery landing page (new content type, new NextJS Component, more complicated CD API Queries)</li></ol>We also cover the following:<ul><li>Starter app overview, install, and walk through</li><li>Using CMA to read and import content</li><li>SDKs / APIs overview and introduction</li><li>SDKs / APIs deep dive with patterns / practices&nbsp;</li><li>Roles &amp; Permissions</li><li>Workflow</li><li>Marketplace intro</li><li>Automation hub intro</li></ul><h1>What we will be building</h1><h2>Composable Hero&nbsp;Gallery Page</h2><img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/bltd51a0c5b982c72f8/664c027a1983ea9d6dac29b4/composable-heros.png" alt="composable-heros.png" height="auto"/><h4> Composable Hero Detail Page</h4><img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/bltcba8639d82e39f82/664c02a3785339639e9e3d9f/composable-heros-detail.png" width="auto" alt="composable-heros-detail.png" height="auto" max-width="auto" style="max-width: auto;width: auto;height: auto;"/><h1>Getting Started</h1>1.&nbsp; Create a new Training Instance - Go to&nbsp;<a href="https://www.contentstack.com/academy-old">https://www.contentstack.com/academy-old</a> and select 'Create a Training Instance'. 2.&nbsp; <a href="https://github.com/contentstack/contentstack-academy-playground">Download the course code from Github (https://github.com/contentstack/contentstack-academy-playground)</a> 3.&nbsp; Rename the .env.local.sample file to .env.local and update the configuration properties <img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/bltb3b6b76e3ee547ed/664c033cc9024cafa4ad58b4/rename-sample.png" alt="rename-sample.png" height="auto"/> 4. Build the project with 'npm i' 5.&nbsp; Run the website with 'npm run dev'

What We'll Build

Getting Started

<h1>Architecture</h1><h2>Big Picture Architecture Diagram</h2><h3>Backend</h3>The Backend of Contentstack is the CMS with the ability to create and publish content.&nbsp; The focus here is on editor ease-of-use by providing a simple, powerful and flexible UI for content creation and management.&nbsp; In addition to the out of the box functionality, we also provide an ability to extend the interface by creating UI Extensions using our App SDK and connect to 3rd-party applications such as DAM providers, Analytics, E-Commerce platforms and more.<h3>Frontend</h3>The focus on the frontend is high-performance for your website and web application. APIs and SDKs are provided to the developer for using in their applications to perform read-only queries to the content.&nbsp; The Content Delivery APIs use an internal CDN to cache all queries to the platform which results in higher performance for all your web applications.&nbsp; This is also where we find the Images API for delivering image assets.<img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/blt40df19fbdfa691c4/664c7d55a671fa7891f218bf/Architecture.png" alt="Architecture.png" height="auto"/><h2>Environments</h2><ul><li>One Stack can publish to multiple Environments. &nbsp;Think of Environments as “publish destinations”.</li><li>Each Environment has one Delivery Token, otherwise known as an Access Token. &nbsp;That token is unique per Environment.</li><li>Each Stack has an API key. &nbsp;There is only 1 API key per Stack and it is unique.</li><li>Most API calls will require both an API token and a Delivery / Access Token.</li></ul><img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/blta9f0e57d8a3c5a6e/664c7d9f79abee8ebd3d1534/environment.png" alt="environment.png" height="auto"/>Multi-Stack Architecture Diagram<img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/bltd1dd48a1fcbec491/664c7de28a66292552b1397b/multi-stack.png" alt="multi-stack.png" height="auto"/>

Big Picture Architecture

Architecture Walkthrough

Environments Walkthrough

In this module, we'll dive into the world of Contentstack's powerful APIs that can help you build your digital experiences faster, easier, and better. Our APIs are designed to help developers access content and make updates programatically.First, we'll start with Contentstack's Content Delivery API. This API allows developers to retrieve content from Contentstack's headless CMS and deliver it to any digital platform or device. You'll learn how to use our API to retrieve content in a structured and organized manner, so you can easily integrate it into your website, app, or any other digital platform.Next, we'll explore Contentstack's Content Management API. This API enables developers to create, update, and manage content in Contentstack's headless CMS programmatically. You'll learn how to leverage our API to automate content creation, content management workflows, and enable seamless collaboration between developers and content editors, and increase the efficiency of your content creation processes.Finally, we'll dive into Contentstack's Images API. This API allows you to transform and optimize images on-the-fly, so you can deliver the best possible visual experience to your users. You'll learn how to use our API to resize, compress, and optimize images.By the end of this module, you'll have a deep understanding of Contentstack's powerful APIs and how to leverage them to build faster, better, and more engaging digital experiences. So, let's get started!<h1>Using the Content Delivery API</h1>Contentstack's Content Delivery API is a powerful tool that enables developers to retrieve content from Contentstack's headless CMS and deliver it to any digital platform or device. It allows you to fetch content in a structured and organized manner, which makes it easier to integrate into your website, app, or any other digital platform.The Content Delivery API is built on top of a powerful caching layer, which ensures lightning-fast performance even when you're dealing with large amounts of content. This caching layer also ensures that your content is always up-to-date and in sync with the latest updates made to the CMS.One of the biggest advantages of using Contentstack's Content Delivery API is that it's completely agnostic to the technology stack you're using. Whether you're building your website using a traditional CMS or a modern front-end framework like React or Vue.js, the Content Delivery API can be seamlessly integrated into your workflow.With the Content Delivery API, you can also retrieve content in multiple languages, which is essential for building global websites and apps. The API also allows you to fetch only the content you need, which reduces the amount of data transfer and improves the overall performance of your application.<a href="https://www.contentstack.com/docs/developers/apis/content-delivery-api/">Content Delivery API Documentation</a><img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/bltbeecb6f7ab8cf28a/664d437c785339c0e89e4f8e/API-map.png" alt="API-map.png" height="auto"/>

Using the Content Delivery API

<h3>Using the&nbsp;Content Delivery API documentation </h3><ol><li>Go to the <a href="https://www.contentstack.com/docs/developers/apis/content-delivery-api/#get-all-entries">Get Entries section of the Content Delivery Documentation</a></li><li>Select the Get all Entries link to open the query window on the right</li><li>Update the parameters to use the following:
 - content_type_uid: blog_post
 - environment: preview (or development)
 - locale: en-us
 - api_key: (found in the settings / tokens / content delivery token settings page)
 - access_token:&nbsp;(found in the settings / tokens / content delivery token settings page)

 <a href="https://www.contentstack.com/docs/developers/apis/graphql-content-delivery-api/#postman-collection">If you have questions, see the Postman guide for more details</a></li><li>Execute the request with the 'Try' button</li><li>Congrats!&nbsp; you just queried the Contentstack Content Delivery API!</li></ol>

Using the Content Delivery API documentation

Querying the Content Delivery API with the Documentation Walkthrough

<h3>Using the Postman collection to connect with the Content Delivery API</h3><ol><li><a href="https://www.postman.com/downloads/">Download and install Postman</a></li><li><a href="https://www.contentstack.com/docs/developers/apis/postman-collections">Download the Contentstack Postman Content Delivery collection</a></li><li>To obtain the Content Delivery Token, follow these steps in Contentstack: navigate to the "Settings" page, select "Tokens," then choose "Content Delivery." If you haven't created a Delivery Token yet, <a href="https://www.contentstack.com/docs/developers/create-tokens/create-a-delivery-token/">create a new Delivery Token</a>. <a href="https://www.contentstack.com/docs/developers/create-tokens/#work-with-delivery-tokens">Additional information about tokens, including Delivery Tokens, can be found in our documentation</a>&nbsp;</li><li>Open Postman and select the 'Content Delivery API - Contentstack' collection.&nbsp; Entries, Get all entries</li><li>Edit the Postman variables and update the values for api_key and access_token.&nbsp; The api_key is found on the Delivery Token settings page.&nbsp; The access_token is the Delivery Token.&nbsp; These are used in the Headers of the request.
 Also, add the value of the content_type_uid as 'blog_post', environment as 'preview' and locale as 'en-us'.</li><li>Send the request.&nbsp; Contentstack replies&nbsp;with the JSON of all blog_post entries.</li></ol>

Using the Postman collection to connect with the Content Delivery API

Using Postman to query the Contentstack Content Delivery API Walkthrough

<h2>Getting Started using the JavaScript Content Delivery SDK</h2>To get started with the Content Delivery SDK and NodeJS, the first thing you need to do is to install it. You can do this by running the following command in your project directory:npm install contentstack <h2>Helpful Javascript Resources</h2><a href="https://github.com/contentstack/contentstack-javascript">Javascript SDK on Github</a>&nbsp;<a href="https://www.contentstack.com/docs/developers/sdks/content-delivery-sdk/javascript-browser/reference/">Javascript API Reference</a>
 Include the JS SDK in your projects<pre>https://cdn.jsdelivr.net/npm/contentstack@latest/dist/web/contentstack.min.js </pre>Once you have installed the SDK, you need to initialize it with your API key, delivery token, and environment name. Here's an example of how to do this:<pre>const Contentstack = require('contentstack'); const Stack = Contentstack.Stack({ api_key: 'your_api_key', delivery_token: 'your_delivery_token', environment: 'your_environment' }); </pre>With the SDK initialized, you can start retrieving content from Contentstack's API. The SDK provides several methods for fetching content, depending on your requirements.If you want to retrieve a single entry, you can use the Entry method, as shown in the following example:<pre>Stack.ContentType('your_content_type_uid').Entry('your_entry_uid').fetch() .then(function success(entry) { console.log(entry); }, function error(err) { console.log(err); }); </pre>In this example, your_content_type_uid is the unique identifier of the content type you want to retrieve, and your_entry_uid is the unique identifier of the entry you want to retrieve. The fetch() method retrieves the entry and returns it as a JavaScript object.If you want to retrieve multiple entries, you can use the Query method, as shown in the following example:<pre>const stack = Contentstack.Stack({"api_key":"bltc2242b759e36fcb9","delivery_token":"cs1470a664abc4563bd43a604d","environment":"development"});&nbsp; // use your api_key and delivery_token here from your Stack const query = stack.GetEntry('blog_post').Query(); query.toJSON() &nbsp; .find() &nbsp; .then( &nbsp; (result) =&gt; { &nbsp; &nbsp; console.log(result[0]); &nbsp; }, &nbsp; (error) =&gt; { &nbsp; &nbsp; console.error(error); &nbsp; }, ); </pre>In this example, your_content_type_uid is the unique identifier of the content type you want to retrieve. The find() method retrieves all the entries of the content type and returns them as an array of JavaScript objects.The SDK also provides methods for filtering and sorting entries, as well as retrieving entries with specific fields. You can learn more about these methods in the Contentstack documentation.There are also SDKs for most popular languages such as .Net, Java, PHP, Python, Ruby, iOS, Android, Dart, etc.Documentation links:<ul><li><a href="https://www.contentstack.com/docs/developers/sdks/content-delivery-sdk/javascript-browser/reference/">API Reference</a></li><li><a href="https://github.com/contentstack/contentstack-javascript">JavaScript SDK Github Repo</a></li><li><a href="https://www.contentstack.com/docs/developers/sdks/">All SDKs</a></li><li><a href="https://www.contentstack.com/docs/developers/web-framework/querying/">Query examples</a>
 </li></ul><img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/blt31c71c762d48a421/664d45aa79abeeeb093d23a5/content-sdk.png" alt="content-sdk.png" height="auto"/>

Using the JavaScript Content Delivery SDK

<h2>Using the GraphQL API with Postman</h2> <h3>GraphQL</h3>Contentstack's GraphQL API is a powerful tool for developers who want to integrate Contentstack's content management system (CMS) into their web or mobile applications. It provides a flexible and efficient way to retrieve content from Contentstack's content repository using the GraphQL query language.With Contentstack's GraphQL API, developers can retrieve content from their Contentstack projects using a single API call. The API returns only the data that is requested, which reduces the amount of data transferred and improves performance. The API also supports pagination, filtering, and sorting, which enables developers to retrieve only the content they need and to organize it in a way that best suits their application.Contentstack's GraphQL API supports all of the content types and fields defined in a Contentstack project, including modular blocks and assets. This means that developers can retrieve any type of content from Contentstack, including text, images, videos, and more.In addition, Contentstack's GraphQL API is designed to work seamlessly with popular frontend frameworks and libraries, such as React, Vue.js, and Angular. This allows developers to easily integrate Contentstack's content into their applications and to build dynamic and engaging user experiences.
 <h3>GraphQL API Explorer</h3>Contentstack has a GraphQL API explorer to query Contentstack's Content Delivery API.&nbsp;&nbsp;<img src="https://images.contentstack.io/v3/assets/bltebc53cfaf0dd6403/blt720a9df15d2b3c95/664d46208a0182e22014ca07/graphQL.png" alt="graphQL.png" height="auto"/><ol><li>In the Contentstack UI, navigate to Settings and then GraphQL</li><li>Build your queries</li><li>There is also an <a href="https://www.contentstack.com/docs/developers/graphql-api/use-the-graphql-queries-with-apollo-sdks/use-graphql-queries-with-apollo-client-javascript-sdk/">Apollo Client JavaScript SDK</a>&nbsp;for using the API&nbsp;</li></ol><h2>More GraphQL API Resources</h2><ul><li><a href="https://www.contentstack.com/docs/developers/apis/postman-collections/">GraphQL&nbsp;Postman Collection</a></li><li><a href="https://www.contentstack.com/docs/developers/graphql-api/graphql-sample-apps/">GraphQL Sample Apps</a></li><li><a href="https://www.contentstack.com/docs/developers/graphql-api/use-the-graphql-queries-with-apollo-sdks/use-graphql-queries-with-apollo-client-javascript-sdk/">Using GraphQL with the Apollo Client JavaScript SDK</a></li></ul>

Using the GraphQL API with Postman

<h1>CDN and Caching</h1>A Content Delivery Network (CDN) ensures that a cache of your content is stored at various locations around the globe. Consequently, whenever there is a page request, the content is served from the cache of the nearest CDN server, rather than the origin server ensuring quicker content delivery.<h2>How CDN Cache Works in Contentstack</h2>The CDN is always up-to-date. It ensures that the cache is always fresh through purging old data and caching new data.When any user requests a piece of content, the nearest CDN server checks if it has a cached copy of the requested content. If not, it checks with the shield server. And, if the shield server does not have the cache of the requested content, it fetches the content from the origin server.A shield server is an extra layer of caching that reduces the load on the origin server. It is located near the origin server, and it saves the cache of content that it serves to any CDN server. So, if any other CDN server requests the same data, the shield server would serve the cached content.Contentstack automatically purges content from the internal Contentstack CDN when published.&nbsp;&nbsp;Helpful links:<ul><li><a href="https://www.contentstack.com/docs/developers/cdn-and-caching/contentstack-cdn-cache-management/">How CDN Cache Management works in Contentstack</a></li></ul>

CDN and Caching

<h1>Query Examples with the Content Delivery API</h1><h2>Query by URL</h2><pre>const getContentByURL = async ({ contentType, slug, refUids, locale, filter }) =&gt; { try { const Query = global.Stack .ContentType(contentType) .Query() .language(locale) if (refUids) { let refs = refUids.replace(/ /g, '').split(',') Query.includeReference(refs) } let result = await Query .includeFallback() .where('url', `/${slug}`) .toJSON() .includeEmbeddedItems() .addParam('include_metadata', 'true') .find() if (result &amp;&amp; result.length &gt; 0 &amp;&amp; result[0].length &lt;= 0) { // for trailing slash match result = await Query .includeFallback() .where('url', `/${slug}/`) .toJSON() .includeEmbeddedItems() .addParam('include_metadata', 'true') .find() } (global.env === 'preview' || global.env === 'staging-preview' ||global.env === 'development') ? Contentstack.Utils.addEditableTags(result[0][0], contentType, true, locale) : '' //metadata key required for _metadata in cms entry data if(result.length &gt; 0 &amp;&amp; result[0].length &gt; 0) { result[0][0] = {...result[0][0], metadata: result[0][0]} } if (result) return result[0][0] } catch (error) { throw new Error(error) } }</pre> <h2>Query by UID</h2><pre>const getContentByUID= async ({ contentType, entryUid, refUids, locale }) =&gt; { try { const Query = global.Stack .ContentType(contentType) .Entry(entryUid) .language(locale) .includeFallback() .includeEmbeddedItems() if (refUids) { let refs = refUids.replace(/ /g, '').split(',') Query.includeReference(refs) } let result = await Query.toJSON().fetch() if (result) return result } catch (error) { return error } }</pre> <h2>Example to Get All Entries</h2><pre>const getEntries = async ({ contentType, refUids, locale }) =&gt; { let collectionData try { const Query = global.Stack.ContentType(contentType) .Query() .language(locale) if (refUids) { let refs = refUids.replace(/ /g, '').split(',') Query.includeReference(refs) } let result = await Query .includeFallback() .toJSON() .includeEmbeddedItems() .addParam('include_metadata', 'true') .find() if (result &amp;&amp; result.length &gt; 0 &amp;&amp; result[0].length &lt;= 1) { //for entry type = single (global.env === 'preview' || global.env === 'staging-preview' || global.env === 'development') ? Contentstack.Utils.addEditableTags(result[0][0], contentType, true, locale) : '' //metadata key required for _metadata in cms entry data result[0][0] = {...result[0][0], metadata: result[0][0]} return result[0][0] } //for entry type = multiple (global.env === 'preview' || global.env === 'staging-preview' || global.env === 'development') ? Contentstack.Utils.addEditableTags(result[0][0], contentType, true, locale) : '' if (result) return result } catch (error) { res.status(500).send(`Internal Server Error\n: ${error}`) // throw new Error(error) } }</pre>

Query Examples with the Content Delivery API

<h1>Using the Contentstack Images API</h1>Welcome, developers, to the Contentstack Images API! As you may know, images are an integral part of any digital experience, and we understand the importance of delivering optimized images quickly and efficiently. That's why we've created the Contentstack Images API, a powerful tool that allows you to manipulate, optimize, and deliver images to your web and mobile applications. Whether you're new to the platform or a seasoned developer, this guide will provide you with everything you need to know to get started with the Contentstack Images API. So let's dive in and explore the possibilities of this powerful tool together!Here are three advantages to using the Contentstack Images API:<ol><li>Performance: The Contentstack Images API allows you to deliver optimized images at scale, reducing load times and improving the overall performance of your web and mobile applications.</li><li>lexibility: With the Contentstack Images API, you have the flexibility to resize, and transform images in real-time, giving you the ability to customize images to fit any layout or design.</li></ol><h1>Trying out the Image Delivery API</h1>The quickest way to get started with the Image Delivery API is to try it out with the <a href="https://www.contentstack.com/docs/developers/apis/image-delivery-api/#introduction">online documentation</a>.&nbsp;&nbsp;Resize an image on the flyContentstack's Images API resizes images on the server and provides the resized file in the response.&nbsp; This is highly performant as the resized image is stored in the CDN cache on the Contentstack side.<h2></h2><h2>Exercise:&nbsp; Resize an image with the Contentstack Images API</h2>1. Go to the following URL, <a href="https://www.contentstack.com/docs/developers/apis/image-delivery-api/#resize-images">https://www.contentstack.com/docs/developers/apis/image-delivery-api/#resize-images</a>2.&nbsp;Update the width of the image and see the image size and dimensions being changed <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576471/original/5395739f-6abc-477d-8df5-85c98301bd33-Screen_Shot_2023-05-02_at_2.17.52_PM.png" width="100"/><h2> Exercise: Auto-optimizing images with webp</h2>1.&nbsp;Navigate to the Automate Optimization section of the documentation,&nbsp;<a href="https://www.contentstack.com/docs/developers/apis/image-delivery-api/#enable-auto-optimization">https://www.contentstack.com/docs/developers/apis/image-delivery-api/#enable-auto-optimization</a>2. Leave the default as webp in the query parameters<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576472/original/3a20e031-c973-4b47-864c-c990151c343b-Screen_Shot_2023-05-02_at_2.20.38_PM.png" width="100"/><h2>Using the Images API in your NextJS Applications</h2>Pass the width,&nbsp;height, or auto attributes to the src property in the img tag<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576473/original/fee1998b-24e1-41c8-bcc8-ee70428c203e-Screen_Shot_2023-05-09_at_12.47.19_AM.png" width="100"/><h2>Exercise: Use the Images API to resize the home world image</h2>1.&nbsp; Update the NextJS code to apply a width param of 150px to the home world image.&nbsp; This resizes the image on the server-side and improves the performance of the page load. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576474/original/c62cc787-8b7d-4a61-a92f-b261a984dfbf-Screen_Shot_2023-05-09_at_12.52.49_AM.png" width="100"/>

Using the Images API

<h1>Exercise: Creating the Character Content Type</h1>In this module we will cover the following topics:<ul><li>How to build a Content Type</li><li>Review Field Types</li></ul>Marketing has provided us with requirements to promote our Composable Heroes by creating&nbsp;a section of the site where each hero will have their own detail page and be listed on a gallery page. In the next few exercises we will define the content type for a Composable Hero and&nbsp;build a hero detail page. &nbsp;There’s no time to waste, let’s get started!<h2>Analyze the Page Design</h2>When defining a new Content Type it's important to have the page design available (in photo / HTML format) so we can model the Content Type and define fields for the content elements.&nbsp;&nbsp;Analyze the following pages and think of the properties that a superhero character would need.&nbsp; When analyzing pages we often look for as many representations of the same content as possible, and then we combine all these fields into one Content Type.&nbsp; In this exercise, let's take a look at these two pages and see what fields they contain.&nbsp; We will focus on the main page content and ignore the headers and footer.&nbsp; If you would like to learn more, the Content Modeling course covers the content type fields in more detail.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576419/original/89e9ec57-5120-4ee8-a1d9-360e9b16af2f-Screen_Shot_2023-05-07_at_9.42.30_PM.jpg" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576420/original/76c24c81-3df4-4d82-9ab6-2f7d6e8135b3-Screen_Shot_2023-05-07_at_9.28.44_PM.png" width="100"/><h2>Defining&nbsp;the Character Content Type for the Hero</h2>In the previous section we analyzed the hero pages and thinking of what fields to use for defining the pages.&nbsp; In this section, we will create the Content Type for the Character.&nbsp; If you wish to copy / paste the code samples later, we would advise you to define the content type with the fields in this exercise.&nbsp; However, if you wish to use your own field definitions, that's fine, but you will also need to adjust the code samples accordingly.Creating the Content TypeUsing the Content Type editor in Contentstack, create a new Content Type with fields for our Character content. &nbsp;While defining the fields, we will need to consider what content we want to show on the detail page. &nbsp;<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/Kv6fnat6-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-creating The Character Content Type" style="position: absolute;" allowfullscreen=""></iframe></div> After the exercise, your Content Type should look like this:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576421/original/e6b48a68-8105-4d04-8e47-6a660bb9286a-Screen_Shot_2023-05-09_at_12.58.54_AM.png" style="max-width: 418px;width: 418;" width="418"/>Steps for the exercise: 1.&nbsp; Create a new Content Type, named ‘Character’ for the composable heroes 2.&nbsp; Add the following fields:Hero Name - Use the Title field Every Content Type in Contentstack has a Title field.&nbsp; We can give it a different display name such as 'Name' or 'Character Name', but we cannot remove it.URL For the Path, use '/composable-heroes/'&nbsp; and then select the option to append the Title to the URL.&nbsp; This is the most common way to define the URL structure.&nbsp; For Content Types where we know the kind of content each page has (character) and that they will have detail pages, we decide to use '/composable-heroes/' as the URL path and then add the title to the end. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576423/original/a4055110-3b05-43fb-a0f3-6355751098d4-Screen_Shot_2023-05-04_at_9.26.43_AM.png" width="429" height="auto" max-width="429" style="max-width: 429px;width: 429;height: auto;"/>Image (File) Contentstack has an <a href="https://www.contentstack.com/docs/developers/apis/image-delivery-api/">Images API</a> and supports uploading any media file, including images, up to 700 MB.&nbsp; For images, there are additional properties such as min/max on width or height, so the CMS ensures the images used in a field meet the minimum size requirements. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576424/original/2f33417f-aa75-4be4-9c57-c53a4ed06ac5-Screen_Shot_2023-04-26_at_1.08.11_PM.png" width="428" height="auto" max-width="428" style="max-width: 428px;width: 428;height: auto;"/>Description (JSON RTE)The JSON RTE field stores the content in JSON and the frontend webapp uses a <a href="https://github.com/contentstack/json-rte-serializer/">JSON RTE Serializer</a> after publishing to transform the JSON to HTML.&nbsp; There is also an <a href="https://www.contentstack.com/docs/developers/automation-hub-connectors/rte-formatter/">Automation Hub connector that can transform the RTE JSON to HTML</a>.&nbsp;&nbsp;The JSON RTE supports custom plugins and you can use the <a href="https://www.contentstack.com/docs/developers/developer-hub/get-started-with-building-apps-using-contentstack-app-sdk/">App SDK</a> and extend the Rich Text Area with your own customizations.&nbsp; Examples in the Marketplace include a word count extension and a Cloudinary extension.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576425/original/ffbba911-f239-40f7-b0dc-eb37c2c6377e-Screen_Shot_2023-04-26_at_1.08.56_PM.png" width="409" height="auto" max-width="409" style="max-width: 409px;width: 409;height: auto;"/>Powers (select field, add the powers)<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576426/original/8a997970-e473-4b49-8238-127f6df95337-Screen_Shot_2023-04-26_at_1.14.30_PM.png" width="413" height="auto" max-width="413" style="max-width: 413px;width: 413;height: auto;"/>Contact Info (Group field, email, phone)Group fields help us organize content fields and in the UI the editor can collapse / open the group.&nbsp; They're also helpful when using the <a href="https://www.contentstack.com/docs/developers/create-content-types/about-field-visibility-rules/">Visibility Rules</a> in Content Types Home world (Reference field)The Home world has an image and some additional properties, so we use a Reference Field and define a Content Type for the Home World instead of using a select field or defining the fields here.<blockquote>Reference fields should be used when the content you want to include either already exists as a standalone entry (or part of one), or will be used by multiple content entries (either of the same type or not)</blockquote> SEOAdd a Global Field and choose the SEO Global Field <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576427/original/e8906710-de5a-4608-ae60-65cb78377132-Screen_Shot_2023-04-26_at_1.18.05_PM.png" width="423" height="auto" max-width="423" style="max-width: 423px;width: 423;height: auto;"/> All Done!Congrats - you are done with the Content Type definition.&nbsp;&nbsp; 3.&nbsp; Now, let's try out the new Character Content Type.&nbsp; Create a new Entry with the Character Content Type and fill in the content and publish to Development<h2>Content Type Best Practices</h2>URL field: &nbsp;Best practices/patterns. &nbsp;Use the /path/:title for most content types, where relevant. &nbsp;This maps to the Route in the web application and is also important for SEO. Choose this wisely. Image field: &nbsp;Consider using the height/width limitations Text fields: &nbsp;Consider any validations Modular Blocks: Think of this as a ‘design system’ of components the user can choose from. &nbsp; They have the flexibility to add it if they want, or not. &nbsp;Blocks can also be added at a later time to extend the content type. This can be done in confidence that things will not break if adjustments are made.If you're using a modern framework such as NextJS or Nuxt, then we can think of having a NextJS Component responsible for rendering the content of one Modular Block.&nbsp; In this way, the content and design are atomic and can be re-used across multiple pages. Reference fields:&nbsp; When re-using content with many entries, we can use a Reference Field and connect the Entries.&nbsp; We will need to add an additional query parameter to the Content Delivery Queries so that the referenced Entry fields will also be returned.&nbsp; One example of using a reference field is on a homepage or landing page where we want to also show a listing of articles, products in a promo, etc.&nbsp;&nbsp; However, be mindful when implementing Reference fields as they can be easily overused. &nbsp;When modeling content, it’s best to keep the relationship &nbsp;as flat as possible and only use reference fields when referring to another type of content that is mostly independent of the model it is being referenced in. &nbsp;If content fields are only used by the current entry, then it’s better to include them in the content type rather than using a reference field. &nbsp;Reference field over-use is the most common content modeling pitfalls &nbsp;and increases the complexity of the system for end users.&nbsp;<h1>Create the NextJS Component for the superhero detail page</h1>Next step is to render the Character Entries on a superhero detail page.&nbsp; This process involves the following steps:<ol><li>Create a new NextJS Component and import the Contentstack libraries</li><li>Use the HTML Provided and add the code to render the Contentstack Character Content Type fields</li><li>Run locally and preview the page</li></ol>
 Now that we have defined our superheroes using the Character Content Type and added some sample content, it's time to create a detail page to display them on our website. The HTML file for the superhero detail page is provided below. Using Contentstack's Content Delivery API and Next.js, we can create the code to render this page on our website.<h2>Programming the Character Detail Page</h2>1. Create a new NextJS Component for the detail page in a folder 'composable-heroes' and using the name [post].tsx2.&nbsp; Analyze the code for the Detail page and notice how we render text fields, reference fields and group fields.&nbsp; <a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/pages/composable-heroes/%5Bpost%5D.tsx">The code is available on Github here.</a>3.&nbsp; Examine&nbsp;the Helper/index.js file and <a href="https://github.com/contentstack/contentstack-academy-playground/blob/89452b765dac23970f24ece7412beefc62bb18ec/helper/index.js#L106">review the code for getting a Single Entry (Character Content Type)</a>.&nbsp; This function will use the existing method ‘GetEntryByUrl in the /contentstack-sdk/index.js file to query for the Entry content.&nbsp;<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576428/original/ba2d9c71-9a7d-46a3-a41a-2c81a2578d35-Screen_Shot_2023-05-09_at_1.04.14_AM.png" width="100"/><a href="https://www.contentstack.com/docs/developers/sdks/content-delivery-sdk/javascript-browser/">Content Delivery JS SDK API Ref</a>
 <a href="https://gist.github.com/robertcurlette-cs/066c818c09c752426056eee7e9fa541c">Examples using the Content Delivery JS SDK in a NextJS Service</a>&nbsp;
 4.&nbsp; Call the Character Query function from the NextJS <a href="https://github.com/contentstack/contentstack-academy-playground/blob/89452b765dac23970f24ece7412beefc62bb18ec/pages/composable-heroes/%5Bpost%5D.tsx#L62">composable-heroes/[post].tsx file</a><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576429/original/536c1ec8-26a2-4463-9b2c-ac1d4cb0c406-Screen_Shot_2023-05-09_at_1.05.22_AM.png" width="100"/> <h2><a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/pages/composable-heroes/%5Bpost%5D.tsx">Code Solution for Composable Hero Detail Page on Github</a></h2> <h2>Field rendering syntax:</h2>Text fields - Rendering the title field{postData?.title}Group fields{postData?.contact_info?.email ? Email : {postData?.contact_info?.email}Images<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576430/original/27ff385a-3aec-4a86-b6d6-846e1e93a850-Screen_Shot_2023-04-26_at_3.21.16_PM.png" width="100"/>
 Reference Field<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576431/original/dd877173-7f63-433b-8f66-c0518119dea5-Screen_Shot_2023-05-08_at_12.14.37_AM.png" width="100"/> 6.&nbsp; Confirm your code with the Composable Detail Page solutionFinal Result - Composable Hero&nbsp;Detail Page<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576432/original/1f0d87fe-ffd0-41b7-bda4-c4ba9d54a610-Screen_Shot_2023-05-07_at_9.28.44_PM.png" width="100"/>

Creating the Hero Detail Page

<h2>The Composable Hero&nbsp;Landing Page</h2>Welcome to this tutorial on creating a superhero gallery page using reference fields in NextJS! In this module, we'll walk you through the steps of creating a new content type called "Superhero Gallery Page" and adding heroes to it manually.&nbsp;We'll start by showing you how to utilize reference fields to display hero content on the landing page with their images and names. This technique is commonly used in product promotions and article index pages, so it's a valuable skill to learn.&nbsp;Next, we'll guide you through the process of creating a new NextJS component and query to retrieve the Landing Page Entry and Reference field Hero Entries. Our NextJS component will loop through all the heroes in the reference field and display their titles, images, and links to their respective detail pages.Finally, we'll demonstrate how to create a new Landing Page Entry and publish it to the Development environment to see the results of our work.By the end of this tutorial, you'll have gained valuable knowledge on how to utilize reference fields in NextJS to create reusable content and enhance the user experience on your website. Let's get started!<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576433/original/7351ff1b-3d8b-41bd-8166-5e28ee77c3ac-Screen_Shot_2023-05-09_at_2.32.13_PM.png" width="556" height="auto" max-width="556" style="max-width: 556px;width: 556;height: auto;"/><h1> </h1><h2>Hero Gallery&nbsp;Page Content Type</h2><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576434/original/0a22ff01-dad0-4e2e-8441-1d78383354a5-Screen_Shot_2023-05-09_at_2.36.28_PM.png" width="462" height="auto" max-width="462" style="max-width: 462px;width: 462;height: auto;"/><h2></h2><h4>Open the Superhero Gallery Page and examine the properties of each field</h4><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576435/original/cdaab9d8-2f03-4f07-85e3-840ab35bc575-Screen_Shot_2023-05-09_at_1.09.30_AM.png" width="469" height="auto" max-width="469" style="max-width: 469px;width: 469;height: auto;"/>Review the following fields below:<ul><li>Title - Default Title field</li><li>URL - /gallery/:title</li><li>Heading - Text field</li><li>Description - Multi-line text</li><li>Characters - Reference field to the Character Content Type</li></ul><h2>Part 2: Writing the code to display the list of heroes</h2>Let's list all the heroes in the reference field on the Gallery&nbsp;page.&nbsp; Users can manually create a list of heroes and our code will loop over all the heroes in the reference field and render the name, image, and link.&nbsp; <h3>Rendering a list of Characters from a Reference Field</h3> 1.&nbsp;&nbsp;Create a NextJS Component for the Gallery page and loop through all the heroes in the reference field, rendering&nbsp;the title, image and a link to the detail page.&nbsp; This involves 2 steps, first writing the query function and then rendering the results. 2.&nbsp; Querying Contentstack for the Characters in the Reference Field <a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/helper/index.js">In the /helpers/index.js file</a>, review the function to get a list of heroes from the reference field 3.&nbsp; <a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/pages/composable-heroes/index.tsx">Review the code for the /composable-heroes/index.tsx file</a>.&nbsp;&nbsp; 4.&nbsp; Review the Composable Heroes Gallery Entry <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576436/original/ff9608d8-86a2-47b1-bb4e-18eb9fd72215-Screen_Shot_2023-05-09_at_1.13.41_AM.png" width="100"/> 5.&nbsp; From the NextJS application, open the Composable Heroes Gallery Page<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576437/original/85ca2631-13ac-4c17-9940-82a4086a4088-Screen_Shot_2023-05-09_at_1.14.40_AM.png" width="100"/> 2. Introduction to using the Query functions of the Content Delivery APIContentstack provides certain queries that you can use to fetch filtered results. You can use queries for Entries and Assets API requests.&nbsp; Please review the <a href="https://www.contentstack.com/docs/developers/apis/content-delivery-api/#queries">Content Delivery Query API documentation</a> and examine the RegEx, Limit and Only functions.For the first part of the exercise, we can use a simple query to find all the entries with the Content Type of Character.&nbsp;&nbsp;<h3>Postman</h3>1.&nbsp; Open Postman and select the Entries/Get Entries call Update the parameters / variables so that:<ul><li>content_type_uid = character</li><li>environment = development </li></ul><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576438/original/cb5eafd4-786d-4d22-b071-b2ba5d4df15e-Screen_Shot_2023-05-04_at_10.11.17_AM.png" width="100"/>You should now have a list of the characters published to the development environment.&nbsp; In the next section, we will use the JavaScript SDK to get the same list and pass it to the NextJS App to render. 3. Query using Javascript SDKIn our web application we will mostly use the <a href="https://www.contentstack.com/docs/developers/sdks/content-delivery-sdk/javascript-browser/reference/">Javascript Content Delivery SDK</a>.&nbsp; Please have a look at the <a href="https://www.contentstack.com/docs/developers/sdks/content-delivery-sdk/javascript-browser/reference/#query">documentation for the query methods</a>.Other SDKs can be found on the <a href="https://www.contentstack.com/docs/developers/sdks/">SDKs documentation page</a><pre>import Contentstack from 'contentstack'; const Stack = Contentstack.Stack({"api_key": "api_key", "delivery_token": "delivery_token", "environment": "environment"}); const result = await Stack.ContentType('character').Query().toJSON().find();</pre><a href="https://www.contentstack.com/docs/developers/sdks/content-delivery-sdk/javascript-browser/reference/#stack-query">More information about this is found in the Javascript SDK Docs</a><h2>Composable Hero Landing Page</h2>The Composable Hero Landing Page uses <a href="https://www.contentstack.com/docs/developers/create-content-types/modular-blocks/">Modular Blocks</a> to provide a flexible structure for authors to create content and add as many content blocks to the page as they wish and also to re-order the blocks.&nbsp;&nbsp;<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576439/original/e0b510f4-af55-47bd-ab1b-828aeac8f24c-Screen_Shot_2023-05-09_at_2.43.15_PM.png" width="100"/> <h2>Open the Superhero Landing Page Entry and review the content</h2><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576440/original/ba505a62-160b-4fcd-9c14-8dd286465340-Screen_Shot_2023-05-09_at_2.39.02_PM.png" width="100"/><h2> </h2><h2>Open the Content Type Definition and examine how the Modular Blocks field is used.&nbsp;</h2>Notice the fields are greyed out - that is because the Modular Block fields are defined using Global Fields.&nbsp; This is a best practice.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576441/original/6abb16ec-3b2f-41bc-bae3-08bd7ec5e042-Screen_Shot_2023-05-09_at_2.45.56_PM.png" width="100"/><h2>Global Field Definitions</h2><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576442/original/ae57a06e-2739-4b32-bada-3a97492cc80f-Screen_Shot_2023-05-09_at_2.47.42_PM.png" width="100"/><h2> </h2><h2>Examine the Code used for the Hero Landing Page</h2>The <a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/pages/gallery.tsx">code for the Gallery Entry (Page)</a>&nbsp;loops through all the Modular Blocks on the page and renders each one with its' own NextJS Component. <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576443/original/7f386f93-cfcc-4b17-91cf-7a37bc2191b4-Screen_Shot_2023-05-09_at_3.10.22_PM.png" width="684" height="auto" max-width="684" style="max-width: 684px;width: 684;height: auto;"/><h2>Each block is rendered with its own NextJS Component</h2><ul><li><div><a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/components/gallery.tsx">Gallery Block</a><a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/components/gallery.tsx"> </a><div><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576444/original/a02cc6fd-09ab-4fb8-8a99-d7952aa8fa0b-Screen_Shot_2023-05-09_at_3.07.40_PM.png" width="591" anchorlink="https://github.com/contentstack/contentstack-academy-playground/blob/main/components/gallery.tsx" height="auto" max-width="591" style="max-width: 591px;width: 591;height: auto;"/></div></div> </li><li><div><a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/components/hero-banner.tsx">Hero Banner Block</a><a href="https://github.com/contentstack/contentstack-academy-playground/blob/main/components/hero-banner.tsx"> </a><div><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576445/original/b5794bc2-878a-43d6-9cc9-b93f6898929c-Screen_Shot_2023-05-09_at_3.05.27_PM.png" width="552" anchorlink="https://github.com/contentstack/contentstack-academy-playground/blob/main/components/hero-banner.tsx" height="auto" max-width="552" style="max-width: 552px;width: 552;height: auto;"/></div></div></li></ul>By adopting this approach, we can isolate the HTML/Code for each block within a single NextJS Component. This simplifies maintenance and enables easy extension of the page in the future by adding a Modular Block and NextJS Component for additional content block types.&nbsp;With this method, you can modify the individual content blocks without having to make changes to the entire page structure. This approach makes the codebase more organized and easier to manage, especially when dealing with complex web applications.&nbsp;By leveraging this technique, you can increase the scalability and modularity of your website, allowing you to add new features and functionalities with ease.

Creating the Hero Gallery Page

<h3>Using Modular Blocks - Advantages</h3>There are several advantages to using Contentstack's modular blocks when designing content types. Here are some of the key advantages:1. Flexibility for marketers: Modular blocks allow marketers to easily create and customize content without requiring technical expertise. With modular blocks, marketers can easily use pre-designed content blocks to create engaging content without having to worry about formatting or layout.2. Reusability: With Global Fields, Modular blocks can be reused across different content types and pages, which can help to save time and effort when creating new content.3. Consistency: Modular blocks ensure consistency in content formatting and layout, which can help to improve the overall user experience.4. Granular control: Modular blocks provide developers with granular control over content structure and formatting, which can help to ensure that content is properly organized and optimized for SEO.5. Easy maintenance: With modular blocks, it is easy to update and maintain content without having to modify the entire content type or page.7. Future-proofing: Modular blocks provide a future-proof solution for content design, as they can be easily updated and modified to meet changing business needs.<h2>Example:&nbsp; Using Modular Blocks in the&nbsp; Starter App</h2>In the Starter App, the Page Content Type uses Modular Blocks to define the various sections of the page.&nbsp; In this example below, notice how each block or module on the page is a Modular Block.&nbsp; In this example we have 3 Modular Blocks.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576483/original/1e5e7a8d-d933-463c-a2ad-7c06c2a2da8b-Screen_Shot_2023-05-03_at_11.14.20_AM.png" width="100"/> These Blocks are used in the Page Content Type.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576484/original/7d7e42c3-cee6-42b1-8ac8-b29a8f32668d-Screen_Shot_2023-05-03_at_11.12.53_AM.png" width="100"/> <h2>Using Global Fields for Defining Re-Usable Content Structures</h2>Global Fields in Contentstack promote the re-use of content structures across content types.&nbsp; They allow us to define a schema of fields and then reference that definition from another content type or modular block.In the StarterApp website, the SEO fields are defined as Global Fields. This makes it easy to manage the SEO fields from one location and re-use the definition across all content types.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576485/original/0739517a-093e-4ae1-99a9-7e4ca5ee8170-Screen_Shot_2023-05-03_at_11.18.29_AM.png" width="100"/><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576486/original/82a84dd9-2701-48b5-be98-a67313de2711-Screen_Shot_2023-05-03_at_11.19.28_AM.png" width="100"/> <h2>Using Global Fields for Modular Blocks</h2>Global fields can&nbsp; also be used to define field sets for Modular Blocks. This is a great way to re-use structure.&nbsp; Note, it is currently not possible to nest a Global Field inside another Global Field, so take that into consideration when designing your content types.<h2>Resources</h2><ul><li><a href="https://www.contentstack.com/docs/developers/create-content-types/modular-blocks/">Modular Blocks</a></li><li><a href="https://www.contentstack.com/docs/developers/global-field/">Global Fields</a></li><li><a href="https://www.contentstack.com/docs/developers/global-field/limitations-of-global-field/">Limitations of Global Fields</a></li><li><a href="https://www.contentstack.com/docs/developers/content-modeling/content-modeling-best-practices/">Content Modeling Best Practices</a></li></ul>

Design Patterns with Content Types

With Contentstack's launch product, developers can focus on building and updating their applications while leaving the hosting infrastructure to Contentstack.To assist users with the various functionalities of this product, Contentstack offers a <a href="https://www.contentstack.com/docs/developers/launch/">comprehensive help center</a> on its website. The help center includes detailed guides and tutorials on <a href="https://www.contentstack.com/docs/developers/launch/import-project-using-github/">creating projects</a>, <a href="https://www.contentstack.com/docs/developers/launch/deploy-hooks/">setting up deploy hooks</a>, and <a href="https://www.contentstack.com/docs/developers/launch/redeploy-automatically-when-content-is-published-on-CMS/">redeploying applications</a> when content is published. Additionally, the website provides a robust community forum where users can interact with other users, share their experiences, and get support from the Contentstack team.<ul><li>Host&nbsp;your website or web app directly from Contentstack, leveraging our high-speed CDN and proven infrastructure.</li><li>Link&nbsp;your Contentstack Stacks and front-end environments without copying and pasting API keys.</li><li>Leverage&nbsp;the only front-end site hosting solution that’s built explicitly for the Contentstack CMS.</li></ul><h2>Framework agnostic</h2>Build projects in virtually any common Javascript front-end framework, easily connect to and deploy code directly from a git repository.<ul><li>Automatic&nbsp;configuration for Nextjs and Gatsby, with more frameworks on the way</li><li>Use&nbsp;virtually any composable Javascript front-end framework with custom build commands.</li><li>Upload&nbsp;static site files via Zip for instant deployment for projects that don’t use git.</li><li>Support&nbsp;for Edge functions and more&nbsp;coming soon!</li></ul><h1>Exercise: Deploy the site with Contentstack Launch</h1>1.&nbsp; Open Launch
 <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576475/original/a9960371-c5f0-4ac2-b19b-2501027d168e-Screen_Shot_2023-05-02_at_5.23.55_PM.png" width="100"/>
 2.&nbsp; New Project
 3.&nbsp; Upload File<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576476/original/b77286c5-3952-468d-b4a7-36a0e493f026-Screen_Shot_2023-05-02_at_5.30.18_PM.png" width="100"/>
 4. Upload the StarterApp project.&nbsp; In this example, we will use the NextJS Starter App.&nbsp; Download the code from the Github repository here:&nbsp;<a href="https://github.com/contentstack/contentstack-nextjs-starter-app">https://github.com/contentstack/contentstack-nextjs-starter-app</a>
 5.&nbsp; Select your Stack with the Starter App and then Import Environment Variables<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576477/original/facb6650-d650-49de-bba1-379cd6daa9d0-Screen_Shot_2023-05-02_at_5.39.21_PM.png" width="100"/>6.&nbsp; Site is being deployed.&nbsp; This takes up to 5 minutes.&nbsp; The URL will be a Contentstack URL with the free trial, however, with a paid plan you will be able to use custom domains.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576478/original/41220368-8584-48c8-9294-e2c6b160b1e1-Screen_Shot_2023-05-02_at_5.34.30_PM.png" width="100"/>
 7.&nbsp; Site is deployed <h3>Learn More About Launch</h3><ul><li><a href="https://www.contentstack.com/docs/developers/launch/">Developer Documentation</a></li><li><a href="https://community.contentstack.com/search?q=Launch&search_type=tag">Community Forum</a></li><li><a href="https://www.contentstack.com/docs/developers/launch/quick-start-nextjs/">Guide for Deploying the StarterApp with Launch</a></li></ul>

Deploying the Starter App with Contentstack Launch

<h2>Introduction to the Content Management API</h2>Our Content Management API (CMA) is a powerful tool that provides a read/write API with a REST interface, as well as SDKs for JavaScript, .NET, and Java. To authenticate with the CMA, we use Tokens. In this exercise, we'll guide you through how to use the CMA with Postman, a popular tool that helps developers use APIs.Let's get started with the exercise. We'll be using Postman, so first, make sure to download the latest Contentstack Postman collection from here: <a href="https://www.contentstack.com/docs/developers/apis/content-management-api/#install-postman">https://www.contentstack.com/docs/developers/apis/content-management-api/#install-postman</a>Also, download and use the Postman Environment Files from Github here: <a href="https://github.com/contentstack/contentstack-postman-collections#environment-files">https://github.com/contentstack/contentstack-postman-collections#environment-files</a><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576448/original/0b816fb7-b254-460a-9ed3-44dcdd58c593-Screen_Shot_2023-05-08_at_12.11.44_PM.png" width="100"/>
 The next step is to create a Management Token to use in our Postman query. To do this, go to Settings in the Contentstack UI, then Tokens, Content Management, and create a Management Token. You can follow this guide for more detailed instructions: <a href="https://www.contentstack.com/docs/developers/create-tokens/generate-a-management-token/">https://www.contentstack.com/docs/developers/create-tokens/generate-a-management-token/</a><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576449/original/55d959c4-0c30-4fd8-aa1d-430234bd3327-Screen_Shot_2023-05-08_at_2.16.32_PM.png" width="100"/>
 Now, open Postman and add the Content Management API Postman Collection. Select Content Management API - Contentstack, Entries, Get a single entry, and you're ready to go!In Postman, select Content Management API -&nbsp;Contentstack, Entries, Get a single entry
 Update the API Key and Access TokenThere are two ways to set the values, using Postman variables like above or hard-coding the values in the Value column. &nbsp;I prefer to use the Environment variables. <a href="https://github.com/contentstack/contentstack-postman-collections#environment-files">https://github.com/contentstack/contentstack-postman-collections#environment-files</a>1.&nbsp; Set the Environment variable values for your Stack in Postman by selecting the icon in the top-right of Postman to open the Environment variable window.Specify the following header values:
 - api_key - This is located in the Settings, Tokens, Management Token page. &nbsp;You can also see it in the URL of the browser, after the /stack/ part of the URL, http://app.contentstack.com/#!/stack/{api_key}- authorization - Management token created in step 12.&nbsp; Use the ‘Get a single entry’’ method and add the base_url, content_type_uid (character) and entry uid to the query. &nbsp;This will retrieve the JSON for the Entry using the backend CMA. &nbsp;*Note, we do not use this API for our frontend website applications as it is not intended for high load / performance. &nbsp;Instead, the frontend web applications use the Content Delivery API which is tuned for high performance.3.&nbsp; Run the query and see the JSON result.
 Notice that we have Create / Read / Update / Delete operations for most types.
 Using the JSON returned from the Get Entry method, we will create new JSON to use for the Create Entry method in the next exercise.
 &nbsp;
 Learn More:
 Key Features of Management Tokens: <a href="https://www.contentstack.com/docs/developers/create-tokens/key-features/">https://www.contentstack.com/docs/developers/create-tokens/key-features/</a><h2>Creating content with the API:&nbsp; Using the Content Management API</h2><h3>Exercise: &nbsp;Create an entry with the Postman API</h3>In this exercise, we'll guide you through creating a new Entry in Contentstack programmatically using our Content Management API. This method is incredibly useful for quickly migrating content from external systems and avoiding manual entry.The trickiest part of this process is creating well-formed JSON that contains all the properties and content for the Entry. But don't worry - we've got you covered. In the previous exercise, we used our CMA to retrieve the Entry JSON, and now we'll use a subset of that JSON to create our new Entry.If you weren't able to retrieve the JSON Entry export in the previous exercise, we've included a sample below. Just make sure to update the UID of the Content Type for it to work.To get started, let's create the Entry JSON required to make a new Entry. Below is an example JSON, but remember to replace the Content Type UID:<pre>{ "title": "New Entry Title", "url": "/new-entry-url", "description": "This is a new Entry created programmatically using the Content Management API.", "content_type_uid": "your-content-type-uid", "metadata": { "tags": ["tag1", "tag2"], "author": "John Doe" }, "body": "</pre><pre>This is the body of the new Entry.</pre><pre>" }</pre>Now, in Postman, open the ‘Create an entry’ method and in the body tab, paste the JSON of the new Entry. Please note that the Title property of the Entry needs to be unique.As we used Postman variables in the previous exercise, you won't need to add any additional settings here, since the api_key and management token are already specified.Finally, hit the Send button in Postman to create your new Entry. Head over to the Contentstack UI to confirm that it has been created successfully.<h2>Exporting Content from Contentstack</h2>Contentstack stores all text content in JSON format.&nbsp; This makes it very easy to import / export and update content using the Content Management API or the CLI.&nbsp; In this section we will discuss the three ways to export content from Contentstack:&nbsp; UI, CM API, and the CLI.<h2>Exporting with the UI</h2><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576450/original/53d9742d-b104-4073-b504-fb9397bcd254-Screen_Shot_2023-05-09_at_12.44.54_PM.png" width="100"/><h2>
 </h2><h2><a href="https://www.contentstack.com/docs/developers/apis/postman-collections/">Exporting with Postman</a></h2><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576451/original/e0fbe528-81a9-4655-8ee4-4a24dab61752-Screen_Shot_2023-05-09_at_12.49.30_PM.png" width="100"/><h2>
 </h2><h2><a href="https://www.contentstack.com/docs/developers/cli/export-content-using-the-cli/">Exporting with the CLI</a></h2><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576452/original/4179c27a-8eab-42dd-b435-4b60e0208ac6-Screen_Shot_2023-05-09_at_12.54.00_PM.png" width="100"/> <h2>Exporting Content from Contentstack</h2>Contentstack stores all text content in JSON format.&nbsp; This makes it very easy to import / export and update content using the Content Management API or the CLI.&nbsp; In this section we will discuss the three ways to export content from Contentstack:&nbsp; UI, CM API, and the CLI.<h4>Exporting with the UI</h4><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576450/original/53d9742d-b104-4073-b504-fb9397bcd254-Screen_Shot_2023-05-09_at_12.44.54_PM.png" width="100"/><h2>
 </h2><h4><a href="https://www.contentstack.com/docs/developers/apis/postman-collections/">Exporting with Postman</a></h4><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576451/original/e0fbe528-81a9-4655-8ee4-4a24dab61752-Screen_Shot_2023-05-09_at_12.49.30_PM.png" width="100"/><h2> </h2><h4><a href="https://www.contentstack.com/docs/developers/cli/export-content-using-the-cli/">Exporting with the CLI</a></h4><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576452/original/4179c27a-8eab-42dd-b435-4b60e0208ac6-Screen_Shot_2023-05-09_at_12.54.00_PM.png" width="100"/>

Importing Content with the CLI and CMA

<h2>Roles</h2>Contentstack has a robust roles and permissions system with built-in roles such as 'Admin', 'Developer', and 'Content Manager' and the ability to create custom roles for authors and editors.&nbsp; In this module we will look briefly at the roles and permissions system in Contentstack.Built-in RolesAdmin:&nbsp;Admin has full access to all features and functions within Contentstack, including the ability to create, edit, and delete content, manage users and roles, and configure the system settings. Super Admins have the highest level of privileges and can perform any action within the platform.Content Manager: The Content Manager has the ability to create, edit, and delete content, as well as manage users and roles. However, they do not have access to the system settings or the ability to perform advanced tasks such as configuring webhooks or integrations.Developer: The Developer role is designed for users who need to access the Contentstack API and develop custom solutions using the platform. Developers have the ability to create and manage content types, as well as access the API documentation and sample code. However, they do not have the ability to manage users and roles. Custom RolesIn Contentstack, custom roles allow users to define and customize the level of access and permissions for specific users or groups of users. This provides greater flexibility and control over how content is managed and published within the system.To create a custom role, a Super Admin or a user with the "Manage Roles" permission can navigate to the Roles section of the Contentstack dashboard and click on the "Add Role" button. From here, they can give the custom role a name and select the specific permissions that they want to grant to users assigned to that role.The available permissions can be grouped into three categories:<ul><li>Content: permissions related to creating, editing, and publishing content and images</li><li>Publishing: permissions related to publishing content and environments</li><li>Languages: Permissions relating to localization</li></ul>Once the custom role is created, it can be assigned to specific users or groups of users within the system. Users assigned to the custom role will only have access to the permissions and features that are granted to that role, ensuring that they only have access to the specific tasks and content that they are responsible for. This helps to improve security and streamline workflows within the system.<h2>Exercise: Creating a custom role</h2>&nbsp;Here are the steps to create a custom role in Contentstack:1. Log in to your Contentstack account and navigate to the “Settings / Users &amp; Roles / Roles” section of the dashboard.2. Click on the “New Role” button to create a new custom role.3. In the “Role Details” section, enter a name for your custom role.4. Next, choose the permissions you want to grant to this role by selecting the options for each permission category (Content, Assets, Languages and Environments).5. Under each permission category, you can select or deselect specific permissions that you want to include or exclude for this role.7. Once you have selected the permissions you want to grant to the custom role, click the “Save” button to save the role.8. To assign users to the custom role, navigate to the “Users” section of the dashboard and select the user(s) you want to assign the role to.9. In the “Update User” dialog box, select the “Roles” tab, and then select the custom role you created from the list of available roles.10. Click the “Save” button to save the changes.That's it! You have now created a custom role in Contentstack and assigned it to specific users within your organization.<h3>Resources</h3><ul><li><a href="https://www.contentstack.com/docs/developers/invite-users-and-assign-roles/examples-to-create-custom-roles/">Examples to create custom roles</a></li></ul><div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/owFEMYhE-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-roles In Contentstack" style="position: absolute;" allowfullscreen=""></iframe></div>

Working with Roles and Permissions

Contentstack's workflow feature is a powerful tool that enables organizations to manage the content creation and publishing process in a streamlined and efficient way. With workflow, content creation and publishing becomes a collaborative process that involves multiple stakeholders, including writers, editors, and approvers.&nbsp;The workflow feature allows you to define a series of states that content can go through, from initial creation to final approval and publishing. Each state represents a stage in the content creation process, and can be assigned to different roles or users. For example, you can set up states such as "Draft", "In Review", "Approved", and "Published".As content moves through the workflow, it can be edited, reviewed, and approved by different users based on their assigned roles. Users can add comments and feedback, and content can be easily tracked and managed throughout the entire process. This ensures that content is thoroughly reviewed and approved before being published, minimizing the risk of errors or inaccuracies.Contentstack's workflow feature also includes notifications and alerts, which keep everyone involved in the process informed of content changes, updates, and approvals. This helps to keep the process moving smoothly and ensures that everyone is on the same page.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576482/original/d66f2fac-5ce5-4725-89f4-c6e7e7e87938-Screen_Shot_2023-05-03_at_11.06.04_AM.png" width="100"/><h2>Exercise: Creating a Workflow with a Publish Rule</h2>Here's a step-by-step guide on how to use Contentstack's workflow feature to create a publishing rule for production:Step 1: Log in to your Contentstack account and select the stack you want to work with.Step 2: Click on the "Settings" button in the top navigation bar.Step 3: Click on the "Workflows" tab.Step 4: Click on the "New Workflow" button.Step 5: Enter the following:
 - Name: &nbsp;"Blog Workflow". &nbsp;
 - Scope (branches): Main. &nbsp;
 - Specific Content Types: Blog EntryStep 6: Add the states that content will go through before being published. For example, you could add the states "Draft", "In Review", "Approved", and "Published".Step 7: Click on the "Enable Workflow" checkbox and the "Save" button to create the workflow.Step 8: Next, you'll need to create a publishing rule that specifies which content should be published to your production environment. Click on the "Publishing Rules" tab.Step 9: Click on the "New Publishing Rule" button.Step 10: Enter a name for your publishing rule, such as "Publish to Production".Step 11: Under "Content type", select the "Blog Entry" Content TypeStep 12: Under "Language", select "All Languages"Step 13: Under "Environment", select "Production"Step 14: Under "Rule Conditions", you can set up conditions that must be met before the content is published. For example, you could require that the content has the "Approved" state before it can be published.Step 15: Click on the "Save" button to save the publishing rule.Step 16: Now, whenever content is created or updated, it will go through the workflow you created in step 5. If the content meets the conditions you set up in the publishing rule, it will be published to your production environment automatically.Congratulations! You have successfully created a publishing rule for production using Contentstack's workflow feature. This will help you streamline your content creation and publishing process and ensure that only approved content is published to your production environment.<h2>Example: Using Workflow and Webhooks for Automating Translation</h2>In the context of a Contentstack workflow, a webhook trigger can be used to automate the movement of content through the different stages of the workflow or send to an external service such as a translation agency.&nbsp;To set up a webhook trigger to use a workflow stage in Contentstack, you would first need to create a workflow and define the stages that content should go through. Once the workflow is set up, you can create a webhook trigger that is triggered when content is created or updated.In the webhook trigger settings, you can specify the workflow stage that the content should be moved to when the webhook is triggered. For example, you could set up the webhook trigger to move the content from the "Draft" stage to the "In Review" stage when it is created or updated.Once the webhook trigger is set up, it will automatically move the content through the workflow based on the rules that you have defined. This can help to save time and improve efficiency, as content can be automatically routed to the appropriate stage without requiring manual intervention.
 Step 1: Set up your workflow in Contentstack
 First, you'll need to set up your workflow in Contentstack to define the stages that content should go through before it is published. For example, you might create stages for "Draft", "In Review", and "Approved".Step 2: Set up a webhook trigger
 Next, you'll need to set up a webhook trigger that is triggered when content is created or updated. In the webhook trigger settings, you can specify the URL of your 3rd-party translation service, along with any required authentication details.Step 3: Define a workflow stage for translation
 In your workflow, you can define a new stage specifically for translation. For example, you might create a stage called "Translation" that is between the "In Review" and "Approved" stages.Step 4: Set up a webhook action to send content to the translation service
 In the workflow stage for translation, you can set up a webhook action that sends the content to the 3rd-party translation service. You can use the webhook trigger that you set up in step 2 to automatically send the content to the translation service when it enters the "Translation" stage.Step 5: Receive and process the translated content
 Once the content has been sent to the translation service, the service will translate the content into the desired language(s). The translation service can then send the translated content back to Contentstack via another webhook trigger.Step 6: Move the translated content to the next stage in the workflow
 When the translated content is received by Contentstack, you can set up another webhook action that automatically moves the content to the next stage in the workflow. For example, you might move the content from the "Translation" stage to the "Approved" stage when it is received.Overall, using a Contentstack webhook trigger with workflow to send content to a 3rd-party translation service can help to streamline the translation process and ensure that content is translated efficiently and accurately.&nbsp;<h1>Resources</h1><ul><li><a href="https://www.contentstack.com/docs/developers/set-up-workflows-and-publish-rules/">Workflow Documentation</a></li><li><a href="https://www.contentstack.com/docs/developers/how-to-guides/#translation-services">Translation Integrations</a></li></ul>

Workflow

Contentstack's webhook system is a powerful tool that allows developers to automate the process of receiving real-time notifications of changes made to content within the CMS. A webhook is an HTTP callback that sends a notification to a specified URL whenever a specific event occurs. In the case of Contentstack, the event could be when content is created, updated, deleted, or published.Developers can create webhooks in Contentstack and specify which events should trigger them. When an event occurs, Contentstack sends an HTTP POST request to the specified URL, containing information about the event and the associated content.With this information, developers can automate processes such as updating search indexes, notifying team members of content changes, or triggering other third-party services. Additionally, Contentstack allows developers to set up conditional logic to filter webhooks based on specific criteria, such as content types, allowing for even more granular control over webhook behavior.<h2>Exercise: Using a webhook to call an endpoint on the webhook.site service</h2>Step 1: Go to <a href="https://webhook.site">webhook.site</a> in your web browser.Step 2: Click on the "Create a webhook" button on the top right corner of the webpage.Step 3: In the "Create a new webhook" modal, you'll see a unique webhook URL that you can use to send HTTP requests. Copy this URL to your clipboard.Step 4: Log in to your Contentstack account and go to the Settings section of your stack.Step 5: Click on the "Webhooks" tab.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576479/original/dbe7d899-ba53-49f0-9a17-e7d053afe841-Screen_Shot_2023-05-03_at_10.24.36_AM.png" width="100"/>
 Step 6: Click on the "Add New Webhook" button.Step 7: In the "Create Webhook" modal, enter a name for your webhook, such as "Webhook.site Test".
 Step 8: In the "URL" field, paste the webhook URL that you copied from webhook.site in step 3.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576480/original/514bd36e-5cf5-4138-88ab-8abfa45ce57c-Screen_Shot_2023-05-03_at_10.26.32_AM.png" width="100"/>Step 9: Under "Webhook Triggers", select "Publish" as the trigger event.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576481/original/8a3fd73e-021d-4b68-b822-830a0549e0e5-Screen_Shot_2023-05-03_at_10.26.49_AM.png" width="100"/>Step 10: Click on the "Save" button to save the webhook.Step 11: Now, whenever you publish content in Contentstack, a webhook notification will be sent to the URL you specified in step 8.Step 12: To test the webhook, publish a new piece of content in Contentstack.Step 13: Return to webhook.site and click on the "Inspect" button next to the webhook that you just created. You should see the webhook notification data from Contentstack, including the published content.Congratulations! You have successfully tested a Contentstack webhook using webhook.site. You can now use webhook.site to test your webhook implementations or receive webhook notifications from other services.<h2>Learn More</h2><ul><li><a href="https://www.contentstack.com/docs/developers/set-up-webhooks/">Webhooks Documentation Page</a></li><li><a href="https://community.contentstack.com/search?q=webhooks">Community Forum</a></li></ul>

Webhooks

<h2>Sending HTTP Messages with Automate</h2>
An&nbsp;<a href="https://www.contentstack.com/docs/developers/automation-hub-connectors/http-action/">HTTP Action</a>&nbsp;allows us to send an HTTP call when a trigger event occurs. This enables us to send JSON from an&nbsp;entry, asset, or release&nbsp;to any service that accepts an HTTP POST, GET, PUT, DELETE, or PATCH. In this module we will use an&nbsp;HTTP Action connector&nbsp;to send the&nbsp;entry&nbsp;JSON to an external webhook listener. This method can be used to integrate with third-party systems that do not&nbsp;have a pre-built connector but can receive a GET or POST request.
Topics covered:
<ul>
 <li>
 Sending JSON to an external web service
 </li>
 <li>
 Using the website&nbsp;<a href="http://webhook.site/">http://webhook.site</a>&nbsp;to receive to our HTTP message
 </li>
</ul>
Please watch the following video to see an example of sending an HTTP message with&nbsp;automate:

<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/jmJmjKiy-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-course Automation Hub, Connect To 3rd Party Webservice" style="position: absolute;" allowfullscreen=""></iframe></div>

<h3>Exercise:&nbsp;Create a new Automation that sends an HTTP Post request to a 3rd party web service when an entry&nbsp;is published</h3>
1. Create a new Automation using a Contentstack Trigger 2. Add a new action&nbsp;and use the HTTP Connector&nbsp; 3. Go to http://webhook.site and create a new webhook listener 4. In the Configure Action step, specify the URL of the webhook from above

Automate- Using an HTTP Connector to Send Data to a 3rd Party System

The <a href="https://www.contentstack.com/docs/developers/marketplace-platform-guides/">Contentstack Marketplace</a> is a platform for apps and other resources that help you extend the capabilities of our core CMS and customize its functionalities. It is a one-stop resource to discover, browse, and install tools to enhance the Contentstack experience by connecting to various third-party services in a simple installation. The <a href="https://www.contentstack.com/docs/developers/marketplace-apps/">apps</a> and resources on Marketplace are created by Contentstack and our partners.&nbsp;<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576487/original/6f4bd6cd-9710-4c45-9dd9-fc5e58005c97-LinkedIn_Screen_Grabs_for_LearnUpon_(1).jpg" width="100"/>Contentstack Marketplace is Contentstack’s very own app distribution platform similar to the App Store in Apple, or the Play Store in Android. You can use and install apps from our Marketplace to extend the existing capabilities of your Contentstack web application.Marketplace Apps allow you to extend the capability of our core CMS and customize its functionalities. With these ready-to-use apps, you can integrate your favorite third-party platforms easily and with minimal effort. These pre-built apps are intended to be quickly and easily installed. Apps like this are built to solve a particular problem, help integrate with a specific software, or provide functionality for a user of Contentstack.

What is Contentstack Marketplace?

Contentstack’s App Marketplace for Extensions is a platform where users can find and install pre-built extensions that can enhance the functionality of their Contentstack projects. These extensions are developed by Contentstack partners or third-party developers and are designed to simplify and streamline common development tasks, such as integrating with external systems, automating workflows, and adding new features to the CMS.Here are the key features of Contentstack’s App Marketplace for Extensions:1. Extension Types: The App Marketplace offers a variety of extensions types, including field types, custom widgets, and integrations. Each extension type has a specific purpose and can be used to enhance the functionality of the CMS in different ways. &nbsp;This includes Dashboard widgets, full-page apps, custom fields, sidebar widgets, rich-text field extensions and a new field modifier.2. Categories: The App Marketplace offers extensions across multiple categories, including SEO, localization, analytics, integrations, and more. These categories make it easy for users to find extensions that fit their specific needs.3. <a href="https://www.contentstack.com/docs/developers/developer-hub/get-started-with-building-apps-using-contentstack-app-sdk/">Developer Documentation</a>: Each extension in the App Marketplace comes with detailed documentation, which provides instructions on how to install, configure, and use the extension.4. &nbsp;The Developer Hub allows developers to upload their extensions to Contentstack and test them out. Additionally, developers can create private extensions for their customers and leverage the Developer Hub to make them accessible.5. Submit Your Own Extension: Developers can submit their own extensions to the App Marketplace. Contentstack reviews each extension to ensure that it meets quality standards before making it available in the marketplace. &nbsp;Using the Developer Hub you can createOverall, Contentstack’s App Marketplace for Extensions provides a centralized location for users to find and install extensions that can enhance the functionality of their Contentstack projects. With a wide range of extensions available across multiple categories, users can customize their CMS to fit their specific needs and streamline their workflows.<h2>Exercise:&nbsp;Installing and Using Apps from the Marketplace</h2>In this module we are going to install two apps from the Marketplace that support developers using Contentstack.1.&nbsp; Developer Tools2.&nbsp; Content Type Visualizer<h2>Installing Developer Tools</h2>Developer tools allow the developer to view the Entry JSON before it is published.&nbsp; This is very helpful when building apps and looking for the structure and properties of the content type.1.&nbsp; Go to the <a href="https://app.contentstack.com/#!/marketplace/apps">Marketplace dashboard</a>&nbsp; (<a href="https://eu-app.contentstack.com/#!/marketplace/apps">EU Marketplace Dashboard</a>)2.&nbsp; Select&nbsp;Developer Tools, Install App, and choose the Stack of where to install it <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576446/original/bdc0e3af-7d8b-4c59-a74d-f3a51d7da1c3-Screen_Shot_2023-05-01_at_6.07.28_PM.png" width="100"/> <h2>Installing the Content Type Visualizer</h2>The Content Type Visualizer is another developer-friendly extension that shows the relationships between Content Types.&nbsp; It is installed on the Dashboard using the Marketplace.1.&nbsp; Go to the <a href="https://app.contentstack.com/#!/marketplace/apps">Marketplace dashboard</a>&nbsp; (<a href="https://eu-app.contentstack.com/#!/marketplace/apps">EU Marketplace Dashboard</a>)2.&nbsp; Select&nbsp;Content Type Visualizer, Install App, and choose the Stack of where to install it <img src="https://learnupon.s3.eu-west-1.amazonaws.com/576447/original/f814d925-6238-49a4-9907-8793ab8c4b58-Screen_Shot_2023-05-01_at_6.10.14_PM.png" width="100"/><div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/TZemBvJ6-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-marketplace App Install Dev Tools And Content Type Visualizer" style="position: absolute;" allowfullscreen=""></iframe></div>

Using Marketplace Apps

Installing and Configuring the NextJS Starter App&nbsp;About Starter Apps In Contentstack, starter apps are pre-built applications that demonstrate the capabilities of Contentstack&nbsp;and provide a starting point for developers learning about and building web applications.Starter apps are designed to be fully functional, customizable, and extensible, providing developers with a set of best practices and common patterns for building web applications that consume content from Contentstack.Starter apps in Contentstack are available for a variety of programming languages and frameworks, including NextJS, React, Angular, and Vue.js. Each starter app includes a set of pre-built content types, entries, assets, and environments.Using starter apps in Contentstack provides several benefits, including:<ul><li>Rapid prototyping: Starter apps provide a quick way to prototype and test new ideas, allowing developers to create a fully functional application in a fraction of the time it would take to build from scratch. &nbsp;</li><li>Best practices: Starter apps are built using best practices and industry-standard patterns, providing developers with a solid foundation for building scalable, maintainable, and high-performing applications.</li><li>Customization: Starter apps can be fully customized to meet the specific needs of the application being developed, including branding, layout, functionality, and integrations with other systems.</li><li>Extensibility: Starter apps can be extended and allowing developers to add new features and functionality as needed.</li></ul>Overall, starter apps in Contentstack provide a powerful and flexible way for developers to jumpstart their projects, reduce development time and costs, and ensure high-quality, scalable, and maintainable applications.<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576412/original/d7095172-d3e3-4174-8502-19dcc4086a7c-Screen_Shot_2023-04-28_at_9.11.59_AM.png" width="100"/><h2>Three ways to get started with the StarterApps</h2>When starting to develop with Contentstack, we can install and use an existing NextJS Starter App called Logoipsum and this can be set up in several ways: &nbsp;1.&nbsp; The first approach involves using an <a href="https://www.contentstack.com/docs/developers/cli/bootstrap-starter-apps/">automated bootstrap CLI script</a> to generate a new Stack or load content into an existing Stack. This method includes all the default content and downloads the NextJS app. We will be using this option for the course.2.&nbsp; The second approach involves installing a Starter App via the Marketplace. This method is useful when you want to try using Contentstack as an Author or Editor and publish content without accessing the frontend code. However, we will not be using this approach in the course.3.&nbsp; <a href="https://www.contentstack.com/docs/developers/sample-apps/build-a-starter-website-using-next-js-and-contentstack/#import-content">Manually import the content with the CLI</a> and download the <a href="https://github.com/contentstack/contentstack-nextjs-starter-app">StarterApp from the Github repo</a> and manually configure the application.&nbsp; This does the same thing as step 1, but requires more time.<h2>Install the Starter App</h2><h3>Create the Stack</h3>To get started we will need to create a new Stack in Contentstack for our NextJS Starter app. &nbsp;To create our Starter App using the Contentstack CMS, we need to follow a few steps. Firstly, we need to create a new Stack and then use a CLI command to import the Starter app content and code. It is crucial to ensure that you have an Empty Stack ready for the StarterApp before proceeding. If you have the role of Organization Owner in Contentstack, then the CLI can create the Stack for you automatically using your login credentials.Watch the following video to explain how to install the StarterApp with the CLI<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/IbfbzKwm-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-create A New Nextjs Starter App Via Cli" style="position: absolute;" allowfullscreen=""></iframe></div><h2>What’s inside the Starter App</h2> The Starter app Stack contains all the Content Types, Entries, Assets, Environments, Tokens, and Roles for a full website. &nbsp;The following video will explain the Starter app and where everything is located:<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/ZZQuG80V-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-starter App Content Types Walkthrough & Token Explanation Ui Code Nextjs App" style="position: absolute;" allowfullscreen=""></iframe></div><h1>Architecture</h1><h2>Big Picture Architecture Diagram</h2><h3>Backend</h3>The Backend of Contentstack is the CMS with the ability to create and publish content.&nbsp; The focus here is on editor ease-of-use by providing a simple, powerful and flexible UI for content creation and management.&nbsp; In addition to the out of the box functionality, we also provide an ability to extend the interface by creating UI Extensions using our App SDK and connect to 3rd-party applications such as DAM providers, Analytics, E-Commerce platforms and more.<h3> </h3><h3>Frontend</h3>The focus on the frontend is high-performance for your website and web application. APIs and SDKs are provided to the developer for using in their applications to perform read-only queries to the content.&nbsp; The Content Delivery APIs use an internal CDN to cache all queries to the platform which results in higher performance for all your web applications.&nbsp; This is also where we find the Images API for delivering image assets.Watch this video that explains the big picture architecture:<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/gu1hi4sL-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-big Picture Architecture" style="position: absolute;" allowfullscreen=""></iframe></div><img src="https://learnupon.s3.eu-west-1.amazonaws.com/576413/original/28c85d0f-f6ed-4644-bde9-f947fc9c37ac-Big-picture_Contentstack_Architecture_Diagram_2x-generic.png" width="100"/><h2> </h2><h2>Environments</h2><ul><li>One Stack can publish to multiple Environments. &nbsp;Think of Environments as “publish destinations”.</li><li>Each Environment has one Delivery Token, otherwise known as an Access Token. &nbsp;That token is unique per Environment.</li><li>Each Stack has an API key. &nbsp;There is only 1 API key per Stack and it is unique.</li><li>Most API calls will require both an API token and a Delivery / Access Token. </li></ul>Watch this video to understand how we use Environments in Contentstack:<div style="position: relative;overflow: hidden;padding-bottom: 56.25%;"><iframe src="https://cdn.jwplayer.com/players/xDslMX1l-b769H14u.html" width="100%" height="100%" frameborder="0" scrolling="auto" title="Dev-environments" style="position: absolute;" allowfullscreen=""></iframe></div>The following diagram for Environments illustrates these concepts:<img src="https://learnupon.s3.eu-west-1.amazonaws.com/576414/original/af295889-db78-4a87-aa40-5e077862b3ad-Environments_2x.png" width="100"/>
 
 <h2><h3>Multi-Stack Architecture Diagram
 </h3><img src="https://lh5.googleusercontent.com/bIvhDECh5mzOrfGNMxSTy-k4EFx7yRO3U5Z5MkFAQ3neVQ1yUP3i15JA-UP88Br9YT5jNUX6BfkST6uZ-nuBlw76G9zULLu-0_u-fVAvdCtQXyJy6UJWX4Govx_fXLXHKSIQvgJgAWMtY-PrKSLtFWY" width="100"/></h2>

Installing the NextJS Starter App with the CLI

<h1></h1><ul><li><a href="http://community.contentstack.com">Contentstack Community</a></li><li><a href="https://www.contentstack.com/docs/developers/">Developer Documentation Portal</a></li></ul><h2>Helpful Documentation Links</h2><h3>APIs</h3><ul><li><a href="https://www.contentstack.com/docs/developers/apis/">APIs Homepage</a></li><li><a href="https://www.contentstack.com/docs/developers/apis/postman-collections/">Postman Collections for APIs</a></li><li><a href="https://www.contentstack.com/docs/developers/cli/">CLI</a></li><li><a href="https://www.contentstack.com/docs/developers/sdks/utils-sdk/javascript/get-started-with-javascript-utils-library/">JavaScript RTE&nbsp;Parsing Utils</a></li><li><a href="https://github.com/contentstack/json-rte-serializer/">JSON RTE Serializer - Github</a></li></ul><h3>Sample Apps / Examples</h3><ul><li><a href="https://www.contentstack.com/docs/developers/sample-apps/">Sample Apps</a></li><li><a href="https://github.com/Contentstack-Solutions/contentstack-nextjs-typescript-base/blob/main/lib/services/contentstack-service.ts">Contentstack Typescript Query / API Service</a></li><li><a href="https://github.com/Contentstack-Solutions/contentstack-nextjs-typescript-base/blob/main/lib/services/contentstack-service.ts">https://github.com/Contentstack-Solutions/contentstack-nextjs-typescript-base/blob/main/lib/services/contentstack-service.ts</a></li><li><a href="https://github.com/Contentstack-Solutions">Contentstack Solutions Github Repo</a></li></ul><h3>Live Preview</h3><ul><li><a href="https://www.contentstack.com/docs/content-managers/author-content/live-preview-real-world-scenarios/">Live Preview Real-world scenarios</a></li><li><a href="https://www.contentstack.com/docs/developers/set-up-live-preview/how-live-preview-works-with-sdk/">How Live Preview Works with the SDK</a></li><li><a href="https://www.contentstack.com/docs/developers/set-up-live-preview/">Set up Live Preview&nbsp;</a></li></ul><ul></ul>

Helpful Resources

The Contentstack Developer Onboarding Course is designed to equip learners with comprehensive knowledge on various aspects of the platform, including its architecture, APIs, SDKs, and the process of creating a NextJS web application.&nbsp; <a href="https://github.com/contentstack/contentstack-academy-playground" target="_blank">Download Playground Here</a>You can also install a training instance by visiting our Legacy Academy. Click the <a href="https://www.contentstack.com/academy-old" target="_blank">Create Training Instance</a> button on the home page.Throughout the course, learners will receive detailed instruction on how to utilize Contentstack's features to build robust and scalable web applications. They will gain a deep understanding of the platform's architecture, enabling them to develop applications that take full advantage of Contentstack's capabilities.&nbsp;Additionally, the course will provide learners with hands-on experience using Contentstack's APIs and SDKs, enabling them to develop efficient and effective web applications. By the end of the course, learners will be equipped with the skills and knowledge necessary to create high-quality web applications using Contentstack.

The Contentstack Developer Onboarding Course is designed to equip learners with comprehensive knowledge on various aspects of the platform, including its architecture, APIs, SDKs, and the process of creating a NextJS web application. 

Contentstack for Developers

cs-for-devs2.png

This quick video reviews how environments work in Contentstack

Understanding Environments

environments-thumbnail.png

Master environments in Contentstack Academy to streamline your content management and ensure smooth transitions from development to production.

<h3>Personalize </h3> At Contentstack we believe Composable Digital Experience Platforms should be easier. Headless should be powerful AND intuitive. Products should be built to be connected. When it comes to personalization with other platforms, adoption is typically difficult, editing is confusing, and implementations are complex.&nbsp;But here at Contentstack we want you to be able to tell the right story to the right people, at the right time. Introducing Contentstack Personalize.

Personalize Demo

This short video will demonstrate the capabilities of Personalize.

Contentstack Personalize

Personalize.svg

Get a tailored experience with our personalized demo and discover how Contentstack can meet your unique needs and streamline your content management.

Understanding Taxonomy

Understand the Taxonomy feature in the Contentstack CMS.

Understanding Taxonomy in Contentstack

understanding-taxonomy.png

Master content organization with our guide on understanding taxonomy in Contentstack Academy; optimize your content structure and enhance efficiency.

Search 2.0

This video describes the search capabilities within the Contentstack CMS

Learn how to search in Contentstack

search.png

Using Search

Master the art of searching with Contentstack Academy's guide and learn to efficiently find and filter content with advanced search techniques.

<h2>AI Accelerator </h2>We’re excited to help you discover the power of Generative AI and integrate it strategically within your Contentstack workflows. Watch this video to learn more about our AI Accelerator program!

Explore