This issue was published on Tuesday, April 30, 2019.
Content Modeling Debate: My friend Allan Thraen and I were mildly arguing about whether or not it's smart to allow editors to change content models from the interface, or if this is a developer-centric activity. Allan posted about his experience and I wrote a rebuttal(-ish):
- Allan: The Curious Case of Content Modeling
- Deane: Repouring the Foundation: The Perils of Content Modeling on the Fly
I followed that up a week later by dusting off a post I had been writing on and off for a year, in which I argue that we just need to some agreement as an industry.
And there were some nice takeaways on the resulting Twitter thread.
Hertz Sues Over AEM Implementation: Hertz, the rental car company, is suing Accenture for an Adobe Experience Manager implementation that went sideways.
The implementation was $32 million, and Hertz purports it to be a mess.
“Accenture's developers wrote the code for the customer-facing ecommerce website in a way that created serious security vulnerabilities and performance problems,” it says before noting that "the defects in the front end development code were so pervasive that all of Accenture's work on that component had to be scrapped."
The article is a voyeuristic view into a CMS implementation trainwreck. Clearly, we're only reading one side of it, but if you think you've been on some bad projects, know that it could get worse.
In the end, Jarod Spool wins the cynicism Olympics with this tweet:
Has there ever been a successful large-scale digital transformation led and executed by an outside vendor?
Org-mode: I mentioned Org-mode last year when discussing Lightweight Markup Languages. It's not well-known – it was created in 2003 specifically for use with Emacs. It's on version 9+ and even has a couple of reference books.
If you love markup formats and geeky discussion about how to represent ideas and formatting in plain text, then that is absolutely your jam.
Xillio: Xillio looks like a neat service that promises “content integration.” They have connectors for what looks like dozens and dozens of CMSs and storage systems and they're promoting the ability to mix and match content between them.
The API enables developers to create one single integration and connect to multiple repositories, without the need for repository specific code. Xillio uses a repository-agnostic code, meaning that if it works for one repository, it works for all repositories.
(True story: I wrote a blog post about content integration once, in the sense of bringing external content into a CMS, like Xillio. However, I finally had to put a disclaimer at the top of it because my analytics told me that “content integration” is a phrase that applies to teaching, and most of the people finding the post from search were teachers working on their certifications.)
GitHub Issues Blog: I like inventive usage of tools to create “CMS,” and this guy using the issues log of his GitHub project as a blog is just the CMS weirdness we all need today.