Get things done in Contentstack
This guide serves as a handbook for getting things done in Contentstack. If you are new to Contentstack, this is the best place to start. It covers documentation on every component of this CMS platform, including creating, managing and publishing content. Browse through the topics and get to know Contentstack well.
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 a like a container that holds the content of your project. This is your starting point. Start by creating a new stack in your account.
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.
Content in Contentstack means entries and assets. Entries refer to the individual pieces of content, while assets are media files such as images, audio, videos, and documents. Once the initial setup is done, you will be mainly managing these two items.
An environment is a deployment server or a content delivery destination where the content needs to be published. You need to set this up before you publish content.
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.
You can add users to your stack to collaborate with them. Assign permissions and define who gets to do what in your stack.
Send real-time data to external apps and integrate with them using webhooks. This is the best tool to keep your other apps in sync with your Contentstack data.
Add an extra layer of security to your Contentstack account by enabling two-factor authentication. It uses a combination of two different verification methods.
Workflow lets you streamline your project’s content generation and publishing lifecycle. It lets you define the workflow stages through which the content needs to travel, and publish rules which are like conditions for publishing.
Instead of publishing entries or assets one by one during an announcement or product update, you can put them all into a release and deploy this release on the requirement. It’s like publishing/unpublishing entries and assets in bulk.