At first look, Plone looks clean, organized. The ideal city!

.fx: extra-large

Now, you want to develop something by your own. Can you face the awful truth?

.fx: extra-large

Well, you will get a very though awakening

.fx: extra-large

If you are strong enough, at some point you will see the matrix. This guy is a Plone developer: he moves fluidly in a middle of a shit storm, he looks quiet and confident because he knows exactly which moves he has to take to face any given danger second by second.

.fx: extra-large

They should be able to walk free in the ideal city

.fx: extra-large

backend api / front pure js is good and trendy, why would I need a CMS as backend? in my last non-Plone project (tereval), it took 4 days to get a working breadcrumb

.fx: extra-large

I want Plone to be their CMS

.fx: extra-large

Why should we need more knowledge than HTML and webmastering to do something with Plone?

.fx: extra-large

Here I am not criticizing the Plone documentation, which is very good. The problem is the whole Plone story here, which is too big.

We have just started such a work in training.plone.org

.fx: extra-large

Good back-office because: good UI to manage content, super secured, easy to customize.

Ok, so Plone is useful even if you are not a Plone developer. But most part of people do not want to write a browser view to get a json. They feel more confident with npm script than buildout recipes.

.fx: extra-large