What is Ghost? — Modern Publishing Platform Explained for Beginners
In this tutorial, you'll learn what Ghost is — a modern open-source publishing platform built on Node.js — and how it differs from WordPress with its streamlined approach to content creation, memberships, and newsletters.
What You'll Learn
- The origin story of Ghost and why it was created
- How Ghost differs from WordPress in philosophy and architecture
- Ghost's core features: Koenig editor, memberships, newsletters, and API
- The Ghost business model: Ghost(Pro) hosting vs self-hosted
- What kinds of websites you can build with Ghost
- The Ghost community, marketplace, and ecosystem
Why It Matters
Choosing the right platform for content publishing is a strategic decision. WordPress powers 43% of the web but requires plugins for membership, newsletters, and SEO — each plugin adds complexity, security risk, and maintenance burden. Ghost was purpose-built to solve these specific problems without the plugin overhead. For creators, publishers, and businesses that prioritize clean publishing, membership revenue, and newsletter growth, Ghost offers a focused alternative that does one thing exceptionally well.
Real-World Use
A freelance journalist wants to build a paid newsletter about cybersecurity analysis. She needs a clean reading experience, a monthly subscription tier, automated newsletter delivery to subscribers, and a public archive of free articles. With WordPress, she would need WooCommerce or a membership plugin, plus a newsletter plugin like Mailchimp, plus a caching plugin, plus regular security maintenance. With Ghost, she installs one platform, configures Stripe for payments, connects Mailgun for email, and has a complete membership+newsletter site running in under an hour.
Learning Path
flowchart LR A["What is Ghost?
You are here"]:::current A --> B["Ghost Architecture"] B --> C["Ghost CLI"] C --> D["Ghost Editor"] D --> E["Ghost Installation"] classDef current fill:#38bdf8,color:#0f172a,stroke-width:2px
What is Ghost?
Ghost is an open-source content management system built with Node.js on the backend and Ember.js on the admin frontend. It launched in 2013 after a successful Kickstarter campaign by John O'Nolan (former WordPress UI lead) and Hannah Wolfe. The goal was simple: create a publishing platform focused entirely on content, free from the bloat of general-purpose CMS platforms.
Think of Ghost as a purpose-built tool, like a chef's knife compared to a Swiss Army knife. WordPress is the Swiss Army knife — it can do almost anything, but you need to open different tools (plugins) for each job. Ghost is the chef's knife — it does fewer things, but it does them exceptionally well. You do not need plugins for newsletters, memberships, or SEO because those are built into the core.
How Ghost Works
When a visitor loads a Ghost site:
flowchart LR A["Browser requests URL"] --> B["Node.js server (Ghost)"] B --> C["Route matching"] C --> D["Content query (SQLite/MySQL)"] D --> E["Handlebars template render"] E --> F["HTML sent to browser"] style B fill:#38bdf8,color:#0f172a style C fill:#38bdf8,color:#0f172a style D fill:#38bdf8,color:#0f172a style E fill:#38bdf8,color:#0f172a
- The browser sends a request to your Ghost site URL.
- The Node.js server receives the request and routes it based on the URL pattern.
- Ghost queries the database (SQLite for development, MySQL for production) for the requested content.
- The Handlebars template engine renders the content into HTML using your active theme.
- The completed HTML page is sent back to the browser.
The Origin Story
Ghost began as a frustration with WordPress. John O'Nolan, who led the WordPress UI team, felt the platform was becoming too complex for its original purpose. The WordPress admin dashboard was bloated, the editor was heavy, and publishing a simple article required navigating layers of settings.
The Kickstarter campaign in April 2013 raised over 196,000 pounds — far exceeding the 25,000 pound goal. This validated what many content creators felt: there was a need for a simpler, more focused publishing platform.
Key milestones:
- 2013: Ghost launches on Kickstarter, raises 196k pounds
- 2014: Ghost 0.4 release with the first public API
- 2015: Ghost 0.7 introduces apps and integrations
- 2016: Ghost 1.0 major rewrite with Ember.js admin
- 2018: Ghost 2.0 introduces memberships and subscriptions
- 2020: Ghost 3.0 with the Koenig editor and card system
- 2022: Ghost 5.0 with revamped memberships and newsletters
- 2024: Ghost 5.x continues with performance improvements and API enhancements
As of 2026, Ghost 5.x is the current major version, with active development focused on memberships, the editor experience, and headless CMS capabilities.
Ghost vs WordPress: Core Differences
| Feature | Ghost | WordPress |
|---|---|---|
| Language | Node.js (JavaScript) | PHP |
| Database | SQLite / MySQL | MySQL / MariaDB |
| Templating | Handlebars | PHP (blocks in FSE) |
| Editor | Koenig (card-based) | Gutenberg (block editor) |
| Memberships | Built-in | Plugin required |
| Newsletters | Built-in | Plugin required |
| Plugins | No plugins (apps deprecated) | 60,000+ plugins |
| Themes | Handlebars-based | PHP/PHP+HTML |
| SEO | Built-in | Plugin required (Yoast, etc.) |
| REST API | Built-in Content + Admin API | REST API (core since 4.7) |
| Hosting | Ghost(Pro) or self-hosted | WordPress.com or self-hosted |
The most significant difference is the plugin model. WordPress relies on plugins for almost every feature beyond basic publishing. Ghost intentionally has no plugin system — all features are either built into the core or accessed via the API.
This means Ghost sites are generally faster, more secure, and easier to maintain than WordPress sites, but they are also less customizable. If Ghost does not have a feature built in, you cannot simply install a plugin to add it.
Core Features
The Koenig Editor
The Koenig editor is Ghost's card-based editor. Instead of a single text area with shortcodes, you build content by adding cards — text, images, galleries, embeds, markdown, callouts, and more. Each card is a self-contained content block that you can reorder, edit, or delete independently.
Built-in Memberships
Ghost has a complete membership system built into the core. You can:
- Create free, paid, and premium membership tiers
- Accept payments through Stripe
- Gate content behind membership levels
- Send newsletters to members
- Track member analytics
No plugins needed. No third-party services (except Stripe for payments and Mailgun for email).
Newsletters
Ghost doubles as a newsletter platform. When you publish a post, you can send it as an email to your subscribers. Ghost handles:
- Email design and formatting (using your theme styles)
- Subscriber management
- Open and click tracking
- Sending through Mailgun (or your own email service)
Content API and Admin API
Ghost provides two REST APIs out of the box. The Content API is public and read-only — it serves your posts, pages, tags, and authors to any client. The Admin API is authenticated and allows full CRUD operations. This makes Ghost a natural headless CMS — you can use the API to fetch content into a React, Vue, or Next.js frontend.
What You Can Build with Ghost
Ghost is purpose-built for content-driven websites:
- Blogs and publications: Clean, fast-reading experience with no distractions
- Paid newsletters: Subscription-based content with Stripe payment processing
- Membership sites: Tiered access to premium content
- Documentation sites: Clean typography and fast page loads
- Portfolio sites: Content-first presentation of work
- Company blogs: Professional publishing with team collaboration
- Course platforms: Gated lessons with membership tiers
- Hybrid free/premium sites: Free articles to attract readers, premium content for revenue
Ghost(Pro) vs Self-Hosted
Ghost offers two deployment options:
Ghost(Pro)
Managed hosting by the Ghost Foundation. Prices start at around $9/month for a basic plan. Benefits include:
- One-click setup, no server management
- Automatic updates and backups
- Built-in CDN and caching
- Email delivery included (no separate Mailgun setup)
- Official support
Self-Hosted
You install Ghost on your own server (VPS, Docker, or local). Benefits include:
- Full control over configuration
- Lower cost for high-traffic sites
- Custom infrastructure and integrations
- No monthly platform fee (just hosting costs)
The trade-off is operational complexity. Self-hosted Ghost requires Node.js knowledge, server management, and regular maintenance.
The Ghost Ecosystem
- Ghost(Pro): Official managed hosting at ghost.org
- Ghost Marketplace: Themes and integrations at market.ghost.org
- Ghost Forum: Community support at forum.ghost.org
- GitHub: Open-source development at github.com/TryGhost
- Docs: Official documentation at ghost.org/docs
Common Mistakes
Treating Ghost like WordPress: Beginners expect Ghost to work with plugins like WordPress. Ghost has no plugin system. If you need custom functionality, you use the API or build a custom integration. Trying to find a "Ghost plugin" for every feature leads to frustration.
Choosing Ghost for the wrong project: Ghost is a publishing platform, not a general-purpose CMS. It does not have e-commerce capabilities, forums, user-generated content, or a page Builder. If you need a corporate website with complex content types, or a full online store, WordPress or Drupal may be better choices.
Ignoring the membership features: Ghost comes with a complete membership system, but beginners sometimes set up third-party membership solutions that complicate their setup. Before adding external tools, explore what Ghost already provides.
Underestimating Node.js hosting requirements: Ghost runs on Node.js, not PHP. Many shared hosting plans do not support Node.js. You need a VPS or a Node.js-compatible hosting provider. Check hosting requirements before choosing Ghost.
Neglecting the email setup: Ghost uses Mailgun for newsletter delivery. Setting up Mailgun requires DNS configuration (DKIM, SPF, MX records). Beginners sometimes skip this and wonder why their newsletters land in spam folders.
Practice Questions
What problem did Ghost set out to solve that WordPress did not address? Answer: Ghost was created to provide a streamlined, focused publishing experience without plugin bloat. The founders believed WordPress was becoming too complex for its original purpose as a publishing platform, and that content creators needed a tool that prioritized writing, memberships, and newsletters without requiring dozens of plugins.
What is the main architectural difference between Ghost and WordPress? Answer: Ghost is built on Node.js (JavaScript), while WordPress is built on PHP. Ghost uses Handlebars for templating and SQLite/MySQL for data storage, while WordPress uses PHP templates and MySQL/MariaDB. Ghost has no plugin system, while WordPress has over 60,000 plugins.
What are the two deployment options for Ghost, and when would you choose each? Answer: Ghost(Pro) is managed hosting by the Ghost Foundation — choose it for simplicity, automatic updates, and built-in email delivery. Self-hosted gives you full control and lower costs at scale — choose it when you need custom infrastructure, have high traffic, or want to avoid monthly platform fees.
Challenge: Research three popular websites that use Ghost. Visit each site and identify which Ghost features they use: memberships, newsletters, Koenig editor cards, API-driven features, or custom themes. Write a one-paragraph analysis for each site explaining why Ghost was a good fit.
FAQ
Mini Project
Your task: Evaluate whether Ghost is the right platform for a hypothetical publishing project.
- Define the project: a technology news publication that will have free articles, a premium monthly newsletter ($10/month), paid members-only analysis pieces, and a public API for a mobile app.
- For each requirement, identify whether Ghost handles it natively or requires external services.
- Create a comparison table showing how Ghost, WordPress, and Medium each handle the requirements.
- Write a conclusion stating your recommendation.
This exercise trains you to evaluate publishing platforms against real requirements — a skill you will use constantly as a content strategist or web developer.
What's Next
Now that you understand what Ghost is and when to use it, you are ready to dive into how it works under the hood:
Continue to Lesson 2: Ghost Architecture — Explore the Node.js backend, Ember.js admin, database options, and Handlebars templating system.
Related lessons:
- Ghost CLI — Install and manage Ghost from the command line
- Ghost Installation — Set up Ghost on a production server
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro