Blog

And I "had" to change web site generator yet again. This time was rather weird. I didn't update NodeJS nor any package. Out of the blue the generation simply stopped working. Since I wasn't entirely happy with a few things of the previous generator, I decided to move on without attempting that much to fix the build process. Well, OK, I didn't try at all to fix it.

Recently I replaced my old SSD which, resulted in me re-installing everything. All seemed fine. When I started to write new content to the site and run the command to generate it in order to verify if the layout was correct, errors. Lots of them. Apparently the packages in my Metalsmith tool chain became broken with the newer Node version. So I run the command to update the packages, in the hopes it would fix. Unfortunately it didn't. And apparently it became worse because instead of spitting lots of error messages the process just froze.

Yes, I know this is not exactly related to game development, but I have to talk/rant about this. Markdown is a really nice tool! It makes writing texts for web pages a lot easier. Yet, if you are using it as part of static site generation chain, like this entire site, then it becomes impractical, unless you have very simple requirements.

That's not the case for this site. As an example, I created the "card" system to layout the tutorials, news and blog entries. Those cards require quite a bit of nested <div></div> contents. After searching a bit about this specific case, people suggested to directly use the tags within the markdown file. Well, honestly that already defeats the purpose of the format. But, there is another problem. Nesting tags like that will somewhat "force" indentation in order to make the source readable. Well, depending on the markdown interpreter, it will trigger the <code>...</code> tag, forcing to remove the readability of the text.