Overhaul of the Volto introduction. Add prod examples. Fixes #853. #854
Conversation
There was a problem hiding this comment.
Good to simplify, you cannot namedrop things like "object traversal" in an introduction without at least explaining them. If not, better to leave out. It would of course be good to explain some concepts later, such as content types and indeed traversal, but not here
|
IMHO, I think that we must state more clearly that Volto supports a basic subset of features using Guillotina as a backend. I'm fine to do it at the end in order to not confuse people about the current feature support but it should be said at some point. In the current state, Guillotina just pops out of existence on the page without further introduction. I'm fine with the rest. |
| Volto uses [Plone](https://plone.org) and its [REST API](https://github.com/plone/plone.restapi) as a backend. | ||
| Plone is a mature and secure content management system written in [Python](https://www.python.org/). | ||
| It has the [best security track record of any major CMS](https://plone.com/secure.html). | ||
| Out-of-the-box, Plone comes with everything you need to build sophisticated websites and enterprise-grade intranets. |
There was a problem hiding this comment.
Sorry, but we are doing it again. We are overselling Plone over the subject of the writing. We are speaking now about Volto, right? So Plone can't have more sentences describing it than Volto has. Volto has plenty of features worth to be mention above the fact that the backend is Plone.
There was a problem hiding this comment.
@sneridagh you are absolutely correct. I think I have to rewrite the entire thing from the scratch again to get it right. It is so hard to get Plone out of our heads here...
|
For me, it's confusing for my clients that Guillotina is experimental or even not mentioned on the backends as we are delivering it. For us, it's really stable and allows projects to not depend on any python developer from bootstrap to deliver. |
|
@polyester @sneridagh @bloodbare you all make very good points! This was meant as a first draft. I wanted to start from zero. Taking into account my own experience and expectation as a developer when I check out a new project on github. I don't want to read a real introduction and hear how awesome a project is or how many backend options I have. I want to see where it is used in production and a link to the demo. Then I re-visit the README to get more in-depth information. I will go over the introduction and try to include your concerns. I agree that we shouldn't sell Guillotina as experimental. It is stable and ready for production use. Though, from a users/dev point of view, who does not know the difference between Plone/Guillotina/NodeJS, this is all an implementation detail. Plone is an implementation detail. The Volto introduction in the README should sell Volto, nothing else. |
|
Superseded by #3131 |
No description provided.