Writing and delivering a book on Digital Humanities

The Story

I wrote a markdown book on Programming and Digital Humanities. I learned how to use Rstudio and Rbookdown on the way, they made it super easy to write the book. So I ended up with an R Markdown file (.Rmd).

GitHub was the first choice to share it. It renders Markdown directly, but not .Rmd — Yuhui has a wonderful post on why .Rmd is not rendered as .md on GitHub. So I changed it to standard Markdown (.md). People can preview the book, something may get lost in translation, but having the stuff out was already cool.

I also thought that if you really really really want the book you can clone it, renamed as .Rmd as R build it. …

My first attempt was all hand-made text editor “design”. A useful learning experience, but quite painful and inefficient. Can I do any better with further exposure to different tools?


We are going to:

  1. create a navigation bar with CSS;
  2. add some style and theme in the form of a gradient;
  3. create a cookie consent pop-up in JavaScript. …

Then a deadline came or there was a talk to be prepared, an unexpected application to be written, yet another assignment passed semi-aggressively from your boss or, simply, we were resting for the first time in X years (hoping X != 10).

Long story short: the blogdown package is there to change this and help.

As academics we are terrible subjects to learn semi-technical things. We ask for whys and want to understand things (black boxes are enemies, unless we capitalize all our concepts… that’s probably making a career out of black boxes). That steeps our leaning curve. …


Guglielmo Feis

M.A. phil. Ph.D.. Working on Digital Humanities, games and blockchain. Podcaster, guitar player, and something I forgot. http://www.thegui.eu/

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store