Author Archives: John West

This blog post explains how you can expose the JSON representation of an Entry retrieved from a headless CMS in an Entry Model class. Having access to the cached JSON can be incredibly valuable and could justify retrieving and caching the entire Entry JSON once rather than retrieving the Fields Values needed for specific purposesContinue reading “-Expose Entry JSON from Entry Model”

This blog post continues (maybe a bit repetitiously) the rant that I started at https://deliverystack.net/2020/07/21/contentful-net-sample-entry-model/. In that post I mentioned some of the implications of Contentful’s representation of the value of Rich Text Fields in a proprietary JSON format rather than XHTML, and some of the technical implications of that implementation. I understand the intention,Continue reading “-Some [More?] of the Reasons Why I Do Not Like How Contentful Represents Rich Text Fields”

Content Modeling is basically the definition of Content Types and relationships between Entries. Content Modeling should be the main part of a CMS implementation, and should begin with detailed requirements. Thoroughly evaluate content modeling features before selecting a CMS platform. Confirm basics such as support for referenced/nested Entries and custom Field Types that you canContinue reading “-CMS Content Modeling Considerations and Resources”

It is very valid for .NET Core developers working with headless CMS to ask why some of the code suggested in this blog does not appear in the SDK, including at least the following. Update 14.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likely stay here forContinue reading “-Why Isn’t This In the .NET SDK?”

You can use Block Model classes to model the different types of blocks that can appear in a Contentstack Modular Blocks Field as strongly-typed objects. Update 14.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likely stay here for some time, but new content will appear here: BlockContinue reading “-How Contentstack Modular Blocks Fit .NET Core”

When invoking RESTful API calls to retrieve data from a Content Management System (CMS), search index, or other system, a common pattern is that the service returns a limited number of records of a maximum fixed size, called a page. If you need additional records, you request the next page. Update 14.Dec.2025: After years ofContinue reading “-.NET Core Paging and Threading with Headless (CMS)”

If you can access the JSON representation of an Entry, then you can convert that JSON to an Entry Model (https://deliverystack.wordpress.com/2020/07/20/net-core-headless-cms-entry-models-and-entry-model-classes/). Update 14.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likely stay here for some time, but new content will appear here: This functionality works well asContinue reading “-Convert Entry JSON to Entry Model”

In a previous blog posts (https://deliverystack.wordpress.com/2020/07/21/contentstack-net-sample-entry-model/) I may have cast Contentstack Modular Blocks (https://www.contentstack.com/docs/developers/create-content-types/modular-blocks/) in a bad light. In fact, Modular Blocks are incredibly powerful and honestly one of the few differentiators between headless CMS providers from a .NET content delivery perspective. They aren’t difficult to model or implement. Update 14.Dec.2025: After years of frustrationContinue reading “-Contentstack Modular Blocks and .NET Core”

The (Best) [CMS] API Has No Methods. I mean that in the sense that The Emperor Wears No Clothes. With twenty five years of experience in enterprise systems including twenty in CMS, I mean it with conviction. Update 14.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likelyContinue reading “-The (Best) [CMS] API Has No Methods”

In addition to supporting modern JavaScript frameworks (and actually fitting well with .NET Core and ASP.NET Core), because they allow each party to focus solely on their own requirements and technologies using stable and well-defined interfaces to other platforms, complete SaaS solutions (cloud-hosted, microservice-architected, RESTful API-implemented, decoupled, including content management) derive maximum value from theContinue reading “-SaaS is the Only Real Cloud”