The CMS Trap

From Issue #24

I enjoyed this essay about what we need to content manage and what we don’t: The CMS Trap.

A CMS Trap is a state of a web-application in which the development of content management systems is obstructing the development of the content.

The author argues that as soon as we decide to provide management tools for something, we open up a huge nest of problems, and sometimes no management is the better answer. This echos what I wrote in my article for O’Reilly from our last issue.

A programming pragmatism is “YAGNI”, which means “You aren’t gonna need it.” In CMS, should we have YAGMI – “You aren’t gonna manage it”?

This is item #118 in a sequence of 305 items.

You can use your left/right arrow keys to navigate