# CMS Developer Orientation ### About this export | Field | Value | | --- | --- | | **content_type** | course | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/cms-developer-orientation | | **language** | en | | **product_area** | Contentstack Academy | | **learning_path** | cms-developer-certification | | **course_id** | cms-developer-orientation | | **slug** | cms-developer-orientation | | **version** | 2026-07-31 | | **last_updated** | 2026-08-03 | | **status** | published | | **keywords** | ["Contentstack Academy"] | | **summary_one_line** | Orientation Start the certification with clear expectations, the right resources, and a first successful interaction with Contentstack. Who This Course Is For Take this course if you are new to the certification, new to … | | **total_duration_minutes** | 24 | | **lessons_count** | 5 | | **video_lessons_count** | 0 | | **text_lessons_count** | 5 | | **linked_learning_path** | cms-developer-certification | | **linked_assessment_ref** | LMS_UNCONFIGURED_COURSE_ASSESSMENT | | **markdown_file_url** | /academy/md/courses/cms-developer-orientation.md | | **generated_at** | 2026-08-03T11:49:36.483Z | | **intended_audience** | [] | | **prerequisites** | [] | | **related_courses** | [] | > **Academy MD v3** — companion `.md` for Ask AI. Quizzes and graded assessments are **LMS-only**; this file never contains answer keys. ## Course Overview | Metadata | Value | | --- | --- | | Catalog duration | 23m 30s | | Released (if known) | 2026-07-31 | | Product area | Contentstack Academy | ### Description # Orientation Start the certification with clear expectations, the right resources, and a first successful interaction with Contentstack. ## Who This Course Is For Take this course if you are new to the certification, new to Contentstack, or want a faster path into the rest of the curriculum. ## You Will Be Able To * explain how the certification is structured and how to study it effectively * find the Contentstack docs, API references, SDKs, and support resources you will use repeatedly * complete an initial stack and API walkthrough before the deeper conceptual courses ## Recommended Preparation Have a Contentstack account ready or create a free developer stack before you begin the quickstart lesson. ## Estimated Effort 30 minutes ## Build Thread You will begin the Veda storefront journey by opening a stack, identifying the core objects, and making your first delivery request. ## Suggested Next Step Start with [Certification scope and how to use this curriculum](/course-0-orientation/module-0-1-what-this-certification-covers/01-certification-scope). ### Learning objectives 1. Follow each lesson in order. 2. Practice in a training stack using placeholders **YOUR_STACK_API_KEY** and **YOUR_DELIVERY_TOKEN** in local `.env` files only. 3. Validate API responses against the official documentation. ### Topics covered Contentstack Academy ## Course structure ```text cms-developer-orientation/ ├── 01-what-this-certification-covers-overview · text · 1 min ├── 02-certification-scope-and-how-to-use-this-curriculum · text · 1 min ├── 03-navigating-contentstack-docs-apis-and-resources · text · 1 min ├── 04-getting-started-with-the-veda-kickstart · text · 1 min ├── 05-your-first-contentstack-build-inspect-content-and-make-an-api-call · text · 1 min ``` ## Lessons ### Lesson 01 — What This Certification Covers : Overview #### Lesson text # What This Certification Covers This module helps you start quickly: understand the certification, find the right resources, and complete your first Contentstack workflow. ## Why This Module Matters Developers are more likely to stay engaged when they know what they are building, what tools they need, and how to get an early win. This module provides that starting point. ## You Will Be Able To * explain the scope and expectations of the certification * find the docs, APIs, SDKs, and support channels you will rely on later * complete a first stack and delivery walkthrough before CMS Developer Foundations ## Recommended Preparation Sign in to Contentstack and keep a stack available while you work through the lessons. ## Estimated Effort 30-45 minutes ## Practice Focus Use the Veda scenario to inspect real content, locate the right documentation, and make a first API call with confidence. ## Suggested Next Step Start with lesson 1 in this module and complete all three lessons before moving to Foundations. #### Key takeaways - Connect **What This Certification Covers : Overview** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ### Lesson 02 — Certification scope and how to use this curriculum #### Lesson text # Certification scope and how to use this curriculum > TL;DR > > * This certification covers seven courses spanning content modeling, APIs, preview architecture, workflows, extensions, and integrations > * Complete Course 1 first -- every later course builds on its vocabulary and mental models > * Keep a Contentstack stack open while you study; hands-on practice is where learning sticks > * Self-check questions test application, not memorization -- use them honestly Welcome to the Contentstack Developer Certification. This curriculum exists because building well on a headless CMS requires more than knowing where buttons live in a dashboard - it requires understanding content modeling trade-offs, API behavior under real conditions, preview architecture, workflow automation, and how extensions and integrations connect Contentstack to the broader technology ecosystem. Over seven courses, you will develop that understanding through explanation, concrete examples, and self-check questions that test whether you can apply what you have learned. This opening lesson lays out exactly what the certification covers, who it is designed for, what prior knowledge you should bring, and how the courses fit together. ## Why this matters Most developers abandon product learning paths when the material feels abstract or disconnected from real work. This certification is designed to help you understand Contentstack well enough to build with it, not just describe it. The faster you understand the platform and complete a first successful workflow, the easier it becomes to stay motivated through the more advanced architecture and implementation topics. ## You will be able to * explain who this certification is for and what it is designed to teach * identify the prerequisite skills and tools needed for the hands-on modules * choose an efficient path through the courses based on your role and goals * use the quickstart and recurring Veda scenario to keep later lessons grounded in real product work ## Who this certification is for This certification targets developers who build on top of Contentstack. That includes frontend developers consuming content through delivery APIs, fullstack developers wiring up preview environments and webhooks, and backend developers integrating Contentstack into larger platform architectures. If your day-to-day work involves fetching entries from the Content Delivery API, defining content types, configuring Live Preview, or building custom extensions, this curriculum is built for you. You do not need to be a Contentstack expert before you start. The courses are designed to take you from foundational concepts through advanced implementation patterns. However, you should arrive with a working knowledge of web development fundamentals: HTML, CSS, and JavaScript or TypeScript. You should be comfortable making HTTP requests, reading JSON responses, and working with REST APIs. If you have used fetch or axios to call an API endpoint, parsed the response, and rendered data in a frontend framework, you have enough technical background to succeed here. ## What this certification does NOT cover Scope boundaries matter. This certification focuses on the developer experience of building with Contentstack. It does **not** cover: * **Pricing and licensing** - We do not discuss plan tiers, usage limits, or billing structures. Refer to the Contentstack pricing page for that information. * **Sales and marketing features** - Topics like Contentstack's Personalize product, A/B testing configuration, or analytics dashboards fall outside the developer certification scope. * **Deep admin and operations tasks** - Organization-level settings, SSO/SAML configuration, user provisioning via SCIM, and compliance auditing are important but belong to a platform administration track rather than a developer certification. * **Framework-specific tutorials** - While examples may reference React, Next.js, or other frameworks, this is not a framework course. The emphasis is on Contentstack concepts and APIs that apply regardless of which frontend you choose. Keeping these boundaries clear means the curriculum stays focused on what developers actually need: the ability to model content, retrieve it efficiently, build editorial tooling, and integrate Contentstack into production systems. ## Expected prerequisites To get the most out of this certification, you should have: * **Basic web development skills** - You can build a simple web page, work with JavaScript/TypeScript, and understand client-server architecture. * **Familiarity with REST APIs** - You know what HTTP methods (GET, POST, PUT, DELETE) do, how request headers work, and how to interpret JSON responses. * **A code editor and terminal** - You will want to run code examples and make API calls during the hands-on exercises. * **Access to a Contentstack stack** - The certification assumes you can log into Contentstack and work with a stack. Contentstack offers a free developer plan at [https://www.contentstack.com/pricing](https://www.contentstack.com/pricing), which provides enough access to complete every exercise in this curriculum. If you do not have a stack yet, create one before starting Course 1. No prior Contentstack experience is required. Course 1 covers the foundational building blocks from the ground up. ## How the curriculum is structured The certification is organized into seven courses. They build on each other conceptually - Course 1 establishes vocabulary and mental models that every later course depends on - but after completing Course 1, you can study Courses 2 through 7 in any order that fits your needs. A developer focused on content modeling might move directly to Course 2, while someone tasked with setting up Live Preview could jump to Course 4 after finishing the foundations. Each lesson follows a consistent structure: an opening that frames the topic, core content that explains concepts and patterns, practical guidance with code examples or configuration walkthroughs, a short practice activity, and self-check questions at the end. **Use the self-check questions honestly.** They are not graded, but they reveal whether you actually understand the material or just skimmed it. If a question stumps you, re-read the lesson before moving on. The questions are designed to test application, not recall - they ask you to reason about scenarios, not memorize definitions. ## Use case: The Veda Revival Collection (eCommerce jewelry store) Veda is an upscale all gender jewelry line featuring four distinct sets inspired by early 2000s pop culture, each reinterpreted with modern, understated luxury. Every piece is crafted in combinations of silver, gold, and diamonds, blending youthful nostalgia with refined elegance. Designed to be worn by anyone (cis, trans, or nonbinary), these accessories celebrate the spirit of the 2000s in a contemporary, inclusive aesthetic. Veda is not just a one-time example in this certification. It is the recurring storefront scenario you will return to across the curriculum, so the same jewelry brand helps anchor each new concept in familiar product context. As you move through the courses, you will use Veda to connect content modeling, API delivery, preview, workflow, extensions, and integrations to real Contentstack implementation work. ![veda-homepage.png](https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/am30ebfcf40c0fc2ae/1032ef6e839bfc6de70ac732/veda-homepage.png?locale=en-us) ## Course overview Here is what each course covers, so you know the full landscape before diving in: ### Course 1: Foundations of Contentstack for developers Establishes the mental model for headless CMS architecture and introduces Contentstack's core building blocks: stacks, content types, entries, assets, and environments. You will learn how developer decisions directly shape the content editing experience and why the separation between content management and content delivery is an architectural choice with real consequences. ### Course 2: Content Modeling Takes you deep into designing content type schemas that serve both editorial usability and API consumption. Covers field types, modular blocks, references, global fields, taxonomies, and the trade-offs between flexible and structured modeling approaches. This is where you learn to build content architectures that do not break when requirements change. ### Course 3: Delivery and Management APIs Covers the full surface of Contentstack's API layer. You will work with the Content Delivery API (REST and GraphQL), the Content Management API, and understand authentication patterns, pagination, query operators, and response structures. This course teaches you to retrieve content efficiently and manage content programmatically. ### Course 4: Live Preview and Visual Builder Focuses on Contentstack's preview infrastructure and the Visual Builder for in-context editing. You will learn how Live Preview connects your frontend to draft content in real time, how Visual Builder enables drag-and-drop page composition, and how to configure both for production use with your chosen frontend framework. ### Course 5: Workflows, Publishing, and Branches Covers content governance: workflow stages, publishing rules, release management, and the branching model for content type development. You will understand how to design publishing pipelines that give editors autonomy while maintaining quality gates, and how branches let you iterate on content models without disrupting production. ### Course 6: Extensions and Customization Explores how to extend Contentstack beyond its built-in capabilities. Covers custom fields, custom widgets, dashboard widgets, and the App Framework (formerly called Extensions). You will learn when to build a custom extension versus using built-in features, and how to package and deploy extensions for your team. ### Course 7: Integrations and the Composable DXP Addresses how Contentstack fits into a larger technology ecosystem. Covers webhooks, automation (Automate), the CLI, and integration patterns with third-party services. You will learn how to connect Contentstack to your deployment pipeline, search infrastructure, DAM, commerce platform, and other services in a composable digital experience platform. ## How to approach this curriculum A few practical tips for getting the most out of your study time: 1. **Work through Course 1 first.** Every later course assumes you understand the vocabulary and architecture introduced in Course 1. Skipping it will leave gaps that compound. 2. **Keep a stack open while you study.** Reading about content types is useful; creating one and fetching entries from it through the API is where the learning sticks. Every concept in this curriculum maps to something you can do in a real Contentstack stack. 3. **Give the self-check questions real effort.** They are placed at the end of each lesson for a reason. If you cannot answer them confidently, the next lesson will be harder than it needs to be. 4. **Revisit lessons when you hit real-world problems.** This curriculum is designed as both a learning path and a reference. When you encounter a content modeling decision or an API integration challenge in your actual work, come back to the relevant lesson. The goal of this certification is not to test whether you can memorize Contentstack's feature list. It is to verify that you can make sound architectural and implementation decisions when building on the platform. Every lesson is written with that goal in mind. ## Practice in Contentstack Before you move on to Course 1, complete the quickstart lesson in this module and verify that you can: 1. identify a content type and a published entry in a real stack 2. locate the environment and delivery token needed for content delivery 3. run one successful API request and inspect the JSON response yourself That small exercise gives the rest of the certification a concrete anchor. > What you'll need > > This certification covers courses 1-7. Courses 1-2 are conceptual and require no coding. Starting from Course 3, you'll need comfort with TypeScript, Node.js, and at least one frontend framework (Next.js examples are used throughout). Course 4 assumes familiarity with React hooks and SSR/CSR patterns. ## Summary This certification is built to help developers make sound implementation decisions in Contentstack, not to memorize feature names. Start with the foundations, keep a stack open, complete the quickstart early, and use the recurring Veda scenario and self-checks to connect ideas to real product work. #### Key takeaways - Connect **Certification scope and how to use this curriculum** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ### Lesson 03 — Navigating Contentstack docs, APIs, and resources #### Lesson text # Navigating Contentstack docs, APIs, and resources > TL;DR > > * Bookmark the developer docs at contentstack.com/docs/developers/ -- you will return to it constantly > * API base URLs differ by data center region; using the wrong one causes silent "stack not found" errors > * When an SDK method behaves unexpectedly, check the raw API reference or the SDK source on GitHub > * Use the Contentstack CLI for migrations and bulk operations; use Postman collections for interactive API exploration Knowing where to find accurate, up-to-date information is as important as knowing the information itself. Contentstack maintains a large documentation ecosystem spanning product guides, API references, SDK documentation, sample applications, and community resources. This lesson gives you a practical map of that ecosystem so you can find answers quickly throughout this certification and in your production work. ## Why this matters Developers build faster when they can find the right reference before they start guessing. Knowing where Contentstack documents delivery APIs, SDKs, CLI flows, and support channels reduces friction across the rest of the certification. ## You will be able to * locate the main documentation and API references you will use most often * choose between guides, raw references, SDK docs, and source code when debugging * use docs and tooling resources to accelerate learning in the Veda scenario and beyond ## The main documentation site Your starting point for all Contentstack developer documentation is [https://www.contentstack.com/docs/developers/](https://www.contentstack.com/docs/developers/). This is the developer-focused section of the docs, distinct from the editorial and admin documentation. From here, you can navigate to guides on content modeling, API usage, SDKs, CLI tools, and platform features. The documentation is organized by topic rather than by user role, so you will find content type documentation alongside API references and SDK guides. Bookmark the developer docs landing page - you will return to it often. ## API reference documentation Contentstack exposes three primary API surfaces, each with its own reference documentation: ### Content Delivery API (REST) The [Content Delivery API reference](https://www.contentstack.com/docs/developers/apis/content-delivery-api/) documents every endpoint for retrieving published content. This is the API your frontend applications call in production. The reference covers endpoints for fetching entries, assets, content types, and synchronized content. Each endpoint includes the HTTP method, URL structure, required headers, query parameters, and example responses. When you read a Content Delivery API endpoint, pay attention to these elements: * **Base URL** - This varies by data center region (more on that below). * **Required headers** - Every request needs api\_key, access\_token (your delivery token), and environment. * **Query parameters** - Operators like $in, $nin, $gt, $lt, $regex, and $and/$or let you filter entries without downloading everything. The include\[\] parameter resolves referenced entries in a single request. * **Response structure** - Responses wrap entries in a standard envelope with metadata. Understanding this structure prevents confusion when you parse responses. ### Content Management API (REST) The [Content Management API reference](https://www.contentstack.com/docs/developers/apis/content-management-api/) documents endpoints for creating, updating, and deleting content programmatically. This is the API you use for automation, migrations, bulk operations, and backend integrations. It requires a management token or an authtoken with appropriate permissions. The management API is broader than the delivery API. It covers content types, entries, assets, environments, publishing rules, workflows, webhooks, global fields, taxonomies, roles, and more. When you need to script content operations - importing entries, updating schemas, managing publishing queues - this is the reference you will consult. ### GraphQL Content Delivery API The [GraphQL API reference](https://www.contentstack.com/docs/developers/apis/graphql-content-delivery-api/) documents Contentstack's GraphQL endpoint for content delivery. GraphQL lets you request exactly the fields you need in a single query, which can reduce payload size and eliminate over-fetching. The schema is auto-generated from your content types, so the available queries match your stack's content model. The GraphQL reference explains query syntax, filtering, pagination, and how references are resolved. If you are already familiar with GraphQL from other platforms, the Contentstack implementation will feel natural. If you are new to GraphQL, the reference includes enough context to get started, but you may want to supplement it with a general GraphQL introduction. ## How to read API documentation effectively API reference pages can feel dense if you do not know what to focus on. Here is a practical approach: 1. **Start with the endpoint URL and method.** This tells you what the operation does. GET /v3/content\_types/{content\_type\_uid}/entries retrieves entries; POST to the same path creates one. 2. **Check required headers.** Every Contentstack API call needs an api\_key header. Delivery calls need access\_token; management calls need authtoken or authorization (for management tokens). Missing headers produce authentication errors that can waste debugging time. 3. **Read the query parameters.** This is where the real power lives. Filtering, sorting, pagination, field projection, and reference inclusion are all controlled through query parameters. Understanding these prevents you from writing client-side filtering logic that should happen on the API side. 4. **Study the response format.** Look at the JSON structure. Note where the actual data lives (usually in an entries or entry key), what metadata is included, and how pagination information (like count and skip) appears. 5. **Try it.** Copy the example curl command, substitute your stack credentials, and run it. Seeing a real response is worth more than reading three pages of documentation. ## SDKs and language-specific documentation Contentstack provides official SDKs for several languages and platforms: * **JavaScript/Node.js** - The most commonly used SDK for web applications. Available for both Content Delivery and Content Management. * **Python** - Useful for scripting, data pipelines, and backend integrations. * **Java** - Common in enterprise environments and Android development. * **.NET** - For C# applications and Microsoft ecosystem integrations. * **Ruby** - Available for Ruby on Rails projects. * **Swift / iOS** and **Dart / Flutter** - For native and cross-platform mobile development. Each SDK has its own documentation section accessible from the main developer docs. SDK docs typically include installation instructions, initialization patterns, query examples, and reference documentation for the SDK's classes and methods. An important distinction: SDK documentation shows you how to use Contentstack through a language-specific abstraction, while the raw API reference shows you the underlying HTTP behavior. Both are valuable. When an SDK method does not behave as expected, checking the raw API reference often reveals what is happening underneath. You can find links to all SDKs at [https://www.contentstack.com/docs/developers/sdks/](https://www.contentstack.com/docs/developers/sdks/). ## Understanding regional API base URLs Contentstack operates multiple data center regions, and your API base URL depends on which region your stack is hosted in. Using the wrong base URL is a common source of "stack not found" or authentication errors. The regions are: Region Delivery API Base URL Management API Base URL North America (NA) cdn.contentstack.io api.contentstack.io Europe (EU) eu-cdn.contentstack.com eu-api.contentstack.com Azure North America azure-na-cdn.contentstack.com azure-na-api.contentstack.com Azure Europe azure-eu-cdn.contentstack.com azure-eu-api.contentstack.com GCP North America gcp-na-cdn.contentstack.com gcp-na-api.contentstack.com When you see an API example in documentation or in this curriculum, the base URL shown may not match your region. Always substitute the correct base URL for your stack. You can find your stack's region in the Contentstack dashboard under stack settings, or by checking the URL when you are logged into the Contentstack web application. ## GitHub repositories Contentstack maintains several public GitHub repositories that serve as both reference implementations and practical tools: * **SDKs** - Source code for all official SDKs is available on GitHub. This is useful when you need to understand SDK behavior at a deeper level or contribute bug fixes. * **Sample applications** - Starter apps demonstrating Contentstack integration with popular frameworks (Next.js, Gatsby, Nuxt, Angular, and others). These are excellent starting points for new projects. * **CLI tools** - The Contentstack CLI (@contentstack/cli) is a command-line tool for managing stacks, content types, entries, and migrations. Its source and documentation live on GitHub and npm. * **Automation Hub / Marketplace apps** - Examples and templates for Contentstack Automate connectors and marketplace applications. You can find Contentstack's GitHub organization at [https://github.com/contentstack](https://github.com/contentstack). When starting a new project, check the sample apps first - they often save hours of boilerplate setup. ## The Contentstack CLI The Contentstack CLI deserves specific mention because it plays an important role in developer workflows. Install it via npm: npm install -g @contentstack/cli The CLI supports operations like: * **Stack management** - Create and configure stacks from the command line. * **Content type export/import** - Move content type schemas between stacks, which is essential for migration workflows. * **Entry export/import** - Bulk content migration. * **Plugin and extension scaffolding** - Generate boilerplate for custom extensions. * **Seed** - Populate a stack with sample content for testing. CLI documentation is available at [https://www.contentstack.com/docs/developers/cli/](https://www.contentstack.com/docs/developers/cli/). ## Postman collections Contentstack provides Postman collections for both the Content Delivery API and the Content Management API. These collections include pre-configured requests for every endpoint, making it easy to explore the APIs interactively without writing code. To use the Postman collections: 1. Import the collection into Postman (links are available in the API reference docs). 2. Set up a Postman environment with your api\_key, access\_token or authtoken, and the correct base\_url for your stack's region. 3. Run requests and inspect responses. Postman is particularly useful during the learning phase because it lets you experiment with query parameters, inspect response headers, and build up API familiarity before writing application code. ## Community and support resources When documentation alone does not answer your question, Contentstack offers several support channels: * **Community forum** - The [Contentstack community](https://community.contentstack.com/) is a forum where developers ask questions, share solutions, and discuss implementation patterns. Search the forum before posting - many common questions already have detailed answers. * **Support tickets** - If you have a Contentstack account, you can file support tickets for technical issues. This is the right channel for bugs, unexpected API behavior, or account-specific problems. * **Stack Overflow** - Questions tagged with contentstack on Stack Overflow provide another searchable knowledge base. This is a good resource for finding solutions from the broader developer community. * **Contentstack Academy** - Contentstack's own learning platform at [https://www.contentstack.com/academy/](https://www.contentstack.com/academy/) offers additional courses and learning paths that complement this certification. * **Developer Learning Space** - The [Contentstack Developer Hub](https://www.contentstack.com/developers/) aggregates developer resources including tutorials, guides, and quickstarts. ## Tips for effective documentation navigation After working with Contentstack documentation regularly, a few navigation habits prove valuable: 1. **Use the search.** The documentation site has a search function that works across all sections. When you know the feature name or API endpoint you need, search is faster than browsing the navigation tree. 2. **Distinguish between guides and references.** Guides explain concepts and walk through workflows. References list every parameter and option. Start with the guide to understand the concept, then switch to the reference when you need exact syntax. 3. **Check the region.** As noted above, API base URLs differ by region. Whenever you copy a URL or code snippet from documentation, verify the base URL matches your stack's region. 4. **Look at the SDK source when behavior is unclear.** SDK documentation sometimes lags behind the raw API. If an SDK method is not behaving as documented, check the SDK source code on GitHub or test the equivalent raw API call directly. 5. **Bookmark your most-used references.** You will return to the Content Delivery API query parameters page, the content type field reference, and the webhook configuration guide repeatedly. Bookmark them instead of navigating through the menu each time. 6. **Check the changelog.** Contentstack publishes release notes and changelogs that document new features, API changes, and deprecations. When something works differently than expected, the changelog may explain why. ## Summary Contentstack becomes easier to learn when you know where to look. The main developer docs, API references, SDK docs, GitHub repositories, CLI docs, and community channels each answer different kinds of questions. Reaching for the right resource quickly is part of being an effective Contentstack developer. #### Key takeaways - Connect **Navigating Contentstack docs, APIs, and resources** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ### Lesson 04 — Getting started with the Veda Kickstart #### Lesson text # Meet Veda, the project behind the certification > **Your course lab: Next.js + Contentstack** > > Import one complete content and catalog experience, then use it to explore modeling, APIs, preview, workflow, and integrations throughout the course. [Import Veda from the Marketplace](https://www.contentstack.com/marketplace/kickstart-veda) · [Open the Veda setup guide](https://www.contentstack.com/docs/headless-cms/veda) * * * ## Content architecture at a glance page ├── product ├── category └── product\_line Structured entries → Next.js routes * * * ## Why Veda is our shared starting point Small kickstarts are useful for proving that a framework can fetch one entry. Veda goes further: it is a complete Next.js App Router reference for a content-driven jewelry catalog and marketing site. It includes several connected content types, reusable page sections, product discovery, metadata, Live Preview, Visual Editor support, and deployment-aware caching. That makes Veda substantial enough to reveal real architectural decisions while still being understandable as a learning project. You will return to the same stack and codebase throughout this certification instead of inventing a new example for every topic. > Content experience, not a commerce engine > Veda includes products, categories, product lines, navigation, and merchandising pages. It does **not** include a cart, checkout, payments, customer accounts, or order management. Treat it as the content and experience layer that a commerce platform could complement. * * * ## How Veda supports the course 1. **Start here: import a working stack.** See real schemas, entries, assets, and routes before studying them in isolation. 2. **Courses 1–3: understand the contract.** Trace how content types become API shapes and how the app fetches and renders them. 3. **Courses 4–7: operate and extend it.** Explore preview, releases, workflow, customization, deployment, and integrations. * * * ## What the starter gives you Layer What to look for Content model page, header, category, product, and product\_line content types Page composition Modular hero, list, media, two-column, and rich-text sections Application Next.js App Router, React, TypeScript, and Tailwind CSS Delivery Contentstack Delivery SDK fetchers for pages and catalog entries Editing Live Preview, Visual Editor bindings, and preview-aware rendering Operations Incremental Static Regeneration and Launch cache-priming support * * * ## Recommended setup: import from Marketplace The Marketplace route is the course default because it creates the content types, entries, and assets together without requiring CLI setup. ### Before you start You need: * a Contentstack account * organization Owner or Admin access to import the starter, or help from someone with that role * Node.js 20 or later for local development * familiarity with React, TypeScript, and the Next.js App Router when you begin exploring the code ### 1\. Import the starter 1. Open [Kickstart Veda in the Contentstack Marketplace](https://www.contentstack.com/marketplace/kickstart-veda) and sign in. 2. Select **Import**. You can also find it under **Marketplace → Starters** in Contentstack. 3. Name the new stack. Veda: The Revival Collection makes it easy to recognize during the course. 4. Select **Import Starter** and wait for the background import to finish. When the import completes, your stack should contain the Veda content types, sample entries, and assets. You may deploy with Contentstack Launch from the Marketplace flow, but a hosted deployment is not required for the early lessons. > The import is only the CMS half > Marketplace prepares your stack; it does not configure a local checkout of the Next.js application. Complete the next section if you want to run Veda locally. ### 2\. Inspect the content before the code Open the imported stack and find each of these objects: * the product content type and one product entry * the product\_line content type (including the underscore in its UID) * the category content type and its relationship to products * the page content type and its modular components * the header entry used for shared navigation Do not try to understand every field yet. Your goal is to recognize the major content shapes and see that the frontend relies on their UIDs as an API contract. ### 3\. Run the application locally Clone the canonical project and install its dependencies: git clone https://github.com/contentstack/kickstart-veda.git cd kickstart-veda npm install cp .env.example .env.local In your Veda stack, go to **Settings → Tokens**. Gather the stack API key, a delivery token, a preview token, the target environment, and the stack region. Add them to .env.local using the variable names from .env.example: NEXT\_PUBLIC\_CONTENTSTACK\_API\_KEY= NEXT\_PUBLIC\_CONTENTSTACK\_DELIVERY\_TOKEN= NEXT\_PUBLIC\_CONTENTSTACK\_PREVIEW\_TOKEN= NEXT\_PUBLIC\_CONTENTSTACK\_ENVIRONMENT= NEXT\_PUBLIC\_CONTENTSTACK\_REGION= NEXT\_PUBLIC\_CONTENTSTACK\_PREVIEW=true Keep .env.local out of version control. If you deploy through Launch, check that the hosted environment variables map to the exact names expected by the repository. Start the development server: npm run dev Open http://localhost:3000/ and browse beyond the homepage. Visit the product listing, a category, a product line, and an individual product to see how different content types drive different routes. * * * ## Your setup is complete when * \[ \] **The stack exists.** You can open the five core Veda content types and their sample entries. * \[ \] **The content is published.** The entries you plan to browse are available in the environment used by your delivery token. * \[ \] **The site renders.** The local app shows navigation, pages, and catalog content from your stack. * \[ \] **You can trace one item.** You can connect a product entry in Contentstack to its route in the running site. * * * ## If something does not work Symptom Check first Empty pages or missing navigation Confirm the starter finished importing and entries are published to the configured environment. Content cannot be found Make sure the stack region and delivery token belong to the same stack. Preview does not update Set NEXT\_PUBLIC\_CONTENTSTACK\_PREVIEW=true exactly, enable Live Preview for the stack, and use http://localhost:3000/ as the local preview URL. A content type query fails Confirm the expected UIDs are unchanged, especially product\_line. The app works locally but not in Launch Compare the hosted variables with .env.example and update the Live Preview URL to the deployed HTTPS origin. For a terminal-first alternative, deeper configuration details, and an explanation of the repository architecture, use the [official Veda setup documentation](https://www.contentstack.com/docs/headless-cms/veda). The [Veda developer guide](https://developers.contentstack.com/kickstarts/kickstart-veda) explains why the project is a useful reference implementation and highlights the files worth studying. ## Continue the orientation With Veda in place, complete [Your first Contentstack build](https://contentstack-developer-certification.eu-contentstackapps.com/course-0-orientation/module-0-1-what-this-certification-covers/04-your-first-contentstack-build). You will inspect one of the imported content types and retrieve its published entries through the Content Delivery API. #### Key takeaways - Connect **Getting started with the Veda Kickstart** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ### Lesson 05 — Your first Contentstack build: inspect content and make an API call #### Lesson text # Your first Contentstack build: inspect content and make an API call > TL;DR > > * Open a real stack before Course 1 so the platform stops feeling abstract. > * Identify one content type, one entry, one environment, and one delivery token. > * Make a Content Delivery API request and inspect the JSON response yourself. > * If you have time, repeat the same request with the JavaScript SDK to connect product concepts to code. ## Why this matters Developers stay motivated when they can prove, early, that they understand the product well enough to make something happen. This lesson gives you that first win before the certification asks you to reason about architecture, modeling, preview, and governance in depth. ## You will be able to * locate the minimum stack information needed to read published content * inspect a content type and entry in the Contentstack UI * run a first Content Delivery API request successfully * connect the returned JSON to the frontend work you will do later in the certification ## Recommended setup You will need: * access to a Contentstack stack * a published entry in at least one environment * a delivery token for that environment * curl available in your terminal If your stack is mostly empty, create one simple content type with a title field and publish one entry to a development environment before continuing. If you want a richer dataset, use the Veda seed content referenced later in Course 3. ## The quickstart path Use this lesson as a short lab. Do not just read it. Keep the stack open and complete each step. ### Step 1: inspect the stack basics In Contentstack, note these values: 1. Your **stack API key** 2. Your **stack region** 3. The name of one **published environment** such as development 4. One **delivery token** scoped to that environment You will reuse these four values throughout the certification. Course 3 explains them in depth; for now, the goal is simply to see how they unlock content delivery. ### Step 2: inspect one content type and one entry Open a content type and answer these questions: * What is the content type UID? * Which fields are clearly meant for API consumers? * Which fields exist to help editors work safely? ![product-contenttype-UID-veda.png](https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/ama87e2a10f85453f2/1790df8dbcf375d1ffcd85b1/product-contenttype-UID-veda.png?locale=en-us) Then open one published entry and note: * the entry title * the locale * whether the entry references other content or assets ![productentry-veda](https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/am797e217727c711d2/6f2f1af7ba7ab261b5c0e5ea/Screenshot_2026-07-07_at_10.54.06.png?locale=en-us) Use the Veda scenario if available. A product, category, or page entry works well because those shapes recur later in the certification. ### Step 3: make your first Content Delivery API request Replace the placeholders below with your own values: curl -s "https://cdn.contentstack.io/v3/content\_types//entries?environment=" \\ \-H "api\_key: " \\ \-H "access\_token: " \\ | jq If your stack is not hosted in North America, swap the base URL for the correct regional endpoint before running the command. When the request succeeds, look for: * the entries array * field UIDs that match the schema you inspected in the UI * system fields such as uid, locale, and timestamps If you get no data back, check the most common causes first: * wrong region * wrong environment * token scoped to a different environment * entry not published to the environment you requested ### Step 4: connect the JSON to real developer work Look at one entry in the response and answer: * Which fields would a listing page need? * Which fields would a detail page need? * Which fields would likely stay internal to editors? This is the core shift of the certification: you are not building around pages owned by the CMS. You are consuming structured JSON and deciding how each experience should render it. ### Step 5: optional SDK version If you want one extra confidence-building step, run the same idea through the JavaScript SDK: import Contentstack from "@contentstack/delivery-sdk"; const stack = Contentstack.stack({ apiKey: process.env.NEXT\_PUBLIC\_CONTENTSTACK\_API\_KEY!, deliveryToken: process.env.NEXT\_PUBLIC\_CONTENTSTACK\_DELIVERY\_TOKEN!, environment: process.env.NEXT\_PUBLIC\_CONTENTSTACK\_ENVIRONMENT!, region: Contentstack.Region.US, }); const result = await stack.contentType("").entry().query().find(); console.log(result.entries\[0\]); You do not need to master the SDK yet. The goal is simply to see that the same content can be explored through raw HTTP or through a developer-friendly library. ## Practice in Contentstack Complete this checklist before moving on: 1. Identify one content type and one published entry in your stack. 2. Run one successful delivery API request. 3. Save the response or copy one entry into a scratch file for later reference. 4. Write one sentence explaining what your frontend would render from that response. If you cannot complete all four steps, resolve that now. The rest of the certification becomes much easier once the platform feels concrete. ## Common mistakes ### Mistake 1: treating the dashboard as the whole product If you only click around the UI and never inspect the API response, Contentstack still feels like a form builder instead of a structured content platform. ### Mistake 2: using the wrong region or environment Many first-time delivery failures are not authentication failures at all. They are context mismatches: the wrong base URL, the wrong environment, or content that was never published there. ### Mistake 3: waiting until Course 3 to touch the APIs This certification gets easier when you connect concepts to one real response early. A single successful request now pays off for the rest of the path. ## Summary Your first win in Contentstack is small but important: identify a real content type, inspect a real entry, and retrieve published content yourself. Once you have done that, the rest of the certification is no longer about abstract CMS features. It is about understanding, shaping, and extending a platform you have already touched. #### Key takeaways - Connect **Your first Contentstack build: inspect content and make an API call** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ## Resources & references | Page | Companion Markdown | | --- | --- | | /courses/cms-developer-orientation/what-this-certification-covers-overview | /academy/md/courses/cms-developer-orientation/what-this-certification-covers-overview.md | | /courses/cms-developer-orientation/certification-scope-and-how-to-use-this-curriculum | /academy/md/courses/cms-developer-orientation/certification-scope-and-how-to-use-this-curriculum.md | | /courses/cms-developer-orientation/navigating-contentstack-docs-apis-and-resources | /academy/md/courses/cms-developer-orientation/navigating-contentstack-docs-apis-and-resources.md | | /courses/cms-developer-orientation/getting-started-with-the-veda-kickstart | /academy/md/courses/cms-developer-orientation/getting-started-with-the-veda-kickstart.md | | /courses/cms-developer-orientation/your-first-contentstack-build-inspect-content-and-make-an-api-call | /academy/md/courses/cms-developer-orientation/your-first-contentstack-build-inspect-content-and-make-an-api-call.md | ## Supplement for indexing ### Content summary Orientation Start the certification with clear expectations, the right resources, and a first successful interaction with Contentstack. Who This Course Is For Take this course if you are new to the certification, new to … Orientation Start the certification with clear expectations, the right resources, and a first successful interaction with Contentstack. Who This Course Is For Take this course if you are new to the certification, new to Contentstack, or want a faster path into the rest of the curriculum. You Will Be Able To explain how the certification is structured and how to study it effectively find the Contentstack docs, API references, SDKs, and support resources you will use repeatedly complete an initial stack and API walkthrough before the deeper conceptual courses Recommended Preparation Have a Conte ### Retrieval tags - Contentstack Academy - cms-developer-orientation - What - This - Certification - Covers - Overview - scope - and - how - use - Navigating - Contentstack - docs ### Indexing notes Chunk at each "### Lesson NN — Title" heading; copy lesson_id and topics from the preceding HTML comment into chunk metadata for RAG filters. Course slug: cms-developer-orientation. Union of lesson topic tokens: What, This, Certification, Covers, Overview, scope, and, how, use, this, Navigating, Contentstack, docs, APIs, resources, Getting, started, with, the, Veda, Kickstart, Your, first, build, inspect, content. Do not embed or retrieve LMS-only quiz items or mastery exam answer keys from this export. ### Asset references | Label | URL | | --- | --- | | veda-homepage.png | `https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/am30ebfcf40c0fc2ae/1032ef6e839bfc6de70ac732/veda-homepage.png?locale=en-us` | | product-contenttype-UID-veda.png | `https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/ama87e2a10f85453f2/1790df8dbcf375d1ffcd85b1/product-contenttype-UID-veda.png?locale=en-us` | | productentry-veda | `https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/am797e217727c711d2/6f2f1af7ba7ab261b5c0e5ea/Screenshot_2026-07-07_at_10.54.06.png?locale=en-us` | ### External links | Label | URL | | --- | --- | | Contentstack Academy home | `https://www.contentstack.com/academy/` | | Training instance setup | `https://www.contentstack.com/academy/training-instance` | | Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` | | Contentstack documentation | `https://www.contentstack.com/docs/` | | https://www.contentstack.com/pricing | `https://www.contentstack.com/pricing` | | veda-homepage.png | `https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/am30ebfcf40c0fc2ae/1032ef6e839bfc6de70ac732/veda-homepage.png?locale=en-us` | | https://www.contentstack.com/docs/developers/ | `https://www.contentstack.com/docs/developers/` | | Content Delivery API reference | `https://www.contentstack.com/docs/developers/apis/content-delivery-api/` | | Content Management API reference | `https://www.contentstack.com/docs/developers/apis/content-management-api/` | | GraphQL API reference | `https://www.contentstack.com/docs/developers/apis/graphql-content-delivery-api/` | | https://www.contentstack.com/docs/developers/sdks/ | `https://www.contentstack.com/docs/developers/sdks/` | | https://github.com/contentstack | `https://github.com/contentstack` | | https://www.contentstack.com/docs/developers/cli/ | `https://www.contentstack.com/docs/developers/cli/` | | Contentstack community | `https://community.contentstack.com/` | | Contentstack Developer Hub | `https://www.contentstack.com/developers/` | | Import Veda from the Marketplace | `https://www.contentstack.com/marketplace/kickstart-veda` | | Open the Veda setup guide | `https://www.contentstack.com/docs/headless-cms/veda` | | Veda developer guide | `https://developers.contentstack.com/kickstarts/kickstart-veda` | | Your first Contentstack build | `https://contentstack-developer-certification.eu-contentstackapps.com/course-0-orientation/module-0-1-what-this-certification-covers/04-your-first-contentstack-build` | | product-contenttype-UID-veda.png | `https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/ama87e2a10f85453f2/1790df8dbcf375d1ffcd85b1/product-contenttype-UID-veda.png?locale=en-us` | | productentry-veda | `https://assets.contentstack.io/spaces/amfbc91b83fc78cf96/assets/am797e217727c711d2/6f2f1af7ba7ab261b5c0e5ea/Screenshot_2026-07-07_at_10.54.06.png?locale=en-us` |