/
TODO.txt
64 lines (30 loc) · 3.52 KB
/
TODO.txt
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
## Priorities
### Current items
Left off tutorial improvements at Chapter 14 (strings), which was completed.
Chapters 21, 22, 26 and 27 are OK, but could still use a lot of clean up.
Rewrite Introduction.
Check to make sure that the plots only use things which have been taught, especially oecd and portland in chapters 10 and 11.
### Specific Chapter Issues
Q&A sections, at least in RStudio and Code.
Make more use of https://ggplot2-book.org/ and https://docs.posit.co/ide/user/
Maybe much of the material in Quarto R4DS chapter belongs in RStudio and Github chapter, allowing Quarto tutorial to focus on projects.
Do RStudio and Code and RStudio and Github tutorials link up well together?
The styler package and its use seem important and worth discussing. See https://www.youtube.com/watch?v=_nAfJ-5nkcU&authuser=0 for other interesting options.
### Graduation Exercises
Jade's idea for "Exploration" sections at the end of each tutorial. Give students some choices. Let them explore. Let them make something. There is no wrong answer.
Might be nice if each middle chapter tutorial (like factors, dates and times, et cetera) finished with a beautiful plot which required the use of skills from that chapter to manipulate the data first. An example is babynames in Strings chapter.
Even better, instead of a line-by-line plot built in the tutorial, we should have students create this plot oustide of the tutorial. It should be an exercise, like RStudio and Github, which starts with a student making a repo, connecting it to an RStudio project, starting a quarto document, loading libraries and data, building a plot, rendering the document so it looks nice and then publishing the plot on the web. Students need more practice with all these steps.
One project might be: Make any plot you like! Maybe using `diamonds`. Maybe give some advice? Maybe a fork? Maybe Github pages? Would require creating an index.qmd. Maybe explain how to use the visual editor.
Don't forget to review stuff, like shortcut keys.
### Publishing Issues
Should we be exploring other ways, besides RPubs, of publishing individual pages? quarto publish quarto-pub quarto-1.qmd works! quarto publish gh-pages quarto-1.qmd also has real possibilities.
## Leftover Material from Chapter 29
Maybe find a home for this stuff?
The most important set of options controls if your code block is executed and what results are inserted in the finished report:
eval: false prevents code from being evaluated. (And obviously if the code is not run, no results will be generated). This is useful for displaying example code, or for disabling a large block of code without commenting each line.
include: false runs the code, but doesn’t show the code or results in the final document. Use this for setup code that you don’t want cluttering your report.
results: hide hides printed output; fig-show: hide hides plots.
error: true causes the render to continue even if code returns an error. This is rarely something you’ll want to include in the final version of your report, but can be very useful if you need to debug exactly what is going on inside your QMD. It’s also useful if you’re teaching R and want to deliberately include an error. The default, error: false causes rendering to fail if there is a single error in the document.
As you work more with knitr, you will discover that some of the default chunk options don’t fit your needs and you want to change them.
When inserting numbers into text, format() is your friend.
Lots more stuff on figures, caching, tables, et cetera.