Last updated: 2020-06-12
Checks: 7 0
Knit directory: workflowr-useR2020/
This reproducible R Markdown analysis was created with workflowr (version 1.6.2.9000). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.
Great job! The global environment was empty. Objects defined in the global environment can affect the analysis in your R Markdown file in unknown ways. For reproduciblity it’s best to always run the code in an empty environment.
The command set.seed(20200611)
was run prior to running the code in the R Markdown file. Setting a seed ensures that any results that rely on randomness, e.g. subsampling or permutations, are reproducible.
Great job! Recording the operating system, R version, and package versions is critical for reproducibility.
Nice! There were no cached chunks for this analysis, so you can be confident that you successfully produced the results during this run.
Great job! Using relative paths to the files within your workflowr project makes it easier to run your code on other machines.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
The results in this page were generated with repository version 28e7671. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish
or wflow_git_commit
). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:
Ignored files:
Ignored: .Rhistory
Ignored: .Rproj.user/
Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
These are the previous versions of the repository in which changes were made to the R Markdown (analysis/customization.Rmd
) and HTML (docs/customization.html
) files. If you’ve configured a remote Git repository (see ?wflow_git_remote
), click on the hyperlinks in the table below to view the files as they were in that past version.
File | Version | Author | Date | Message |
---|---|---|---|---|
Rmd | 43117cb | John Blischak | 2020-06-12 | Add lesson on customization, and also customize tutorial website. |
After you’ve created your workflowr website, you may wish to customize its appearance. This lesson covers a few key methods. For the full details, please read the official vignette Customize your research website.
The website you created with workflowr is an rmarkdown-generated website. The rmarkdown website settings are saved in the configuration file analysis/_site.yml
. The default theme applied to workflowr websites is “cosmo”. You should see the output section below that passes site-wide settings to workflowr::wflow_html()
, which in turn passes these arguments to rmarkdown::html_document()
.
output:
workflowr::wflow_html:
toc: yes
toc_float: yes
theme: cosmo
highlight: textmate
The available themes are from Bootswatch, but only a subset are available for use with rmarkdown:
As an example, this workflowr website uses the theme " yeti ".
Go to Bootswatch and find a few themes you like. Then try them out by changing the value of theme in analysis/_site.yml
and rebuilding one of the pages. You can either click the Knit HTML button or use wflow_build()
. For convenience, choose a fast running Rmd so you can quickly explore multiple themes. Note that the updated theme will only be applied to rebuilt pages, so you’ll see the previous theme on different pages if you click around the website.
Once you’ve decided on a theme, commit the change to analysis/_site.yml
while additional republishing all the Rmd files with the following command:
wflow_publish("analysis/_site.yml", "Change the theme", republish = TRUE)