Unfortunately, this isn’t supported by the current Markdown standard out of the box. Because technical articles grow fast, I wanted to be able to split articles into separate markdown files. Markdown offers everything I need to produce technical articles. So I could easily access any final article later using GitHub’s website and I don’t have to browse thru the repositories history. If you assign a tag to a commit in git, it becomes a release on GitHub. I merge to master once I’ve finished an article and associate a proper w to the merge commit.

I ended up in just working on my develop branch. In the beginning, I was also using git flow and created dedicated feature branches for every article. Books are too big, and perhaps you want to set up webhooks to automatically generated previews for your book on each and every push. Only books, for every book I wrote, a dedicated repository has been created. I’ve created dedicated repositories for all different kind of publications (print articles, online articles, white papers). I use GitHub and their $7 paid plan to create as many private repositories I want to. Of course are all my articles stored in a private repository. git makes editing, restoring and merging various parts of an article very easy.Įverything I create is under version control, so why should my articles be the only exception? Of course, do you need all the regular support for images, footnotes, and so on.

highlight source code directly in the text.When writing about frameworks, programming languages or scripts, you’ve some slightly different requirements than authors of regular books or articles. That said, I want to share the tools I use and the workflow I prefer. I do this for almost a decade now and I’ve used many different approaches to make writing as comfortable as possible for me. Like many other developers, I write articles for various print and online magazines.

Ia writer chromebook