Jul 29, 2017 | Comments
I recently started learning how to use emacs, which is a text editor and a Lisp interpreter. During my quest for resources, I came across a number of developers and their blogs. Since I’m always intrigued by what sort of tools developers use to make their blogs, I did a little snooping. A shocking number of people who didn’t use WordPress as their blogging platform opted for flat files instead.
Now I had dabbled a little bit in static pages before with BoltWire but ultimately abandoned it to go back to WordPress. I think where I went wrong with BoltWire was that it simply did not have a big enough community (although they are an extremely dedicated community) to keep me reassured that I had made the right choice.
However, I know flat files in general is a real and upcoming thing. Since I’m planning to use emacs and Markdown files as my main way of documenting things, it would be easy to use it in my blogging as well.
So my main reasons for switching to a flat file system:
WordPress was giving me so much trouble when it came to security. Yes, Jetpack did help in reducing spam and MySQL doesn’t randomly stop working anymore but you have to admit that using WordPress on a Digital Ocean server makes you a target.
Yes, WordPress does have versioning for content however it would be much easier to have version control for settings, themes, etc. over the WordPress kind.
I don’t need everything that WordPress offers and honestly sometimes I feel like it might be a bit overkill. Since the server I’m on has limited RAM and disk space, I need to be careful about the amount of resources I use. It helps that I don’t have many visitors to begin with but still!
Faster loading times
While I’m unsure if this is too much of a concern for me but loading times do make me a bit worried. Fetching from a database can be quite slow.
I want a more future proof blogging system
There are options to export your content into XML files in WordPress however it can’t beat readable Markdown, which many static file systems use. The fact that everything is file based is future proof in itself. Migrating from one server to the other wouldn’t be too much hard work.
- What comment system to use
I do not like Disqus. I dislike the fact that I have to register for yet another site and people can’t click on my name on a comment and go directly to my website. I also don’t like the fact that the comments don’t stay on my server. I want to be able to have my comments.
- Learning curve
This would be a little more technically involved at first to get everything installed, just due to the nature of it not being a one-click install.
- So many choices!
There is no shortage of flat file systems out there. Like I’ve said, I’ve dabbled in BoltWire before and wiki systems but it’s so hard to find one that will work for you when there’s a breadth of options.
One of the main frameworks I’ve been looking at is Hugo which is used by Baty.net, Modern Emacs, kieranHealy.org, but she’s a girl…, and more. I am very attracted to this option because it seems like it could work pretty well with an emacs workflow.
Thankfully, I finally recovered my previous website, erzadel.net and now have access to my old blog posts. I’ll be tinkering with that this weekend and try to have a clone of my old blog up and running on my local machine. We’ll see how it goes!