Skip to content

Commit aeaa466

Browse files
committed
ready for submission
1 parent 4d43238 commit aeaa466

File tree

2 files changed

+12
-57
lines changed

2 files changed

+12
-57
lines changed

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,12 +80,17 @@ You can access the tutorials via the Tutorial tab in the top right
8080
If either of the following is happening to you
8181

8282
<ul>
83+
8384
<li>
85+
8486
Cannot find the Tutorial pane
8587
</li>
88+
8689
<li>
90+
8791
Cannot find any r4ds tutorials
8892
</li>
93+
8994
</ul>
9095

9196
Then **remember to restart your R session** after installing the

TODO.txt

Lines changed: 7 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -1,81 +1,31 @@
11
## Priorities
22

3-
### Me
3+
We should consider deprecating/removing all the RStudio stuff when Positron is released.
4+
5+
Point people toward positron.tutorials.
46

57
Data Import and Numbers took 90/80 minutes last summer. That is too long. Edit them so that they are closer to 60 minutes.
68

79
Communication is the tutorial which would most benefit from a clean up.
810

9-
Put a new version of R4DS on CRAN. This will require dealing with a couple of annoying NOTES from R CMD check.
10-
11-
Ensure that any useful material from Quarto R4DS chapter 28 is added to the RStudio and Quarto tutorial.
12-
13-
Add a section to Quarto Websites Introduction tutorial which covers much of the material in Quarto Formats R4DS chapter 29. See below for some info.
14-
15-
Ensure that RStudio and Code and RStudio and Github tutorials link up well together.
16-
17-
Tighten some longer tutorials so that they are more like 60 minutes. See below.
18-
19-
### Khang
11+
Tighten some longer tutorials so that they are more like 60 minutes.
2012

2113
Test Data Visualization tutorial. Fix up any problems.
2214

23-
### Satvika
24-
2515
Test both Quarto Websites tutorials. Note that they have been reworked to use Github pages.
2616

17+
Clean up tutorials 24 and 26.
2718

28-
### Sharav
2919

30-
Tutorial 24
31-
32-
* Find the complaints in Discord and email me the link. #tutorials channel? #general channel?
33-
* Fix the complaints.
34-
* general quality improvements, as with knowledge drops, typos and so on.s
35-
36-
Tutorial 26
37-
38-
* Find the complaints in Discord and email me the link. #tutorials channel? #general channel?
39-
* Fix those complaints.
40-
* Read: https://ppbds.github.io/tutorial.helpers/articles/books.html
41-
* Re-read the chapter. Quality check for entire tutorial.
42-
43-
44-
45-
### Notes from DK
20+
## Other topics
4621

4722
Would be cool to test commands which we expect students to enter into the Console. Of course, written questions don't allow for test chunks, but we can just make our own chunks, with include = FALSE. They will run during tutorial creation and fail if the command no longer works. Of course, in most cases, we would need to create, on the fly, the file which those commands access.
4823

4924
Make more use of https://ggplot2-book.org/ and https://docs.posit.co/ide/user/
5025

51-
5226
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. Note its addition to the new verion of RStudio.
5327

54-
55-
56-
57-
58-
## Leftover Material from Chapter 29
59-
60-
Maybe find a home for this stuff?
61-
62-
The most important set of options controls if your code block is executed and what results are inserted in the finished report:
63-
64-
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.
65-
66-
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.
67-
68-
results: hide hides printed output; fig-show: hide hides plots.
69-
70-
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.
71-
72-
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.
73-
74-
When inserting numbers into text, format() is your friend.
75-
76-
Lots more stuff on figures, caching, tables, et cetera.
77-
78-
### Tutorial Times from Summer 2024
28+
## Tutorial Times from Summer 2024
7929

8030
# A tibble: 25 × 3
8131
source minutes N

0 commit comments

Comments
 (0)