Recs.
Updated
SpecsUpdate
Pros
Cons
Con Horrible documentation; Keystone5 is unfinished and the team dumped it for a whole (stripped down) new version
Team even admits to a lot of areas being undocumented. Just spent 5 months implementing Keystone5 just to have it marked for deprecation. Next version removes DB Adapters (the entire reason for us implementing it). This project is poorly managed, and extremely difficult to extend due to incomplete documentation.
Con Github activity is dwindling
A lack of releases since the beginning of 2017, removal of the 4.x beta branch and few commits show that activity on this project is in a downward spiral.
Con Some working knowledge of JavaScript, NPM and Databases is needed
MongoDB is required to be up and running and a Yeoman generator is used to generate the application. Although the prompt based start-up in the command line helps you a lot, it still can be hard for someone inexperienced with NPM and Yeoman.
Con It's hard for front-end developers with no MVC experience setting up views
Keystone follows MVC practices in managing routes, views and templates. Back-end developers with experience in working with MVC frameworks will find themselves at ease since the beginning, but developers who work on the front-end only will have a hard time finding what they are supposed to do to set up templates and such.
Con It does not have a built-in roles system
Although registering a new user is very easy, there is not any roles system out-of-the-box. There is only a check box "Access keystone" which gives a user full administrative power. Adding different kind of users is only possible by editing the user data model.