forked from jtr13/cc20
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.Rmd
133 lines (79 loc) · 10.4 KB
/
index.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
---
title: "Fall 2020 EDAV Community Contributions"
date: "`r Sys.Date()`"
site: bookdown::bookdown_site
output: bookdown::gitbook
github-repo: jtr13/cc20
description: "This book will hold all community contributions for STAT GR 5702 Fall 2020 at Columbia University"
---
```{r, include=FALSE}
knitr::opts_chunk$set(cache = TRUE)
```
# Instructions
This chapter gives you all the information you need to upload your community contribution. **Please read this entire document carefully before making your submission.** Of particular note is the fact that **bookdown** requires a different .Rmd format than you're used to, so you must make changes to the beginning of the file as described below before submitting.
## Background
This web site makes use of the **bookdown** package to render a collection of `.Rmd` files into a nicely formatted online book with chapters and subchapters. Your job will be to submit a slightly modified version of your community contribution `.Rmd` file to the GitHub repository where the source files for this web site are stored. On the backend, the admins will divide the chapters into book sections and order them.
If your community contribution is in a different format, then create a short `.Rmd` file that explains what you did, and includes links to any relevant files, such as slides, etc. which you can post on your GitHub repo (or another online site.)
## Preparing your `.Rmd` file
You should only submit **ONE** `Rmd` file.
After completing these modifications, your `.Rmd` should look like this [sample `.Rmd`.](https://github.com/jtr13/cc20/blob/master/sample_project.Rmd){target="_blank"}
1. Create a concise, descriptive name for your project. For instance, name it `base_r_ggplot_graph` or something similar if your work is about contrasting/working with base R graphics and **ggplot2** graphics. Check the `.Rmd` filenames in [the project repo](https://github.com/jtr13/cc20){target="_blank"} to make sure your name isn't already taken. Your project name should be words only and joined with underscores, **no white space**. In addition, all letters must be **lowercase**. Create a copy of your `.Rmd` file with the new name.
2. Completely delete the YAML header (the section at the top of the `.Rmd` that includes name, title, date, output, etc.) including the `---` line.
3. Choose a short, descriptive, human readable title for your project as your title will show up in the table of contents -- look at examples in the 2019 EDAV rendered book of community contributions [https://jtr13.github.io/cc19](https://jtr13.github.io/cc19/){target="_blank"}. Capitalize the first letter only ("sentence case"). On the first line of your document, enter a single hashtag, followed by a single whitespace, and then your title. It is important to follow this format so that bookdown renders your title as a header. Do not use single `#` headers anywhere else in the document. Note: if your chapter is the first in a section, a second `#` header and section description will be requested during the pull-request and merge phase.
4. The second line should be blank, followed by your name(s):
```
# Base R vs. ggplot2
Aaron Burr and Alexander Hamilton
Your content starts here.
```
5. If your project requires data, please use a built-in dataset or read directly from a URL, such as:
`df <- readr::read_csv("https://people.sc.fsu.edu/~jburkardt/data/csv/addresses.csv")` <br> If you absolutely must include a data file, please use a small one, as for many reasons it is desirable to keep the repository size as small as possible.
6. If you have included a `setup` chunk in your `Rmd` file, please remember to remove the label `setup` in the chunk, i.e., use:
```
{r, include=FALSE}
```
instead of:
```
{r setup, include=FALSE}
```
7. If your project requires libraries to be installed and included in the document, please adhere to the following conventions. Do not evaluate any `install.packages()` statements in your document. Consumers of an `Rmd` file won't want packages to get installed when they knit your document. Include any `library()` statements at the top of your `Rmd` file, below the title, name, and `setup`, but above any content. If your chapter requires the installation of a package from source (is a GitHub installation), please add a comment identifying it as such. Here is an example `library()` section with install statements that won't be evaluated:
```{r, eval=FALSE}
install.packages("devtools") # used for installation from source
install.packages("dplyr")
install.packages("ggplot2")
library("devtools")
devtools::install_github("twitter/AnomalyDetection")
```
```{r, eval=FALSE}
library("AnomalyDetection") # must be installed from source
library("dplyr")
library("ggplot2")
```
You could include both sections, or you could just include the second `library()` section and trust R users to install any packages themselves. If you developed your `Rmd` file before moving your `library()` statements above the rest of the file content, it is highly recommended to knit and review your document again. This may change the namespace that was available in each section of your code during development, causing a function not to work or to exhibit unexpected behavior. This common issue is mentioned in the EDAV R Basics ["Functions stop working"](https://edav.info/basics.html) section.
Want to get fancy? See the [optional tweaks](#optional-tweaks) section below.
## Submission steps
To submit your work, we will be following "Workflow #4" -- that is submitting a pull request to someone else's repository to which you do not have write access. Instructions are available in [this tutorial](https://edav.info/github.html#st-pr-on-another-repo-with-branching){target="_blank"}. They are repeated below in abbreviated form, with specific instructions on naming conventions, content information, and other important details.
1. Fork [cc20 repo (this repo)](https://github.com/jtr13/cc20){target="_blank"} to your GitHub account.
2. Clone/download the forked repo to your local computer.
3. Create a new branch and name it with your project name, in our case `sample_project`. **Do not skip this step. We will not merge your PR if it doesn't come from a branch.** If you already forgot to do this, check [this tutorial](https://edav.info/github.html#fixing-mistakes) for how to fix it.
4. Copy your modified `.Rmd` file with the same name into the root directory on the branch. In our example, it is [`sample_project.Rmd`](sample_project.Rmd){target="_blank"}.
5. Do not include an `.html` file. (In order for the **bookdown** package to work, all `.Rmd` files will be rendered behind the scenes.)
6. [OPTIONAL] If you have other resources (such as images) included in your project, create a folder under `resources/`. In our example, it is [`resources/sample_project/`](resources/sample_project){target="_blank"}. Put the resources files there.
7. When you are ready to submit your project, push your branch to your remote repo. Follow [this tutorial](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork) to create a pull request.
8. At this point a back and forth will begin with the team managing the pull requests. If you are asked to make changes, simply make the changes on your local branch, save, commit, and push to GitHub. The new commits will be added to your pull request; **you do not need to, and should not, create a new pull request.** (If, based on the circumstances, it does make sense to close the pull request and start a new one, we will tell you.)
9. Once your pull request is merged, it's fine to delete your local clone (folder) as well as the forked repository in your GitHub account.
## Optional tweaks
1. If you prefer for links from your chapter to open in new tabs, add `{target="_blank"}` after the link, such as:
`[edav.info](edav.info){target="_blank"}`
2. Note that your headers (`##`, `###`, etc.) will be converted to numbered headings as such: <br> `##` --> 3.1 <br> `###` --> 3.1.1 <br> These headings will appear as chapter subheadings and sub-subheadings in the navigation panel on the left. Think about a logical structure for users to navigate your chapter. We recommend using only `##` and `###` headings since "sub-sub-subheadings" such as 4.1.3.4 are generally unnecessary and look messy.
3. Unfortunately, there's no simple way to preview your chapter before it's actually merged into the project. (**bookdown** has `preview_chapter()` option but it only works after the entire book has been rendered at least once and that will become more and more complex and require more and more packages as the project grows.) If you really want to preview it, fork and clone this [minimal bookdown repo](https://github.com/yihui/bookdown-minimal){target="_blank"}, add your `.Rmd` file, click the "Build book" button on the Build tab (next to Git), and then open any of the `.html` files in the `_book` folder in a web browser to see the rendered book. (**Do not click the Knit button as it will not build a bookdown book.**) <br><br> If you're interested in more **bookdown** options, see the [official reference book](https://bookdown.org/yihui/bookdown/){target="_blank"}. <br><br> Have more useful tweaks to share? Submit an issue or PR.
## FAQ
### What should I expect after creating a pull request?
1. Within a week after you create a pull request, we will apply a label to it and assign an administrator who will review all the files you submit to see if they meet the requirements.
2. It will take some time before we can process all the pull requests, so as long as you see your pull request has been labeled and assigned to an admin, don't worry.
3. However, if the admin contacts you regarding the pull request, that usually means your files fail to meet some requirements. The admin will clearly state what is wrong, so please fix them as soon as possible.
### What if I catch mistakes after my pull request is merged?
You may submit additional pull requests to fix material on the site. If the edits are small, such as fixing typos, it is easiest to make the edits directly on GitHub, following [these instructions](https://edav.info/contribute.html#github-only-walkthrough){target="_blank"}. We will merge first pull requests before edits, so please be patient.
### Other questions
If you encounter other problems, please [submit an issue](https://github.com/jtr13/cc20/issues){target="_blank"} and we will look into it.
Thank you for your contributions!