With the launch of Ghost 1.0 (the blogging software I use for this site), I'm going to attempt to get back into blogging.
On the backend, Ghost 1.0 is a lot better to manage. They have introduced a command line interface (CLI) that makes updating the software much more straightforward (previously this involved a manual, multi-step process that was subject to change and so tricky to script).
On the frontend, the default Casper theme is gorgeous and has basically all the design elements I've been wanting. I have used 3rd party themes before to get what I want, but the problem with these is that they quickly turn obsolete as the developer losses interest in keeping it up to date. This of course isn't an issue with the default theme. If I need to change anything, I can always fork it on GitHub and merge any upstream changes.
I had previous had comments on the site for each post, via a Disqus plugin. This really wasn't used very often and so I will probably not reinstate it. Plus it is something to be moderated (as all user input should be these days). I may just ask people to contact me on Twitter with any comments and if I receive a good one, could post it add the end of the post manually.
There is one issue that Ghost 1.0 hasn't got around to solving yet and that is using Chrome's native spelling and grammar checker. This is planned for in the future. That is why I am writing this on stackedit.io, as their Markdown editor does support said feature. I find the Chrome spell checker to be the best out there, no question. Especially if you switch on the "Ask Google for suggestions" options. This means it is always up to date with the latest words that are found on the web. This saves time looking up whether you've got a newfangled term quite right with a Google search. Google has already done it for you when you right-click to ask for suggestions.
So that's the news about Ghost 1.0 and my intention to blog more (and probably Tweet less).