Markup on

Makefile to process all Asciidoctor files in a directory

christoph.stoettner@stoeps.de (Christoph Stoettner) — Sun, 13 Dec 2020 14:00:00 +0200

I write most of my documents (blog posts, documentation, recipes and so on) with Asciidoctor. Everything is organized in Git repositories.

During GPN 19 (Gulaschprogrammiernacht) I showed how to build html and pdf with a Gitlab CI/CD pipeline. That’s quite handy, but lots of documents I build, I just need locally.

So today I played with WSL2 and a Makefile to build all Asciidoctor files in a directory.

Asciidoctor open links in new window

christoph.stoettner@stoeps.de (Christoph Stoettner) — Mon, 27 Apr 2020 11:49:13 +0200

I write most of my documentation with Asciidoctor, so saving some keystrokes is important.

You can add window=_blank to links in your Asciidoctor source.

Automate hugo

christoph.stoettner@stoeps.de (Christoph Stoettner) — Mon, 30 Dec 2019 14:19:52 +0100

Mid 2018 I switched my blog from Wordpress to Hugo. Main reason was performance and that I can use Asciidoctor to write the posts.

What happened the last 18 months? I stayed with the theme I selected 2018, but I tweaked it a little bit. So I added lunr to implement searching, changed all scripts and fonts from CDN to local (privacy and tracking), updated Bootstrap 3 to 4.

Working with Bootstrap was quite fun, I haven’t done a lot of HTML or CSS the last years, but the grid and css classes from Bootstrap are working without checking each change on all browsers and are responsive.

Asciidoctor for Professional Looking Documentation

christoph.stoettner@stoeps.de (Christoph Stoettner) — Mon, 10 Jun 2019 18:20:11 +0200

For GPN19 I prepared a second talk on Documentation with any Editor. The talk was based on a previous one from Froscon 13, but the pipeline tooling changed.

This time there was a technical issue during the recording and so there are only the slides available, but you can still watch the video of the Froscon talk: Froscon 13: Documentation with any Editor

New Blog Engine

christoph.stoettner@stoeps.de (Christoph Stoettner) — Sat, 14 Jul 2018 14:15:09 +0200

I switched my blog to Hugo the last days. After nearly 12 years with WordPress, I needed something new. Why did I drop WordPress, one of the most used blog engines in the world?

Most used means always most interesting for bad guys. Dynamic pages are slower and can contain more vulnerabilities than static pages (which Hugo generates). Hugo supports git, so I have version control in my posts and design. I can start a small web server locally and test the posts: hugo server -D and the most convenient thing: I can use VIM for editing.