> ## Content Index
> Fetch the complete content index at: https://onemanandhisblog.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Why your big custom CMS project is doomed
- URL: https://onemanandhisblog.com/2015/01/publishers-custom-content-management/
- Published: 2015-01-26T13:56:00.000Z
- Updated: 2015-04-08T16:29:09.000Z
- Author: Adam Tinworth
- Tags: cms, developers, publishers, technology woes

You have [an in-built fatal flaw](http://www.pbs.org/mediashift/2015/01/why-its-risky-business-for-publishers-to-build-their-own-cms/?ref=onemanandhisblog.com):

> News organizations, especially ones with just one medium-sized digital property (this applies to many independent daily newspapers, for example), have a terrible time retaining technical talent. These organizations generally don’t employ more than a few such professionals, making the risk of attrition very high— and attrition is almost always cultural. Using a common framework like WordPress at least gives the next programmer a head start on understanding what his predecessor did.

Here’s another side to the same equation: if you *can* retain your talent, the chances are you’ve got mediocre programmers working on your CMS, given how in-demand developers are right now.

This is why pretty much every journalist I know, bar those working at *Buzzfeed* and *Mail Online* hate their CMSes with a passion.

\[via [Matt](http://ma.tt/2015/01/build-a-cms/?ref=onemanandhisblog.com)\]