Or rather: how I got rid of bloated setup and just wrote markdown.
When I first built this site almost a year ago, I was pretty happy with my setup. It was built with NextJS, hosted with Zeit now and the pages were written in MDX and styled with Sass. A pretty huge pipeline is needed in order to get this to stick together.
However, the site itself was literally just as basic as the site you are looking at right now (as of march, 2020). Why is such a complicated setup needed? Of course, it is not. But I knew NextJS pretty well, had gotten familiar with Sass and I really wanted to write using Markdown. What I wanted was achieved: a homepage I could update by writing markdown. However, I could not quite get past the fact that there was so much setup needed for such a basic thing.
Markblog is my attempt at a solution. It is a small piece of software written in Deno. It simply converts markdown to HTML, and packages it in a nice, tiny, non-bloated blog-like page. As of writing, the default file structure is as follows:
(create this automatically with Markblog's
The index page shows the markdown-text in addition to links to posts, in addition to the content
index.md. Then, Markblog's
build-command triggers conversion to html. In my setup,
this runs as part of a simple CI-pipeline, meaning that I never touch anything other than Markdown-files.
If this interests you, please head over to the project page to see more details!