Need advice about which tool to choose?Ask the StackShare community!
KeystoneJS vs WordPress: What are the differences?
KeystoneJS: Node.js CMS and web application platform built on Express and MongoDB. Keystone is the easiest way to build database-driven websites, applications and APIs in Node.js; WordPress: A semantic personal publishing platform with a focus on aesthetics, web standards, and usability. The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family.
KeystoneJS and WordPress can be categorized as "Self-Hosted Blogging / CMS" tools.
Some of the features offered by KeystoneJS are:
- Express.js and MongoDB
- Dynamic Routes
- Database Fields
On the other hand, WordPress provides the following key features:
- Publishing Tools
- User Management
"Out-of-box tools and basic services" is the primary reason why developers consider KeystoneJS over the competitors, whereas "Customizable" was stated as the key factor in picking WordPress.
KeystoneJS and WordPress are both open source tools. It seems that KeystoneJS with 14.6K GitHub stars and 2.35K forks on GitHub has more adoption than WordPress with 12.6K GitHub stars and 7.69K GitHub forks.
According to the StackShare community, WordPress has a broader approval, being mentioned in 5304 company stacks & 1387 developers stacks; compared to KeystoneJS, which is listed in 11 company stacks and 5 developer stacks.
Hi Stackers, We are planning to build a product information portal that also provides useful articles and blogs. Application Frontend is going to be built on Next.js with Authentication and Product Database helped by Firebase. But for the Blog / Article we are debating between WordPress/GraphQL plug-in or Strapi.
Please share your thoughts.
We eat our own dog food at Strapi and the Strapi blog is actually a good example of a blog that you can make using Strapi. We built the blog using the Dynamic Zone feature of Strapi, allowing us to stack different components with relation to categories and blog posts. The blogpost collection type includes an SEO component, relations to Authors and Categories and all that's needed to add content easily.
I would recommend that you create a firestore collection for all the blogs that you use. You do not need Graph QL, wordpress or Strapi because you are using next.js. Just use ISR(incremental static regeneration) to make a blog.
Tried to use for my mobile app: 1- user role sucks, you have a max of 3 roles users 2- cannot create a user by passing only email, username and passowrd is required 3- cannot interate with users schema 4- plugins page sucks 5- internalizations is not clear, date time is not translated 6- it's not responsive
DIRECTUS is on another level guys, you should try it. Github stars aren't.
I usually take a slightly different tack because the technical level of people I usually am dealing with is lower. I tend to be pitching to decision makers and not tech people. A bit of my standard answer is below.
Wix and Squarespace are proprietary systems meant for unsophisticated users who want to build their own websites quickly and easily. While they are good for that specific use case, they do not offer any way to move beyond that if your needs arise. Since they are proprietary closed systems if you need something more advanced at some point your only option is to start over.
WordPress is an Open Source CMS that allows much more freedom. It is not quite as simple to setup and create a new site but if you are talking to me then you are not looking to build it yourself so that is really a non-issue. The main benefit of WordPress is freedom. You can host it on virtually any decent web hosting service and since it uses PHP and MySQL you can have virtually any developer take over a project without problem.
I believe in open source because of that freedom. It is good for me as a developer and it is good for my clients. If something were to happen to me or my company you would have no problem finding another qualified WordPress developer to take over the site in a totally seamless fashion. There would be no need to start from scratch.
Additionally the extensible nature of WordPress means that no matter what your future needs, WordPress can handle it. Adding things like e-commerce and custom quoting systems are just two examples of advanced solution's that I have added to WordPress sites years after they were first built.
WordPress is used by tiny one person businesses all the way up to major websites like the NY Times and I think it is right for this project as well.
So many choices for CMSs these days. So then what do you choose if speed, security and customization are key? Headless for one. Consuming your own APIs for content is absolute key. It makes designing pages in the front-end a breeze. Leaving Ghost and Cockpit. If I then looked at the footprint and impact on server load, Cockpit definitely wins that battle.
10 Years ago I have started to check more about the online sphere and I have decided to make a website. There were a few CMS available at that time like WordPress or Joomla that you can use to have your website. At that point, I have decided to use WordPress as it was the easiest and I am glad I have made a good decision. Now WordPress is the most used CMS. Later I have created also a site about WordPress: https://www.wpdoze.com
Pros of KeystoneJS
- Out-of-box tools and basic services7
- Large community3
- Great schema-based auto-generated admin interface2
- Great CMS and API platform2
- Great sandbox to play with nodejs2
- Great integrations1
- A great MEAN stack1
- Detail documentations and tutorials1
- Rapid development1
- Open source1
- "easy setup", "uses mongodb"1
- Fast on V81
- Similar to wordpress1
- Fast growing community cms framework1
- Great culture1
Pros of WordPress
- Easy to manage364
- Plugins & themes352
- Non-tech colleagues can update website content258
- Really powerful246
- Rapid website development144
- Best documentation77
- Product feature set44
- Custom/internal social network35
- Open source16
- Great for all types of websites8
- Huge install and user base6
- I like it like I like a kick in the groin5
- It's simple and easy to use by any novice5
- Perfect example of user collaboration5
- Open Source Community5
- Most websites make use of it5
- API-based CMS4
- Easy To use3
- <a href="https://secure.wphackedhel">Easy Beginner</a>2
Sign up to add or upvote prosMake informed product decisions
Cons of KeystoneJS
Cons of WordPress
- Plugins are of mixed quality12
- Hard to keep up-to-date if you customize things12
- Not best backend UI9
- Complex Organization2
- Great Security1