Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWix vs KeystoneJS
When comparing Wix vs KeystoneJS, the Slant community recommends KeystoneJS for most people. In the question“What are the best web content management systems?” KeystoneJS is ranked 6th while Wix is ranked 12th. The most important reason people chose KeystoneJS is:
Keystone comes with an auto-generated Admin UI, which makes things very easy for any task that can be completed using Keystone. In any way Keystone is used, the Admin interfaces saves a lot of time and makes any job easier.
Specs
Question Ranking
Pros
Pro Functionality can be extended with community plug-ins
Wix has an add-on store, called the App Market, that includes community developed bits of functionality (such as comments, calendars and integrations with third-party services) that you can add to your site. The store includes both free and paid add-ons.
Pro Straightforward drag & drop interface
There's a selection of elements you can choose from in the sidebar that you can drag and drop into the page and edit. There are common elements such as text, images and buttons as well as less common elements such as blog or online store. All elements can be adjusted to some extent to fit your needs. For example, you can change things like the font, weight and style of text and even crop, adjust colors and apply filters to images.
Pro Personalized templates
Wix comes with various kinds of templates based on the users genre and needs, ranging from personal, blog, club, portfolio to commercial.
Pro Wix Code lets you add custom code and backends to your WYSIWYG site when needed
This means you can add custom interactions and API's to your site when needed, but do most of the editing in a GUI. This helps you avoid the need to redo an entire site if you need custom interactions. Also dead easy to connect a database and have dynamic components based on CMS updates.
Pro Great support
Pro Out-of-the-box Admin UI
Keystone comes with an auto-generated Admin UI, which makes things very easy for any task that can be completed using Keystone. In any way Keystone is used, the Admin interfaces saves a lot of time and makes any job easier.
Pro Keystone comes with Express already configured
Express comes out of the box already configured from Keystone or it can be treated like any other Express Middleware.
Pro Keystone has easy form processing
Using the data models defined by the developer, Keystone can validate forms automatically without any more setup. Form validation doesn't get easier than this.
Pro Many cool features
Great CMS with auto-generated admin, schemas...
Pro Easy to install and use
KeystoneJS is very easy to install and use.
Pro Easy email management features
With Keystone it is easy to set up an email management system for an application. It has template-based emails and it's also integrated with Mandrill (Mailchimp's transaction email sending service)
Pro Keystone uses MongoDB through Mongoose
Keystone allows the usage of MongoDB since it comes with Mongoose, the most popular ODM for node and Mongo, this means that anything that is built using Mongo can be built with Keystone.
Pro Numerous amounts of templating engines are supported
Keystone supports almost all templating engines out there. Although it uses Jade directly after a fresh install and it points to using it further, other template engines can be installed and used instead.
Pro Effective session management
Keystone has advanced and effective session management and authentication features. Logging in and signing up is easy and it even has password encryption out of the box.
Cons
Con Generated html is very bad
A lot of duplicated css, a lot of absolute positioning.
Con Hard to migrate away
There isn't an option to self-host the site, but neither should there be a need to.
Con Dated templates
Con Unpleasant sign-up process
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.
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 No auto-reload and no good support for RDBMS
Does not have auto-reload in its backend.
Hard to debug.
Features found in document, absent in code.
No enough support to PostgresQL, no automatic migration
Con No default option to add pages in admin panel
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 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 Packaging externals libraries is tricky
Unless you want to import every JS.
