Static websites are cool (and a brief introduction)

Hello {every,no-}one,

Writing the first entry for every blog is much more difficult than I first thought (having to rewrite this first sentence for the tenth time proves this to me). With an audience consisting of literally just one person, yourself, it's a bit like shouting into the void. Whilst it can clear your head, allowing you to put your thoughts in order, the notice of nobody hearing what you said makes it a bit sad. I want to inform the world of subjects I find interesting, related to anything computers and/or activism. I'd like to write short tutorials, informing the readers with my (of course very important and world changing) thoughts and have a big impact on the industry. This will be the most informative blog the internet has ever seen, if I ever get around of publishing my first real entry and stop rewriting there ramblings for the nth time.

The most fitting subject I could come up with is the tool I'm using to publish this blog. I know, this is a pretty sad first subject for a blog with the big ambitions I have. But with me not knowing it existed until a few days ago and finding it pretty impressive already, I'd like to give it a shoutout, albeit into the void for now, and probably forever…

A little bit of a backstory

I've been a software developer since 2012, that's when I started studying Computer Engineering at University. Web development has always been my weak point. I haven't touched web development since secondary school (2010). Developing basic (of course static) webpages describing my late cats, family, friends and my hobbies with HTML, frames and the few cool JavaScript animations are all I've ever done. At university I tried to avoid the webdev parts of projects because I thought it wasn't interesting enough. This is something I regret to this day, it's something I admire in the skillsets of a few of my colleagues, being able to condure up a quick dashboard to demo impressive improvements and feature additions in our platform is great when presenting your, sounds-impressive-but-what-does-it-do projects that take weeks to complete. I eventually gave up presenting some of the stuff because inventing ways to demonstrate the workings was more work than writing and testing the code itself.

Searching the web for tools to use

First I considered Wordpress for my blog, I could host it myself, I've used it recently (in 2011, I have a broad meaning for the word recently) and a lot of nice themes are available. Thinking that would not be the way to learn something new and wondering if I even needed a huge CMS to host my simple blog I considered creating a static blog, I wanted to learn how to use NodeJS, a bit of HTML and some CSS. I opened Sublime Text, created the folder ~/Projects/blog and started working on my first index.html in 8 years. After just a few basic elements; <header>, <title> and <body> I started wondering if this was the way to go, I had a few ideas in mind, a few subjects I wanted to write tutorials/points of view on. The thought of standing on the brink of a project that would take weeks to complete the first presentable verison of got me thinking.

What if I could write a blog in Markdown? I know the language pretty well, at least I'd like to think so. Writing those, at first pesky, files for every project became quite intuitive. Writing a few how-to guides in markdown at work was also becoming straightforward. Already envisioning writing a markdown file, committing the file and doing a simple git push would result in a new blog entry.

In my head this was already looking fantastic, now I only had to find the right tools to do so…


Continue writing here, after re-reading and writing

/ "MSDOS didn't get as bad as it is      \
| overnight -- it took over ten years of |
| careful development." (By              |
\              /
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||