# Core Contentstack Concepts - **Authors:** Tim Benniks - **Published:** 2026-04-07T09:46:57.497Z - **Updated:** 2026-04-07T10:34:22.007Z --- Before you seed a stack or open the Veda repo, you need a reliable vocabulary. Contentstack becomes much easier once you know which objects exist, what they are responsible for, and which API is supposed to touch them. ## What you'll learn - The meaning of stack, content type, entry, asset, environment, and locale - The difference between Delivery API, Preview API, and Management API - How references and modular blocks shape real content models - Where beginners usually get confused - Which concepts are portable across projects and which ones are Veda-specific ## The object model you should keep in your head ### Stack Contentstack concept: A stack is the top-level container for your project inside Contentstack. A stack contains things like: - content types - entries - assets - environments - tokens - Live Preview configuration If you are coming from databases, you can think of a stack as the broad project boundary. If you are coming from GitHub, think "repository plus configuration plus data," not just a single file tree. ### Content types Contentstack concept: A content type is the schema for a kind of content. Examples: - page - product - category - header A content type defines fields such as title, description, URL, references, media, modular blocks, and validation rules. This is one of the most important shifts in Contentstack. You do not start by designing pages. You start by designing content shapes. ### Entries Contentstack concept: An entry is one actual item of content that follows a content type. If product is the content type, one ring or necklace is an entry. If page is the content type, your homepage is one entry and your about page is another. ### Assets Contentstack concept: Assets are files stored in Contentstack, such as images, videos, and documents. They are delivered over Contentstack's CDN and can be referenced from entries. In a project like Veda, many visual experiences depend on asset URLs being part of the structured content rather than hardcoded in the frontend. ### Environments Contentstack concept: Environments represent stages of content delivery such as development, staging, or production. The important thing to remember is that environments matter for published delivery. An editor can save drafts at any time, but publication targets an environment. ### Locales Contentstack concept: Locales represent language or regional variants such as en-us or fr-fr. You do not need multiple locales to learn Veda, but once you understand Contentstack well, locales become part of how the same content model can serve multiple audiences. ## The three API modes that matter This is where many first-time users get tripped up. ### Delivery API Contentstack concept: The Delivery API is for reading published content. Use it when: - your public site is rendering live content - you want stable, cacheable responses - you are reading from a specific environment ### Preview API Contentstack concept: The Preview API is for reading draft or unpublished content during preview workflows. Use it when: - editors need to see draft changes - Live Preview is active - your app needs to reflect unpublished changes safely ### Management API Contentstack concept: The Management API is for creating, updating, deleting, and publishing content. Use it when: - you are writing automation scripts - building import/export tools - handling server-side content administration workflows Production note: Never expose Management API credentials in a frontend application. Delivery and preview flows are one thing. Administrative write access is another. ## References: how entries connect to each other Contentstack concept: References let one entry link to another entry. This is how a project stops feeling like isolated pages and starts feeling like a content system. For example, a product line might reference products. A header entry might reference navigation structures. A page might reference blocks, assets, or related content. In Veda, references are part of what makes the project more realistic. Instead of fetching one flat page payload, the app often pulls connected content with deeper include settings because the site is modeling real relationships. ## Modular blocks: how editors compose pages without hardcoding layouts Contentstack concept: Modular blocks let editors assemble a page from reusable content sections. Examples from Veda include: - hero - list - two column - media - rich text This is a major strength of Contentstack when used well. Developers define the available block types and how they render. Editors decide which blocks to use and in what order. That gives you a clean contract: - developers own the rendering components - editors own page composition within those allowed patterns ## Where beginners usually get confused ### Confusion 1: "Entry" versus "page" Not every entry is a page. Some entries are pages, some are products, some are navigation data, and some are reusable supporting content. ### Confusion 2: "Preview" versus "published" Preview is not just "the same content but earlier." It is a different delivery mode with different credentials and different expectations. ### Confusion 3: "Content type" versus "component" A React component is not a content type. A modular block definition inside Contentstack is also not the same thing as a frontend component, even though the two are related. The content model decides what data is available. The frontend decides how that data is rendered. ### Confusion 4: "Environment" versus "region" An environment is a content lifecycle stage inside a stack. A region is the physical or cloud location where your stack and endpoints live. Those are separate concerns. ## What is portable beyond Veda Contentstack concept: Everything in this chapter is portable. The details of Veda will change: - content type names - component names - route patterns - visual style But the core model stays the same: - stacks contain schemas and content - content types define structure - entries hold actual content - assets hold files - environments and locales shape delivery - references and modular blocks enable richer composition - different APIs exist for different jobs ## Key takeaways - Contentstack works best when you think in structured content, not only pages - A stack is the project boundary; content types define structure; entries hold data - Delivery, Preview, and Management APIs serve different jobs and should not be mixed casually - References connect content types into a system - Modular blocks are the bridge between editorial flexibility and developer-controlled rendering --- ## Frequently asked questions ### What is a stack in Contentstack? A stack is the top-level container for a project in Contentstack. It holds content types, entries, assets, environments, tokens, and related configuration. ### What is the difference between a content type and an entry? A content type is the schema (field structure and validation) for a kind of content. An entry is one instance of content that follows that schema. ### When should I use the Delivery API vs the Preview API? Use the Delivery API to read published content from a specific environment with stable, cacheable responses. Use the Preview API to read draft or unpublished content for preview workflows such as Live Preview. ### What is the Management API used for in Contentstack? The Management API is used to create, update, delete, and publish content. It is intended for automation and administrative workflows and should not be exposed in frontend apps. ### How do references and modular blocks affect content modeling? References connect entries to other entries to model relationships. Modular blocks let editors compose pages from predefined, reusable section types while developers control how each block renders. --- ## Chapter Navigation **← Previous:** [What Contentstack is and why Veda is a good starting point](https://developers.contentstack.com/guides/contentstack-0-to-100-for-developers/what-contentstack-is-and-why-veda-is-a-good-starting-point) **Next →:** [Account, Region, CLI, and Stack Setup](https://developers.contentstack.com/guides/contentstack-0-to-100-for-developers/account-region-cli-and-stack-setup)