Last updated: 2020-10-10

Checks: 7 0

Knit directory: r4ds_book/

This reproducible R Markdown analysis was created with workflowr (version 1.6.2). 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(20200814) 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 bbb6cd2. 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:    .Rproj.user/

Untracked files:
    Untracked:  VideoDecodeStats/
    Untracked:  analysis/images/
    Untracked:  code_snipp.txt

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/misc_add_xaringan_slides_github.Rmd) and HTML (docs/misc_add_xaringan_slides_github.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
html 226cd16 sciencificity 2020-10-10 Build site.
html ceae495 sciencificity 2020-09-17 Build site.
html b8fde7d sciencificity 2020-09-13 Build site.
html 0bab89d sciencificity 2020-09-12 Build site.
html 720a89b sciencificity 2020-09-02 Build site.
html 4612bb8 sciencificity 2020-09-02 Build site.
Rmd 7305596 sciencificity 2020-09-02 added new misc section

So you’ve got a set of Xaringan slides …

… but don’t know how to share it …

Disclaimer: This works for a single slide deck
  1. Create your slides like normal, but if you can, name it index.Rmd.
  2. Knit your slides.
  3. If you have not named your markdown document index.Rmd you do need to rename the .html file created from the knitting process into index.html once you’re ready to publish them.
  4. Create a git repo on GitHub.
  5. Initialise a git repo in your slide directory (I use Anaconda Prompt for my Git commands):
      > cd C:\Personal\RLadies\talk_XXX
      (base) C:\Personal\RLadies\talk_XXX> git init
      (base) C:\Personal\RLadies\talk_XXX> git add .
      (base) C:\Personal\RLadies\talk_XXX> git commit -m "first commit"
      (base) C:\Personal\RLadies\talk_XXX> git branch -M master
      (base) C:\Personal\RLadies\talk_XXX> git remote add origin
      (base) C:\Personal\RLadies\talk_XXX> git push -u origin master
  6. If you have your index.Rmd, css folder etc. in a subfolder, move all the contents to the main folder - index.html should be in the main folder.
  7. Create a new branch to be able to host the slides called gh-pages.
      (base) C:\Personal\RLadies\talk_XXX> git checkout -b gh-pages
      (base) C:\Personal\RLadies\talk_XXX> git add .
      (base) C:\Personal\RLadies\talk_XXX> git commit -m "msg"
      (base) C:\Personal\RLadies\talk_XXX> git push origin gh-pages
  8. In GitHub navigate to your repo, and change the branch to the gh-pages one.
  9. Under settings you will get your GitHub Pages website name.
  10. Click the URL, and do your final checks.
  11. Share as you’d like 😄

R version 3.6.3 (2020-02-29)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 18363)

Matrix products: default

[1] LC_COLLATE=English_South Africa.1252  LC_CTYPE=English_South Africa.1252   
[3] LC_MONETARY=English_South Africa.1252 LC_NUMERIC=C                         
[5] LC_TIME=English_South Africa.1252    

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] emo_0.0.0.9000  workflowr_1.6.2

loaded via a namespace (and not attached):
 [1] Rcpp_1.0.4.6     knitr_1.28       whisker_0.4      magrittr_1.5    
 [5] R6_2.4.1         rlang_0.4.7      stringr_1.4.0    tools_3.6.3     
 [9] xfun_0.13        git2r_0.26.1     htmltools_0.5.0  yaml_2.2.1      
[13] digest_0.6.25    rprojroot_1.3-2  assertthat_0.2.1 crayon_1.3.4    
[17] purrr_0.3.4      later_1.0.0      promises_1.1.0   fs_1.4.1        
[21] glue_1.4.1       evaluate_0.14    rmarkdown_2.1    stringi_1.4.6   
[25] compiler_3.6.3   generics_0.0.2   backports_1.1.6  lubridate_1.7.8 
[29] httpuv_1.5.2