Ghost vs WordPress

Overview

WordPress

Stacks99.3K

Followers41.4K

Votes2.1K

GitHub Stars20.6K

Forks12.9K

Ghost

Stacks518

Followers506

Votes219

GitHub Stars51.1K

Forks11.1K

Ghost vs WordPress: What are the differences?

Ghost: Just a blogging platform. Ghost is a platform dedicated to one thing: Publishing. It's beautifully designed, completely customisable and completely Open Source. Ghost allows you to write and publish your own blog, giving you the tools to make it easy and even fun to do; 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.

Ghost and WordPress can be primarily classified as "Self-Hosted Blogging / CMS" tools.

"Beautiful" is the primary reason why developers consider Ghost over the competitors, whereas "Customizable" was stated as the key factor in picking WordPress.

Ghost and WordPress are both open source tools. Ghost with 30.2K GitHub stars and 6.52K forks on GitHub appears to be more popular than WordPress with 12.6K GitHub stars and 7.64K GitHub forks.

According to the StackShare community, WordPress has a broader approval, being mentioned in 5281 company stacks & 1353 developers stacks; compared to Ghost, which is listed in 60 company stacks and 39 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on WordPress, Ghost

Kamaldeep

CEO at Zhoustify Agency

Nov 13, 2020

Decided

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.

69.2k views69.2k

Comments

Krish

Nov 19, 2021

Needs adviceon

Next.js

Firebase

WordPress

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.

293k views293k

Comments

Xander

Founder at Rate My Meeting

Mar 30, 2020

Decided

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.

243k views243k

Comments

Detailed Comparison

WordPress	Ghost
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.	Ghost is a platform dedicated to one thing: Publishing. It's beautifully designed, completely customisable and completely Open Source. Ghost allows you to write and publish your own blog, giving you the tools to make it easy and even fun to do.
Flexibility;Publishing Tools;User Management;Media Management;Full Standards Compliance;Easy Theme System;Extend with Plugins;Built-in Comments;Search Engine Optimized;Multilingual;Easy Installation and Upgrades;Importers;Own Your Data	An intuitive, minimal editor; Ultra-fast content management; All SEO features built-in natively; Native desktop & mobile apps; Publish once, distribute everywhere; Headless CMS with Node.js REST APIs; Over 19x faster than WordPress; Secure & independently audited; Custom theme or any JAMstack front-end
Statistics
GitHub Stars 20.6K	GitHub Stars 51.1K
GitHub Forks 12.9K	GitHub Forks 11.1K
Stacks 99.3K	Stacks 518
Followers 41.4K	Followers 506
Votes 2.1K	Votes 219
Pros & Cons
Pros 418 Customizable 369 Easy to manage 357 Plugins & themes 259 Non-tech colleagues can update website content 248 Really powerful Cons 13 Hard to keep up-to-date if you customize things 13 Plugins are of mixed quality 10 Not best backend UI 2 Complex Organization 1 Do not cover all the basics in the core	Pros 45 Beautiful 35 Fast 29 Quick/simple post styling 20 Live Post Preview 20 Open source
Integrations
ClickTale Clicky Disqus Formstack GoSquared HipChat Hipmob KickoffLabs KISSmetrics LiveChat	No integrations available

What are some alternatives to WordPress, Ghost?

Drupal

Drupal is an open source content management platform powering millions of websites and applications. It’s built, used, and supported by an active and diverse community of people around the world.

Strapi

Strapi is100% JavaScript, extensible, and fully customizable. It enables developers to build projects faster by providing a customizable API out of the box and giving them the freedom to use the their favorite tools.

Wagtail

Wagtail is a Django content management system built originally for the Royal College of Art and focused on flexibility and user experience.

OctoberCMS

It is a Laravel-based CMS engineered for simplicity. It has a simple and intuitive interface. It provides a consistent structure with an emphasis on reusability so you can focus on building something unique while we handle the boring bits.

Twill

Twill is an open source CMS toolkit for Laravel that helps developers rapidly create a custom admin console that is intuitive, powerful and flexible.

ProcessWire

ProcessWire is an open source content management system (CMS) and web application framework aimed at the needs of designers, developers and their clients. ProcessWire gives you more control over your fields, templates and markup than other platforms, and provides a powerful template system that works the way you do

Typo3

It is a free and open-source Web content management system written in PHP. It can run on several web servers, such as Apache or IIS, on top of many operating systems, among them Linux, Microsoft Windows, FreeBSD, macOS and OS/2.

Directus

Let's say you're planning on managing content for a website, native app, and widget. Instead of using a CMS that's baked into the website client, it makes more sense to decouple your content entirely and access it through an API or SDK. That's a headless CMS. That's Directus.