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:
We’ve been here before. Working in academia or knowledge production the “wouldn’t it be nice to have a website?” thought jumped in our mind more than once. Maybe it was for networking, for sharing our work or a project, for teaching, etc.
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. …