Alison edits round1

[apreshill]

Hey @dcossyleon,

I think this can be safely merged in. It should look like this:

https://quirky-liskov-be449b.netlify.com/

A few things to note:

1. I wonder if we want to do any CSS styling more with the TOC now that we have sections vs chapters (should sections perhaps be uppercase, then chapters in title case? I defer to you, but right now it is the opposite.

2. Also I did sort of a trick with a lot of those "intro" chapters. We could do some CSS with first of type selectors to perhaps indent those, italicize, or otherwise denote those differently. They are currently just unnumbered, but hoping you might have some ideas.

3. I added some divs to the css for better tip/note/warning boxes (issue #3). I copied over the ones from the current R packages book, so please style away. Also I think we cannot use the lightbulb image as it needs attribution. But the setup is now there for you. See them in action here; code here. You can literally change anything about these- and add more as you think appropriate (right now there are just two: rstudio-tips and tips).

4. I was wondering if you might want to reconsider some kind of image at the top of each chapter? You could either do full width with some css magic, or you could do includes: before_body instead of in_header option (link). Up to you, but I still love that image and miss it!

5. Finally, I added a folder called modules/ where you could (if you wanted to) store individual Rmd docs to be used as child documents to the bookdown parent versions (link). See an example here.

[dcossyleon]

My questions/ comments below:

1. I wonder if we want to do any CSS styling more with the TOC now that we have sections vs chapters (should sections perhaps be uppercase, then chapters in title case? I defer to you, but right now it is the opposite.

• I agree that the highest level titles should be the ones that are uppercase. I've updated this. Some alternatives I'd like to play around with include making Sections uppercase and also giving it a background color, having the chapters also be uppercase, and having the subsections be title case. Another alternative to try would be to add a line above or beneath the Sections, to help make the hierarchy clearer.

2. Also I did sort of a trick with a lot of those "intro" chapters. We could do some CSS with first of type selectors to perhaps indent those, italicize, or otherwise denote those differently. They are currently just unnumbered, but hoping you might have some ideas.

• One thing I am wondering about to address this is whether we can remove the chapter title "introduction" altogether and turn the Section title into a link that houses the introduction content. The reason I'd like to try this is because I've always found it a bit disorienting that Bookdown TOCs are made up entirely of clickable links except for the Section Titles--and additionally, that the Section Titles don't appear anywhere else besides the TOC. @apreshill, what are your thoughts on this? Is there a way to make a title both a Section and Chapter Title?

3. I added some divs to the css for better tip/note/warning boxes (issue #3). I copied over the ones from the current R packages book, so please style away. Also I think we cannot use the lightbulb image as it needs attribution. But the setup is now there for you. See them in action here; code here. You can literally change anything about these- and add more as you think appropriate (right now there are just two: rstudio-tips and tips).

• done! might need your help to figure out what would be best categorized as rstudio-tips

4. I was wondering if you might want to reconsider some kind of image at the top of each chapter? You could either do full width with some css magic, or you could do includes: before_body instead of in_header option (link). Up to you, but I still love that image and miss it!

• Is there any way to insert a chapter-specific (or even section-specific) yaml so that I can apply a different image/HTML file across the pages. Right now the same one is being applied globally.

5. Finally, I added a folder called modules/ where you could (if you wanted to) store individual Rmd docs to be used as child documents to the bookdown parent versions (link). See an example here.

• Yes, I like this! Seeing it in action with the example is helpful, and I'll use these moving forward.