Consider incorporating live tutorials and translations into their respective chapters

[cpaynerogers]

While organizing the chapters for the book, it's easy for me to empathize with reading the book as a native English speaker, and semantically placing the live tutorials and the translations at the end. I think this organization is useful for merging all of the initial pull requests. It was done in the cc19 book, too. However, I'd like us to consider collapsing either the translations or the live tutorials sections, or both, into the preceding sections, so the book isn't biased towards tutorials written in English and provided as an Rmd file. I do know this may be at odds with my cheat sheet issue :)

[ybliu9]

I am not sure if I fully understand what you'd like to do (haha my bad), but I made the following updates in _bookdown.yml:

1. I combined the labels "cheatsheet" and "video tutorials" together as a new chapter "Cheatsheets and video tutorials" and added it to _bookdown.yml
2. I reordered some of the chapters and put "Other topics" to the end
3. I moved around the contributions a little bit and merged a couple of contributions to put under new chapters (labels)

Also, I merged your PR earlier, but I am not sure whether the chapter headers you put in some contributions would work. You might want to knit and render the book to double check the format.

Please let me know if you have any additional thoughts :)

[cpaynerogers]

It looks like the chapter headers aren't rendering. Can you share why you think they won't work, since they aren't working?

Here's an example of what we could do that I had in mind with this issue. There is a chapter that translates the candela package into Chinese. The candela package is an interactive visualization tool. Could we add the chapter to the data visualization section, or should keep it in a translations section? The bias being that we're only including English resources in our foremost chapter groupings and grouping all of the translations together "just because." This issue is just to make sure we consider that bias.

[jtr13]

@cpaynerogers Excellent point about bias. I like the idea of integrating the translations with the rest of the material.

I'm doing the rendering manually because GitHub Actions isn't set up properly yet. I just rendered the book so please check if it's correct. I don't recommend testing the rendering locally since it involves installing tons of packages that you likely don't want. The goal is to have GitHub Actions set up with Netlify in a way that gives us deploy previews so we can check the rendering before merging the pull requests, but right now we don't have it set up that way.

[cpaynerogers]

In the spirit of getting people's chapters merged, I think the current organization works, but lets keep this issue open. I'd be happy to update translations to exist alongside English chapters in each section with a separate pull request once everyone's work is in a draft of the book (and anything else, like the Netlify GitHub Action, is working).

The current rendering looks right relative to the _bookdown.yml, but we'll need to merge chapters from each section and add any missing (PART) labels in the first chapter of those sections.

[ybliu9]

@cpaynerogers Do you mean that we delete the translations Part and append these submissions to the respective sessions based on their topics? If so, I think this makes sense and I can update those submissions after we confirm this.
I have looked at the rendered book, and I will double check to make sure all Parts have (PART) labels in the first chapter. I was not sure if the headers work because I didn't render the book, but now they look fine.