Squirrel Notes is an email newsletter about CMS and other content technologies. It publishes twice each month.
This issue was published on Friday, March 02, 2018.
Non-sequiturs from the world of content management.
A Versioning Primer. The Wikipedia page for Version Control is worth reading. CMS versioning is always less intensive than source code versioning (and some would say that version control and versioning are two different things), but the theoretical concepts of comparing and reconciling changes is a core content skill.
Static Site Generators. A friend and are debating a blog post about CMSs for very small websites. But, with the advances in static site generation, some sites don't need a traditional CMS at all. Functionality keeps moving to the client, and a static/generated website is a perfectly viable option for many cases.
Here's a directory of static site generation tools. I'm personally partial to Wyam, as it's on .NET and is phenomenally well-architected, but there's something for almost every platform.
Headless CMS Directory. Here's a new directory for headless CMS. If it looks similar to the static site gen directory, that's because it's run by the same folks.
However, as I mentioned in a blog post about the headless market last year, it's just not that simple. There are "pure" headless CMS, then there are other systems that are headless-ish. The lines are very blurry. (Hell, combine an API event model, cloud storage, and a few dozen lines of code, and technically anything can be headless...)
And to get really meta, we should talk about combining headless and static which brings us all the way back around to...decoupled? I take credit for bringing together Contentful and Wyam, which resulted in an official connector between those two systems.
Masters in Content Management. I've been looking for a "Masters of Content Management" program for about a decade now (proof: here's a blog post from 2006). But what would have even look like? My suspicion is that it's a combination of three things:
The first one is easy enough to find, but the last two are harder. A couple resources:
An API for Words. The Words API is an — wait for it — API for words. It's a REST service that will perform any number of operations on English language text, including getting definitions, synonyms, or antonyms. There are a number of ways this could be integrated into a CMS to provide editorial assistance. (Incidentally, I first wrote about the Words API in what remains the only post to ever take Gadgetopia offline).