Ghost Apps - Power to the People



I’m sure that I’m not the only one that thinks that this could be the major change for Ghost and might be the thing that will make Ghost a lot more popular.

Right now we have some Apps that are developed by Ghost organisation. There is no way to create a custom App without changing the core … and we all know that we should not touch the core.

There is a v0.0.2 implemented but I’m pretty sure it doesn’t work anymore. Even if it works it’s still pretty complicated to implement and very basic (v0.0.2).

Apps would be an amazing feature because it gives the developers the power to create amazing features that others can benefit from.

Apps offer unlimited possibilities.

I simply can’t wait for this. :slight_smile:

Conditionals in handlebars
"Hooks" for developers
New apps integrations
When will sitemap generator be triggered?

I would like to second this. The current app implementation is a nice start but falls down on the permissions side. Is there any plan on the road map for rekindling this effort? If the community works to implement some of the missing functionality, what is the likelihood of it being integrated in to Ghost?

The ability to appropriately seed a context with permissions from an app along with the existing ability to add custom routes to Ghost would allow for some highly requested items to be externalized and customized (contact forms, Zapier type integrations, etc.) for individual sites without muddying the core code base.

As mentioned, something like a contact form requires touching the core and re-integrating those changes after any updates.


In fact even simple helpers would be great to have at this stage but apps would cover that too.


Deprioritizing Ghost’s independent developer community is by far the greatest risk to the future growth of the platform. There is clearly no shortage of talent willing to contribute to Ghost’s core offering, but as years slip by it seems that pool of talent is fading. As true functional contribution feels more and more futile, much of the talent we have left seem be those bent on mass producing the same cliché bootstrap themes.

I love Ghost, and it would not be crazy to say I owe current engineering career to the things I learned from dissecting the platform. That said, the longer the community waits to shine, the sooner they realize that they too can build an express app which serves content.


I might be rambling here :slight_smile: but I was looking at the Apps section of my blog and I was wondering if it doesn’t make sense to add here several other standard app integrations that people might frequently use, such as:

  • Google Analytics & Tag Manager
  • GitHub (for people to manage and modify their themes or integrate their projects - I think this would be something cool to have for a theme, use it from github and sync your changes with the upstream theme updates)
  • <insert other sexy, cool and popular app that people use frenquently here)

Thinking about how these usually work it seems to be a “simple” authentication integration via the app auth api.


Apps haven’t really been fleshed out at all. You have to do some hackery in the database to even allow adding new apps. I documented it in the old slack channel many moons ago.

TL;DR: Not worth the effort until they finalize the spec on app integration on the Ghost side.


Hello guys,

Thinking on how busy the core team is, and how our requested features maybe are not like ideal for the future of “Ghost” as a project but at the same time they are a NEED for us (as Ghost users/developers), what do you think about implementing hooks?

This way, allow developers to build their own “logic” around the core without having to affect the actual Ghost core. The ideal scenario is to implement hooks (events) Before and After each “update” (create, update, delete) is performed; and this should be available for any kind of “content” that a Ghost user modify through the Ghost-Cli, API or Admin like, but not limited to: posts, settings, uploads, etc.

What do you guys think about it? I’m seriously starting to move a lot of my personal and customers projects from WP and custom CMSs to Ghost so thinking as Developer I see a lot of features that I can build for my customers and the open source community but are not a good fit to be a “must” in a core as the use case of my ideas are for limited scenarios so it would worth to build a solution as “an addon” to the core.

That said, I can just wait for your thoughts :smiley:


Hooks are an interesting idea! A problem I often have with authors is they tend to leave important things blank when posting, such as SEO metadata or tags. It would be cool to invoke a script when posts are published to clean up the nonsense as it goes live.

Right now I’ve using a few workarounds that help a lot. For instance, I’ve used the Zapier integration to send me a twilio SMS when authors save a draft, which allows me to intercept these things head-on.

Chances are I’ll stick to Zapier for now and write custom scripts to clean things up at a database level as I wouldn’t expect this kind of niche use to make it to the top of any backlogs soon.