a bunch of tidying up. Sorry if it breaks things

README.md

@@ -4,9 +4,9 @@ How we do collaborative reproducible data analysis and reporting. Mostly (but no
 
 This repo does three things:
 
- * it is a collection of R [how-to resources](resources.md) including some notes on:
-   * how to [use git branches](gitBranches.md) 
-   * how to use [drake](https://docs.ropensci.org/drake/) to massively speed up and [manage your workflow](https://milesmcbain.xyz/the-drake-post/)
+ * it is a collection of R [how-to resources](howTo/resources.md) including some notes on:
+   * how to [use git branches](howTo/gitBranches.md) 
+   * how to use [drake](howTo/drake.md) to massively speed up and [manage your workflow](https://milesmcbain.xyz/the-drake-post/)
  * it is a [template](repoAsATemplate.md) repo that illustrates how we work and which you can copy;
  * it is an R package that you can build if you want to using 'install and restart' from the RStudio Build menu. If you do you will then be able to use its functions viz: `woRkflow::functionName()` (not that it has many).
 

howTo/drake.md

+# drake:
+
+ * use [drake](https://docs.ropensci.org/drake/) to massively speed up and [manage your workflow](https://milesmcbain.xyz/the-drake-post/). This includes always:
+    * loading and processing all your data inside a drake plan in a .R file. _So it only gets re-run if the code or data changes_
+    * creating each of your output objects inside the drake plan. _So they only get re-created if the code or data changes_
+    * rendering your .Rmd report at the end of the drake plan. _So you can pass the params in and report the output objects_
+    * => the first time you run the plan it will build everything. The second time, e.g. after you fix a .Rmd typo, _only the bits that have changed get re-built_. **Warning: drake can reduce the time it takes to run your code by an order of magnitude. This could seriously damage your tea & cake in-take...**
+ 
+We have an example of [using drake](https://git.soton.ac.uk/SERG/workflow/-/blob/master/Rmd/make_basicReport.R)
\ No newline at end of file

resources.md → howTo/otherResources.md

-## 'How to' resources:
+# Other 'How to' resources:
 
  * excellent [guidance for collaborative project teams (especially team leads)](https://opensource.guide/) even if they're not open and not R
  * [What they forgot to teach you](https://rstats.wtf/) about R including some required reading:
@@ -14,10 +14,4 @@
     * we have written a [short guide](gitBranches.md)
     * [HappyGit](https://happygitwithr.com/fork-and-clone.html) gives you the details
     * [ohshitgit](https://ohshitgit.com/) may be required here too (but not if you've followed the instructions above)
- * using [git(hub/lab) issues](https://guides.github.com/features/issues/) as a way to manage your project - just like we did for the [new ECCD website](https://git.soton.ac.uk/SERG/sergwebsite/-/issues)
- * how to use [drake](https://docs.ropensci.org/drake/) to massively speed up and [manage your workflow](https://milesmcbain.xyz/the-drake-post/). This includes always:
-    * loading and processing all your data inside a drake plan in a .R file. _So it only gets re-run if the code or data changes_
-    * creating each of your output objects inside the drake plan. _So they only get re-created if the code or data changes_
-    * rendering your .Rmd report at the end of the drake plan. _So you can pass the params in and report the output objects_
-    * => the first time you run the plan it will build everything. The second time, e.g. after you fix a .Rmd typo, _only the bits that have changed get re-built_. **Warning: drake can reduce the time it takes to run your code by an order of magnitude. This could seriously damage your tea & cake in-take...**
- 
\ No newline at end of file
+ * using [git(hub/lab) issues](https://guides.github.com/features/issues/) as a way to manage your project - just like we did for the [new ECCD website](https://git.soton.ac.uk/SERG/sergwebsite/-/issues)
\ No newline at end of file