| **env.R** | Where we store all the parameters that might be re-used across our repo. Such as colour defaults, data paths etc. We avoid using a project/repo level .Rprofile because it can lead to [a **lot** of confusion](https://support.rstudio.com/hc/en-us/articles/360047157094-Managing-R-with-Rprofile-Renviron-Rprofile-site-Renviron-site-rsession-conf-and-repos-conf
| **env.R** | Where we store all the parameters that might be re-used across our repo. Such as colour defaults, data paths etc. We avoid using a project/repo level .Rprofile because it can lead to [a **lot** of confusion](https://support.rstudio.com/hc/en-us/articles/360047157094-Managing-R-with-Rprofile-Renviron-Rprofile-site-Renviron-site-rsession-conf-and-repos-conf). |
) |
| **DESCRIPTION** | But only if you use this as a tmeplate for your own repo - it is a special file for packages |
|**DESCRIPTION**| But only if you use this as a tmeplate for your own repo - it is a special file for packages |
|**LICENSE**| Edit to suit your needs |
| **R/** | Where we store functions that get built |
| **R/** | Where we store functions that get built |
| **analysis/** | Where we store .Rmd files and the .R scripts that call them (usually using a `drake` plan) |
| **analysis/** | Where we store .Rmd files and the .R scripts that call them (usually using a `drake` plan) |
| **docs/** | Where we put output generated by the .R/.Rmd code. This is helpful if you are using [github/lab pages](https://guides.github.com/features/pages/). Unfortunately the University of Southampton gitlab service does not currently support this. |
| **docs/** | Where we put output generated by the .R/.Rmd code. This is helpful if you are using [github/lab pages](https://guides.github.com/features/pages/). Unfortunately the University of Southampton gitlab service does not currently support this. |
