Do you wish your content management system were as complex as your code? Wish no more.

Excerpt

What happens when you have requirements for a CMS that don’t quite fit any off-the-shelf solutions you can find, so you let your developers run wild with the specs?

Description

What happens when you have requirements for a CMS that don’t quite fit any off-the-shelf solutions you can find, so you let your developers run wild with the specs? You end up with an application that supports nested content, hierarchical multi-tenant, multilingual sites, the ability to move content through the deployment pipeline with code changes, and site/environment based user permissions. And Pac Man (don’t ask, we’ll tell you all about it). Sure, it may be that we needed all that (except the Pac Man) but the complexities of who can see what where and when made using the application and viewing the content less than optimal.

We talk through the techniques we used to speed up both sides of our CMS including Postgres query optimization, API-side caching, full-text search vectors, user roles, and content inheritance in an expansive yet sparsely populated site-environment-permission space. And then we threw in the ability to preview content live…

Speaking experience

This is a place holder for our development team, the final speaker is TBD.