Moving to Ghost

I'm on Ghost now!

Setting up my old website (on Jekyll) took me 30-40 minutes. All I had to was install Jekyll, fork and clone my theme, change some defaults, and run jekyll serve to serve it locally, and then Google a little bit to figure out how to host this on Github. Setting Ghost up took around two hours because I didn't know how to Digital Ocean, hadn't purchased this domain and I had to modify some stuff in this theme I didn't like. The last bit was mainly me dubiously editing .hbs files (still don't know what that extension means) and yolo-ing. So far, it's pretty clear to me that blogging is going to simpler and more pleasing on Ghost than it was on Jekyll. So the longer set up time was totally worth it.

  • I have a nice fancy UI where the blog posts I write in markdown are rendered in html in real time. Better than writing them on the command line, saving them, deploying my website locally and checking to see if I got it right.
  • Adding a new tab or static page or changing post metadata doesn't involve fiddling around with a yaml file anymore.
  • I can ssh into my DO droplet whenever to take my website down, test stuff locally, look at nginx error logs if something does wrong.
  • There's a nice separation of the content of my blog and its theme. Switching to a different Ghost theme is a simple matter of uploading a .zip file and activating my theme.

Off the top of my head, here's what I'd like Ghost to support.

  • Vim support in the editor. This is probably the thing I want most. Writing my posts in the terminal when I was on Jekyll wasn't the best but at least I could edit them in vim.
  • More social media fields (especially Github and Spotify)
  • Adding a subtitle to blog posts
  • Being able to preview blog posts in the actual font/style that they will be rendered in
  • Scheduling blog posts
  • A way to caption images (I know Markdown doesn't support it, but the less raw HTML I have to use in my blog posts, the better)
  • Some way of versioning blog posts and integrating them with Github.