Why CMS will not die

Why CMS won't die

Éric Bréhault - PloneConf 2014

Our world: the web

Something new every minute!!

All the CMS are old

Typo3: 1997Drupal: 2001Plone: 2002Wordpress: 2003Joomla!: 2005 (forked from Mambo: 2000)

Not that old

because CMS are still alive.

Sometimes that old

ElegantSuper-hard tomoveNot 100%compliant withmodern comfort standards

Mostly that old

Grumpy but sharp!

But we keep them

BECAUSE USERS NEED CMS!!!

OK, no-CMS is possible

At the beginning, users probably just want to edit

But...

They will also need to manage medias.

But...

A validation workflow would be nice.

But...

Hence we have to manage access rights.

But...

Newsletter is a must-have

But...

Plus a document sharing restricted area.

But...

Multilingual.

But...

Subsites, which are all identical but 2 or 3 things.

Next thing you know...

Face it, you need a CMS

And there will be no youngnewcomers

because CMS are special

Nobody knows about CMS but us (CMSistas)

because CMS are huge projects

It cannot be managed and developed just like anyproject.

Example: who needs buildout in Python but us?

Wordpress = 60%

100% tomorrow? No way!

Never saw any WP at any of my customers.

Nobody promises it will be easy

Is Plone too complex to survive?

All CMS are complex

Recipe to survive?

My 2 cents:

make it always more usable,clear frontend / backend dichotomy.

Thank you!