I recently came across the good talk by the always good Yiuhi Xie at the Rstudio conference about Pagedown. You can see it by yourself reaching out the rstudio website or clicking the image below:
Pagedown is a newly released package ( still in experimentary status) with a really promising mission: help you build beautiful PDFs documents from our beloved Rmarkdown. More precisely it takes Rmarkdown files and render them into html files already “paged” and ready to be saved/converted into PDF.
This is something I am also experimenting with vizscorer, a bot advisor about ggplot plots
Do we really need a package like pagedown?
If you are asking yourself thisk question I will answer proposing you three experiments:
- try to create you resume in markdown for instance to use it on a website, and then employ the same text to generate a PDF you would actually send to a recruiter (and I am not even going to add “a recruiter for a job you would actually like to get”)
- try to generate PDF from one of your Rmarkdown files, and by a PDF I mean that kind of document where images are note broken into half from page to page and written text does not finish beyond the end of the page… (yeah, I know you know what I mean bu that…)
- try to create a decent PDF file in without loosing more than two days. And at this point I don’t have to specify you what I mean by decent :)
Can you see now the kind of pains pagedown package will relief? Now that you are getting this point let’s move on.
There is a version of the package on CRAN but since it is still under development it is suggested to install the development version from Github itself:
## Skipping install of 'pagedown' from a github remote, the SHA1 (a6018457) has not changed since last install. ## Use `force = TRUE` to force installation
pagedown relies on an updated version of pandoc so you should update the package before moving on with your pagedown trial
selecting the preferred template
is now time to select the template you want to employ to create your PDF document. At the moment you can choose from:
- a general purpose paged html, which is the most similar thing to a report you can get right now
- conference post
- Business cards
- a Resume, also known as Curriculum Vitae from European folks
- a Letter, also known as Letter from European folks
if you are an Rmarkdown frequent flyer you should be used with what comes next: a new .Rmd file is created. You just have to save it with a custom name and you will be ready to start editing.
filling in and rendering the template
ok then, I am not going to give you instructions about how to fill the templates, as a genaral guide you can refer to the Rmarkdown guide, which generally holds true for this package as well.
finally obtaining the desired PDF file
Let’s imagine you are already done with your editing and you are ready to render out your template. At the moment this is not the straight forward process you would imagine, and it does not pass trough the well-known knit button.
You rather have to get trough the xaringan pacakge and the following code:
install.packages("xaringan") #if this is not yet installed on your machine xaringan::inf_mr("my_resume.Rmd")
this will ignite the rendering process and in the end will produce the viewer tab showing up your document:
from there it will be quite easy to move to the brwoser leveraging the small button on the upper-left of the viewer pane:
At the moment only Chrome is fully supported from the package, so be sure to download and set it as the default web browser when playing with pagedown
and here we are: you have your document already paged as a regular PDF, ready to be printed into PDF using the regular Chrome procedure (ctrl+p or cmd+p and then save as PDF or open as PDF in Preview).
Isn’t that amazing? If you are still thinking that no, that it is not amazing, please, move back to the three experiments I proposed before.
my suggestions for improvements
As you may have understood I have a good opinion of this package, nevertheless some suggestions came to my mind after trying it:
- provide a more consistent experience for useRs used to the Rmarkdown ecosystem the rendering process should be started from the usual knit button. From the vindow opening after the knitting process one should be able to go the the browser via the usual open in browser button
- give the useRs more access to some basic layout choices within the provided templates ( trough a dedicated Rstudio addin maybe?)
- expand documentation and examples/vignettes (yeah, this is some kind of coward suggestion given the young age of the package, and I actually added it just to reach the magic number of three points…)
Please let me know in the comments if you find the tutorial useful or you think something is missing. Don’t forget to subscribe to be acknowledged about other similar R-related goodies and development of the R packages I maintain.