Version 0.4 of Ghost, the lightweight Node.js blogging platform, went live this month. Some of the more interesting features include support for static pages, a new way to quickly edit posts by appending /edit to the URL, support for date-based permalinks (e.g. /2014/01/25/example-post instead of /example-post), support for uploading SVG images, and the ability to put Ghost in a subdirectory.
With this update out of the way, we’re one closer to seeing the plugin API. That’s currently scheduled for version 0.5 (to be released sometime this spring).
The ability to extend Ghost is, in my opinion, what will make it a truly excellent platform. I really like the editor—which is reason enough to start using Ghost—but I can’t switch any of my sites over (not even my personal blog) until it’s possible for me to add in some features Ghost is missing. I do a bit of linkblogging on my personal blog (Daring Fireball style, with headlines that link to external sites), and Ghost doesn’t offer the ability to do that out of the box. I also have a couple posts on the blog that feature image galleries, originally with WordPress and later through my Jekyll plugin.
Back in the earlier days of blogging, things were different. Most of the popular content management systems that blogs ran on were static page generators, like 
I have asked myself that question countless times. You too have probably spent hours trying to think up a concept for a post on your blog. Inspiration comes and goes. It’s the curse of the writer.
Disabling Comments on Old Posts, or How to Kill Discussion
May 1, 2012 by Matt | Posted in Blogging No CommentsGuess which posts on this site receive the most new comments every week. Older ones. Not the latest posts, but the ones that have stood the test of time and still have people looking.
The terms sometimes used to refer to posts that remain relevant, and bring in traffic, for years are “evergreen content” and “pillar content.” I have posts that are a few years old, are still the most popular in terms of traffic, and gain a couple new comments every month. Occasionally a spam comment will appear on those posts, but they’re outnumbered by legitimate comments, continuing a discussion that has been going on for a long time. Does it really make sense to put an end that, and frustrate readers who arrived a little late but still have questions to ask or opinions to voice, just to avoid a few spam comments Akismet happened to miss?
That seems like a wasted opportunity. Instead, you could update your evergreen posts to remain relevant, and add some links to more recent posts on the same subject. Build user engagement and keep the discussion going.
Smaller blogs, especially, can’t count on timely social media-driven traffic. They tend to succeed more with long-tail traffic from search engines. Obviously you won’t get very many comments at all if the form gets disabled just when a post is becoming popular…
Fortunately, there is a nice middle ground. Some posts, especially ones that have attractive keywords in them but become less relevant later down the line, rarely see legitimate comments but are magnets for spam. I have a couple that seem to get a handful of spam messages that sneak past Akismet every week, but never have real comments anymore. With those kinds of posts, you could probably toggle the discussion off without inconveniencing anybody but spammers.