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

This issue was published on Thursday, October 11, 2018.

Subscribe to receive future issues

Non-sequiturs from the world of content management.

I'm writing this from the Walt Disney World Dolphin Hotel where I delivered the developer keynote for Sitecore Symposium. Thanks to Sitecore for a great event, and for reaching beyond the Sitecore community for speakers. Video was recorded, and I'll include a link in a future issue of Squirrel Notes.

CommonMark: A Spec for Markdown. I love Markdown. It's a good balance between formatting functionality and simplicity, and I love how it's all "in the open," meaning that formatting isn't obscured by a rich text editor that seeks to keep all HTML tags out of view.

Even with Markdown embedded, text still makes sense. And Markdown feels... precise to me. I'd rapidly like to get to a world where everything I do is written as Markdown and stored in Dropbox (RIP: Beegit). The peace of mind I would gain would be remarkable.

(True story: I wrote my entire book in a Markdown-like language called AsciiDoc, via O'Reilly's Atlas system.)

Anyway, 14 years after it was first announced, did you know there's a developing Markdown standard, called CommonMark? It seeks to baseline a version of Markdown that we can all rally around and declare our support for. Extensions can still exist, but the idea is that CommonMark is the lowest common denominator of Markdown that implementations can seek to support.

Here's the specification. It's still iterating pretty rapidly, and they're hoping to get to 1.0 yet this year.

(BTW: I originally used Textile, back in the day, because Movable Type had a plugin. Here's my original blog post discussing it. But Markdown quickly surpassed it in adoption, so it became the de facto standard.)

Magnolia on "Hybrid Headless". Here's a good blog post by Magnolia which discusses the idea of "hybrid headless," which is their name for a WCMS that manages and delivers web content really well, and also allows for headless delivery when necessary.

This is a model I absolutely believe in. I've heard it called "Headless Optional" and "Also Headless" as well.

The WCMS Glossary. A few years back, I wrote a glossary of web content management terms.

The original plan was for this to be part of the book, but it didn't make it in time for publication with the first edition, and I wasn't convinced it was comprehensive enough, so I kept it as a "web-only supplement." It's currently ranking fairly high for "content management glossary" and it sees a steady stream of traffic.

I'm presently defining 210 terms, from A/B Testing to XLIFF. If you see anything missing, drop me a note. I'd love to keep expanding it.

Apple's CMS failure. I perversely enjoy big CMS failures. Here's a blog post from 15 years ago when I found one on USA Today (also note: I was basically describing BuiltWith in that blog post — I should have done something with the idea...)

Well, Apple just had a significant CMS failure. Their CMS pre-published the URLs of multiple pages revealing the new iPhone models before the announcement, and — like it always is when you make a mistake — people were watching.

All Things How has a good summary, complete with screencaps.

Episerver's EMEA Partner Summit. I'll be hosting the dev track of the Episerver Partner Summit in Stockholm in February.

Our unofficial theme is "Exploring the Other Side of the Publish Button," meaning all the neat things you can do with content after you publish it. Episerver has some great technology for delivery optimization, and we'd like to introduce developers to the things that can be done in the publication environment.