Replace Ghost
A blog and newsletter platform that usually ends up on a separate subdomain from the product it markets.
Why teams move off Ghost
Ghost is a fine publishing platform on a subdomain, which is exactly the problem: blog.yourapp.com and yourapp.com/blog are not the same asset to a search engine.
What you give up
Newsletter delivery and paid memberships, which none of the CMS engines include.
This directory says so when an engine only covers part of the job. A replacement that needs a caveat is still worth knowing about — it just should not surprise you in week three.
2 Rails engines that replace Ghost
-
ActiveCanvas
Covers the core of ContentPages and publishing. Newsletter delivery is not part of it.
Ghost → active_canvas
No ratings yet → -
Comfortable Mexican Sofa
Covers the core of ContentPages and content management. Newsletter delivery is not included.
Ghost → comfortable_mexican_sofa
No ratings yet →
Questions
- Is there an open-source alternative to Ghost for Rails?
- Yes — ActiveCanvas and Comfortable Mexican Sofa. Both mount into an application you already run, so there is no second deployment and no second database.
- What do I give up by replacing Ghost?
- Newsletter delivery and paid memberships, which none of the CMS engines include.
- How do I replace Ghost in a Rails app?
- Add active_canvas to your Gemfile, mount it in config/routes.rb at /canvas, and run its migrations. The whole integration is two lines and a migration.
- How much does replacing Ghost save?
- Ghost is priced from $9/mo. The engines here are open source, so the cost becomes the time to mount one and the resources it uses inside your existing application.
Same category