📄from ghost to github pages
Ghost was great. Simple, fast, super(I mean super) easy to set up, rich with features and everything. It has that nice CMS vibe like WordPress but without that slow, bloated feeling(Why would I want 50+ plugins only to write something that probably no one will actually read?). And self-hosting is fun. But it’s not so fun when you only host 2 blogs which you barely write anything on. I do my fun stuff mostly on my Raspberry Pi now and the extra server seemed kinda redundant.
So I decided that it’s time to move. I wanted a clean start, so I didn’t care about post/data migration at all(although that would’ve been a breeze with Github Pages). What I needed was quite simple: plus the customizability, minus the laborious set-ups.
Now, I’m no developer. I’m just a hobbyist. So when I first introduced Github Pages(and Jekyll), I had no clue how it works and it got off the list pretty much instantly. Understanding Git was(and is) challenging, let alone Github Pages itself. But over time, I got a little comfortable with Github and I thought why not give it a try.
Turned out quite nice! I forked riggraz/no-style-please, made some design changes, and voila, there was what I think the most beautiful blog I can imagine. The only thing I miss is the native multi-language feature. But in a way, Ghost was not the best multilingual CMS I know of. Besides, I barely write in Korean, at least on my blog, so it didn’t bother me that much. It is blazingly fast, clutter-free both design and code-wise, uses Git to manage everything. What’s more to want? If I’m feeling lazy, I can also use 3rd party services like forestry. Plus I fell in love with markdown while tinkering with Jekyll.
Github pages. It’s cool. I don’t see any reason you should not use it. Surely if you make money out of writing, Ghost seems promising. But if you just want to write things and want them on the internet, Github Pages seems more than enough.