Articles on episerver.com
I’ve written quite a few articles for Episerver’s resources section.
Changing times will cause dramatically changed consumer and business behavior.
When crisis hits, you need to concentrate on flying the plane.
A CMS should be a content collaboration platform, not just a way to cross the last-mile of publishing.
What people want might not be what they tell you they want. We are what we consume.
Headless isn’t nearly as revolutionary as it once was.
Episerver has been doing “pure” content for over a decade, despite attempts to pigeonhole it as a “web” CMS.
This was an interview with Episerver’s CMO about headless. It covers some CMS history too, which I love.
A review of all the tools in Episerver to keep your content safe and comply with your regulatory environment.
A discussion about hosting models and delivery architectures and how people keep getting them confused.
A fairly combative email about how making a website using some headless architecture is probably best-served by a traditional web CMS.
An admittedly clickbait-y title about what makes a CMS really flexible and adaptable.
For whatever reason, we love tearing things down and rebuilding them, rather than slowly improving over time.
Episerver published a few chapters of my 25 Lessons book as blog posts
Sometimes, you can’t come up with an ROI number, and that’s okay.
People say they want everything “out-of-the-box.” But they don’t, really.
Content management RFP responses can be multi-headed, and therefore confusing.