Glossary

This reference document defines key terms and core concepts across the Contentstack CMS, including structured content, content modeling, publishing workflows, developer tools, and personalization features—serving as a clear reference for content managers, developers, and marketers.

• Stacks: Centralized repository that holds all the content (entries and assets) related to your project. They also serve as a collaboration space where multiple users can work together to create, edit, approve, and publish content.
• Content types: Structure or blueprint of a page or a section of your web or mobile property. They consist of fields which are the building blocks for structured content.
• Entries: Actual pieces of content that you want to publish.
• Assets: Files stored in the system, such as images, videos, PDFs, audio files, and so on.
• Environments: One or more deployment servers or content delivery destinations (web page URLs) where the entries need to be published.
• Trash: Temporary storage area for deleted content types, global fields, entries, and assets, allowing users to review and restore them within the stack.

• Fields: Building blocks for structured content.
• Reference: Field that allows you to create references to entries of the same or other content types.
• Modular block: Field that allows users to dynamically create and modify components of a page or app on the go.
  • Developers first need to add this field while creating a content type and define blocks like “Banner”, “Product Details”, or “Video”.
  • Content managers can choose from these blocks while creating entries.
  • For flexibility, you can nest Modular blocks within Global fields.
• Global field: Reusable field/group of fields you can use across content types. You can also nest Global Fields within Modular Blocks.
• Taxonomy: Categorize content to ease navigation, search, and retrieval.
• Branches: Create stack copies to use as independent workspaces.

• Roles: Permissions assigned to users through an organization role and one or more stack roles. Users can be assigned stack roles when added to an organization or as existing members. Predefined roles include:
  • Organization roles: Organization Owner, Admin, and Member
  • Stack roles: Stack Owner, Developer, Content Manager, and Custom Roles
• Audit Log: Records all activities performed in the stack, including content updates, user logins, publishing events, and administrative actions, helping maintain accountability and security.

• Publish Content: Push entries or assets to target environments.
• Preview Content: Preview entries before publishing, or by creating a preview environment.
• Versions: Track changes with entry versions and asset versions.
• Localization: Adapt content across multiple languages and regions.
• Releases: Bundle entries/assets and deploy together.
• Workflows: Define stages, with workflow stages.
• Automate: Visual tool to automate workflows with trigger-action configurations.
• Timeline: Visualize scheduled updates.
• Live Preview: Real-time editing preview across channels.
• Publish Rules: Control publishing based on approval conditions or workflow stage.

• Command Line Interface (CLI): Perform content ops via terminal scripting.
• SCIM API: Automates user provisioning with SCIM standard.
• Synchronization API: Sync content across systems/environments.
• Content Delivery API: Fetches published content.
• Content Management API: Manage content types, entries, and assets.
• GraphQL Content Delivery API: Fetch customizable content via GraphQL.
• Image Delivery API: Retrieve/manipulate images.
• Webhook: HTTP callback for real-time integration triggers.
• Tokens: Secure, encoded strings used to authorize API requests in Contentstack. Types include:
  • Delivery Token: Grants read-only access to published content via the Content Delivery API (CDA); scoped to specific environments.
  • Preview Token: Grants access to unpublished content for live previews through the website’s preview panel.
  • Authtoken: User-specific token obtained upon login, enabling authenticated operations via the Content Management API (CMA).
  • Management Token: Stack-level token with customizable scopes, used for secure, automated read-write or read-only access via the CMA.

• Personalize: Define and deliver tailored user experiences using variants and audience segmentation.
• Variants: Entry versions tailored to different user groups or for A/B testing.

• Launch: Deploy front-end websites built on Contentstack.
• Marketplace: Browse apps/extensions to extend CMS functionality.
• Brand Kit: Manage branding, style guides, and voice.
• Visual Builder: Drag-and-drop interface for visual content editing.
• Analytics: Centralized CMS usage and performance insights.

Note: Experience Extensions use a legacy method. Prefer UI locations to build and extend Contentstack apps.