Squirrel Notes is an email newsletter about CMS and other content technologies. It publishes twice each month.

This issue was published on Monday, July 09, 2018.

Subscribe to receive future issues

Non-sequiturs from the world of content management.

Note that I delayed this issue because of the holiday in the U.S. which fell directly in the middle of the week. This prompted many to take the entire week for a vacation.

Wordpress Migration Statistic. My friend Seth Gottlieb is the new Vice President of Research Products at Aberdeen. He's examining a dataset of CMS migrations, and he provided me with a stat on migrations away from Wordpress.

In Seth's dataset, 23% of CMS migrations are from WordPress to another system. Seth gave me the top three post-Wordpress systems:

  • Drupal (30%)

  • Wix: (20.8%)

  • HubSpot: (13.3%)

Seth will be providing other stats for Notes in the future.

All-New Denina Documentation. While at the Umbraco conference, I found a developer who said he could write an integration for Umbraco...then sent me one about four hours later. This prompted me to:

Hopefully I'll have an Umbraco integration soon, with integration for other CMSs on the way (two eyes looking right at you, Sitecore).

No idea what I'm talking about? Start with the original blog post: Editorial Scripting in CMS.

Serverless CMS. I keep hearing the "serverless" qualifer more and more to describe solutions that are not bound to a single machine, but instead powered by a collection of cloud services, strung together with APIs.

I've dug into the "serverless CMS" term a little. Lots of SaaS vendors are claiming the moniker, but that's meaningless because with SaaS, you have no control over the infrastructure anyway. (Something could call itself "serverless" and still be server-bound, and how would you know the difference?)

Some hosting vendors are trying to get some usage share around the term (ex: Aerobatic), but what would a serverless CMS look like without a vendor? I found Aerosol and Kitsui, but this is still a term that needs to sort itself out and figure out how it's different from "normal" SaaS.

(Just before this issue left the server, I found this: The Power of Serverless. It's an entire website about serverless, though not just for CMS. I haven't had a chance to review it yet, but it seems relevant.)

WordPress's Gutenberg UI. WordPress has a new upcoming UI refresh that narrows the focus on content creators, as opposed to "power editors" to drift into administration. They're calling the experience Gutenberg, after Johannes Gutenberg, the inventor of the printing press.

Gutenberg also brings "blocks" to WordPress, an editorial tool popularized by Medium. And they're going all-in:

Blocks are the de facto new mechanism for building content features, and we recommend that developers migrate any features they offer that are well-encapsulated by blocks.

Back in 2008, I was calling this style a "composite page"

A Guide to GraphQL. We talked a bit about GraphQL in a prior issue. A friend told me about this "book": The GraphQL Guide.

I quote the word "book" because it's less of a book and more of an experience. You can buy (scroll...) multiple "levels," including those with Git repo access, a t-shirt, a compansion Slack community, etc. It's an interesting example of omni-media content, and how a technical book can extend past the words into something entirely different.

Correction: New York Times Link. Sadly, we had an link error in the last issue. I've corrected it for the archive, and the correct link to the article about tagging and metadata at the New York Times is here:

Metadata and the Tagging Process at The New York Times

In the words of The Times itself: "We regret the error."