The Headless [CMS] Metaphor

This blog post provides my perspective on the headless CMS (Content Management System) metaphor, although some of this content may apply to any headless system. Different CMS vendors use different terminology and definitions. This is my general summary assuming a website as the default delivery channel. Body: The CMS back-end, where content management users maintainContinue reading “The Headless [CMS] Metaphor”

Considerations for Headless CMS Architectures

In the context of a managing a website but likely in more general contexts, there are at least three common architectures for headless CMS: Browsers load static files from web server in content delivery tier that contain data exported from the CMS. Browsers load static files from web server in content delivery tier and consumeContinue reading “Considerations for Headless CMS Architectures”

Resources about Windows Subsystem for Linux (WSL)

This blog post contains a list of links to resources about Windows Subsystem for Linux (WSL). WSL allows running Linux, specifically Bash interactive shells and shell scripts, under Windows. Whenever possible, I use Bash shells and keyboard shortcuts in favor of the Windows user interface. Because they are not specific to headless content management orContinue reading “Resources about Windows Subsystem for Linux (WSL)”

Considerations for Migration to Headless CMS

A recruiter contacted me recently about a project migrating a B2B commerce implementation to headless CMS, which got me thinking about how I might approach such an opportunity. When I walk into a relatively open engagement like this, I generally try to interview as many people as I can, whether I have a chance toContinue reading “Considerations for Migration to Headless CMS”

[Hard] Questions for [Headless] [CMS] Vendors

I intend to use this blog post to catalog questions for headless CMS (Content Management System) vendors that I do not consider to be excessively specific to an individual project. Many of these questions may apply to related implementation scenarios. These issues are in no intended order, are not intended to benefit any specific vendor,Continue reading “[Hard] Questions for [Headless] [CMS] Vendors”

Screen Shots of ASP.NET Core Web Server Output

Here are some screen shots that show preloading all Entries in a Stack into a repository in memory using different Stacks and configurations. Most of this output is from an Instrument class that I expose through a property of the repository itself for convenience, since any code can always access the repository to get otherContinue reading “Screen Shots of ASP.NET Core Web Server Output”

Contentstack Developer Convenience Controller

The code for my previous post registered this controller named Contentstack and I would not want anyone to think that it came from Contentstack. It is super hacky, just for evaluating things and common convenience features in development (for security, it should NOT be enabled except in development). It uses query string parameters but atContinue reading “Contentstack Developer Convenience Controller”

Example .NET Core Controller Action for [Headless CMS] Repository

What follows is a draft of a simple controller action that could support any headless CMS using the repository pattern described in this blog. Most of my ASP.NET project is just template from Visual Studio. Update: This is NOT about generic classes; I should not have used the word generic in the original title ofContinue reading “Example .NET Core Controller Action for [Headless CMS] Repository”

Working with [Headless] [CMS] Vendor [.NET [Core]] SDKs

To summarize: minimize. It is impossible to use an SDK or API without making solutions depend on that SDK or API, including its JSON formats, .NET types, method calls, and otherwise. If you want a big .NET API, you are probably looking for an integrated experience platform rather than a CMS. With headless, you useContinue reading “Working with [Headless] [CMS] Vendor [.NET [Core]] SDKs”

Sample Contentstack Complete Entry Model Class

The ResourceEntry class below provides an example of a complete Entry Model Class for the Contentstack SaaS headless CMS. This Entry Model Class represents a generic type of content resource (also the name of its Content Type) that can manage several different types of content in a Modular Blocks Field. There really is not muchContinue reading “Sample Contentstack Complete Entry Model Class”