A few years ago, my good friend, Deane Barker, wrote the Flying Squirrel Book, the official O'Reilly animal book on Web Content Management. I was lucky enough to be invited to write a little sidebar in that book - and the first few lines describes very well how I felt about Content Management when I first got into it. CMS is about putting content into a database and then pulling it out again and presenting it. How hard could that be.
But what I've found is really fascinating is how the CMS often is the center piece of many other systems that needs to integrate in often quite advanced ways while providing editors with capabilities that enable them to produce great content and target it at the right visitors.
Before I joined Episerver, I worked with both SiteCore and Episerver CMS - and over the years I've taken a natural interest in several other WCMs.
Content Providers and Flat Content
A classic challenge in many CMS - and also in Episerver - has always been what do you do with large amounts of non-hierarchical/flat content? There has been many workarounds along the way and I was just on my way to make yet another when I discovered a well hidden secret deep in the belly of Episervers UI: The Asset widget (that holds blocks and media items) does in fact have infinite scrolling - which in turn can support incredibly large flat structures!
Understanding Episerver CMS - How are images rendered
When using reusable content such as images, the actual HTML rendering of them can happen multiple places. But when is what used? And how can you customize it?
Gist Content Provider
Always preferring coding over 'real work' I figured that it would be pretty neat if I could just drag and drop my gists on GitHub directly into my blog posts here in Episerver in order to embed them. Naturally, a content provider seemed like the right choice...