Make writing technical content great again!

As many other developers, I write articles for various print and online magazines. I do this for almost a decade now and I’ve used many different approaches to make writing as comfortable as possible for me. That said, I want to share the tools I use and the workflow I prefer.

Writing technical articles should be as comfortable as coding in these days

When writing about frameworks, programming languages or scripts, you’ve some slightly different requirements than authors of regular books or articles. You want to

  • create tables
  • highlight source code directly in the text
  • provide complex code snippets

of course do you need all the regular support for images, footnotes, and so on.

Using proper version control system

I use git to manage all my articles. git makes editing, restoring and merging various parts of an article very easy.

Everything I create is under version control, so why should my articles be the only exception?

Of course are all my articles stored in a private repository. I use GitHub and their $7 paid plan to create as many private repositories I want to. I’ve created dedicated repositories for all different kind of publications (print articles, online articles, whitepapers).

Only books, for every book I wrote, a dedicated repository has been created. Books are too big, and perhaps you want to setup webhooks to automatically generated previews for your book on each and every push.

In the beginning I was also using git flow and created dedicated feature branches for every article. To be honest, that was too much 😜. I ended up in just working on my develop branch. I merge to master once I’ve finished an article and associate a proper tag to the merge commit.

Release Feature in github

If you assign a tag to a commit in git, it becomes a releases on GitHub. So I could easily access any final article later using GitHub’s website and I don’t have to browse thru the repositories history.


That’s no surprise. I use markdown to write my stuff. Markdown offers everything I need to produce technical articles. Because technical articles grow fast, I wanted to be able to split articles in separate markdown files. Unfortunately this isn’t supported by the current Markdown standard out of the box. But that’s where tooling comes into play.

A lot of writing tools like iA Writer are supporting exactly this feature.

It’s dead simple. You just provide the path for the markdown file you want to include and you’re done. But this reference has to be placed in it’s own row.

# Article Headline
## Let's get started
## Conclusion

Let’s take a look at an artefact. for example may contain both images and snippets.

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren.
![Figure 1 - FX Arch](images/001-fx-architecture.png)
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren,

Convention over Configuration (CoC)

I love the concept of Convention over Configuration, it’s easier to define a clean structure once and follow that “convention” instead of providing a “configuration” for each and every article.

All my articles are structured using a simple schema.


First, there is the main article folder (here recent-article). This folder contains various files. The main article file is, of course, the most important one. Next to this, I store other markdown files containing notes, notes I use during the early stages when I need to do some research on a topic I’ve to cover as part of the article.

The artefacts folder is a collection of small markdown files. I break my article into small chunks and arrange those chunks in Some artefacts are always pre-populated like and

Images, surprisingly remain to the images subfolder and to stay consistent, all code snippets (longer than three lines) are stored as dedicated markdown files inside of snippets.

Yes, I write all my snippets in markdown instead of just putting a raw code file there.

The advantage of putting the snippet itself, again into a markdown file is just laziness. Each snippet starts with three backticks and also end with those. Having this format, I can copy, cut and paste just the single line to include that particular snippet in the text. Otherwise I’ve to move around three lines (two lines with the three backticks and the include statement).

Last, but not least I have dedicated folders for previews and deliverables, those folders normally contain generated PDF version of the article.

Writing Tools

I’m always trying to find better tooling. You should never stop looking for new opportunities or alternatives to things you currently use. In these days I prefer iA Writer, it’s easy to use and it supports embedding partial markdown files 🤘🏼. It’s also possible to use custom themes, to ensure that your articles either follow a given corporate identity or reuse your preferred fonts, colors, margins,….

Generating previews and deliverables

For generating previews or deliverables, I use either the export function offered by iA Writer or Pandoc. Pandoc is also able to read the include statements for partial markdown files I mentioned earlier.

That’s it. I hove you enjoyed the read. If so, 💚 this post and start following Thorsten Hans. Perhaps you also want to start writing your articles using this workflow and tools. I’d love to read your experiences.