A bit about the tech stack: I'm currently using Jekyll and Github Pages. The combination of the two let me spin up a new, reasonably clutter-free blog in very little time. In fact, I spent more time writing that first post, rather than fiddling with a framework1.
I chose this route because I like owning my data. I always have a copy of the repository, I can check out the Jekyll runtime and run it anywhere I choose.
Why would I do this if I'm only traveling with a tablet, you ask? This is where the benefit of using Github comes in. I can create new files with a relatively simple file format. The repository web view allows one to create and edit files. Using the
_drafts feature of Jekyll, one can edit the file (using the Github built in editor for layout previews), and then rename it and move it to
_posts. Everything can be done from the browser.
Posts are written using the Markdown format (with added bit of header information for organization, template choice etc). Markdown's syntax is generally so clean and understandable in plain text that I've started using it in all my own notes. I'm still looking for a good android file editor - Writer looks promising - I'll also need some offline writing tools.
Granted, the quick spin up time, coupled with the fact that I'm leaving tomorrow has left the layout side of things a little plain. In fact, it's the default template with a few minor modifications. Heck, you can look at the repository itself and see what I've changed.
Since lightweight is the name of the game right now, this stack definitely fits the bill.