Author Archives: John West

This blog post describes an experimental technique that uses content delivery APIs to access content management environments in the Contentstack SaaS headless CMS. For solutions that use a limited subset of content delivery APIs, this approach could support CMS previewing environments that render saved content immediately, without the need to publish those changes to aContinue reading “Previewing without Publishing in the Contentstack SaaS Headless CMS”

This blog post, part of a series about JSON data formats in the Contentstack SaaS headless CMS, describes how Contentstack represents complex field values. Complex fields are those that consist of JSON rather than scalar values. Contentstack JSON Data Formats: Introduction and Scalars – Deliverystack.net Rather than storing zero or more simple, scalar values, complexContinue reading “Contentstack JSON Data Formats: Complex Fields”

This blog post, part of a series about JSON data formats in the Contentstack SaaS headless CMS, describes how Contentstack represents media asset metadata and references as JSON. Contentstack JSON Data Formats: Introduction and Scalars – Deliverystack.net In Contentstack, assets store metadata about files uploaded into the CMS. Technically, assets are like entries in thatContinue reading “Contentstack JSON Data Formats: Assets and File Fields”

This blog post, part of a series about JSON data formats in the Contentstack SaaS headless CMS, describes how Contentstack represents entries as JSON, where entries are records in the CMS that contain values for the fields defined by the content types associated with those entries. Contentstack JSON Data Formats: Introduction and Scalars – Deliverystack.netContinue reading “Contentstack JSON Data Formats: Entry Structure”

This blog post, part of a series about JSON data formats in the Contentstack SaaS headless CMS, describes how Contentstack represents data stored in modular blocks fields as JSON. Contentstack JSON Data Formats: Introduction and Scalars – Deliverystack.net Contentstack modular blocks fields contain blocks of data. In an entry, a modular blocks field may containContinue reading “Contentstack JSON Data Formats: Modular Blocks Fields”

This blog post introduces a series about JSON data formats used by the Contentstack SaaS headless CMS. Contentstack JSON Data Formats: Introduction and Scalars – Deliverystack.net Contentstack JSON Data Formats: Modular Blocks Fields – Deliverystack.net Contentstack JSON Data Formats: Entry Structure – Deliverystack.net Contentstack JSON Data Formats: Assets and File Fields – Deliverystack.net Contentstack JSONContinue reading “Contentstack JSON Data Formats: Introduction and Scalars”

This blog post provides perspectives on what it means for a content management system to be considered headless. A content management system structures and separates data from its use, allowing domain experts to maintain content used by delivery systems such as websites and mobile applications. Rather than providing HTML generation engines, headless CMS expose contentContinue reading “What Does It Mean for a CMS to Be Headless?”

This blog post discusses forms of coupling between content management and content delivery systems in the context of headless CMS. Vendors use the term decoupled rather loosely and inconsistently, generally to indicate that content delivery does not depend on content management, but without describing exactly how. As I tried to understand what decoupled means, aContinue reading “Coupling in [Headless] CMS”

This blog post explains how you can configure a Vercel website to allow URLs for static HTML files without requiring the .html extension in URLs. By default, Vercel requires that URLs for static HTML files include the .html extension. An HTTP request for the URL /path/file.html will retrieve the file at that path, but anContinue reading “Use Static Files and Vercel without the .html Extension in URLs”

This blog post suggests that, when exporting the JSON representation of an entry (record) from a content management system, that JSON should include metadata about the children of the entry based on its URL path. For example, when exporting the JSON representation of the home page at the URL /, that JSON should include metadataContinue reading “Export Child Entry Metadata with Entries from Content Management Systems”