Contentstack is a CMS backend for your digital properties
Contentstack is a content management system, but a headless one. It provides the infrastructure to create and manage content, but it is not coupled to any single presentation layer, such as websites (which is commonly the case with today’s CMSs).
It is headless, which means it can serve content in a presentation-independent way. It provides REST APIs to deliver content to any channel such as websites, mobile apps, devices, marketing kiosks or any digital platform that displays content.
Managing content in Contentstack is easy and does not involve any coding. It’s a simple 3-step process.
Step 1 - Model your content: Define the structure of your content in a platform-independent way. This involves creating a content type and adding relevant fields such as ‘single-line textbox’, ‘date’, ‘file’. Adding fields is a simple drag-and-drop process
Step 2 - Create content: Once the required content types are ready, any user can add content, which is like filling up a form. Multiple users can work together in teams to create important content in multiple languages.
Step 3 - Publish content: The content, once created, can be published to your website, mobile app, or any other channel. The same content can be reused for any platform.
Like any other application, Contentstack has its own set of terminologies. Understanding these concepts make it easier for you to work with.
Organization acts as a parent entity that encapsulates stacks (and all the resources stored within), belonging to the same company or group making project management unbelievably easy.
A stack is like a container that holds the content of your project. It lets you organize content by grouping related content together.
Content type lets you define the structure or blueprint of a page or a section of your digital property. It helps you lay the foundation of your content.
An entry is the actual piece of content created using one of the defined content types. To create an entry, content managers simply fill data in the fields of a content type.
Assets refer to all the media files (images, videos, PDFs, audio files, and so on) uploaded to Contentstack. These files can be used in multiple entries.
A publishing environment corresponds to one or more deployment servers or a content delivery destination where the entries need to be published.
Contentstack offers multi-language support, which allows you to create entries in any language of your choice. Localization is the process of making an entry available in another language.