Comments (5)
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.
from cc20.
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:
- I combined the labels "cheatsheet" and "video tutorials" together as a new chapter "Cheatsheets and video tutorials" and added it to _bookdown.yml
- I reordered some of the chapters and put "Other topics" to the end
- 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 :)
from cc20.
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.
from cc20.
@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.
from cc20.
@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.
from cc20.
Related Issues (20)
- Create appendix chapter on initial setup
- Create appendix chapter on merging PRs
- Create appendix chapter on chapter organization
- Add GitHub Actions to render book
- Create appendix chapter with instructions for PR mergers HOT 1
- Consider a separate "cheatsheet" section in the `cc20` book HOT 2
- Please add me as a collaborator! HOT 2
- Please add me as a collaborator HOT 1
- Collaborator Request HOT 1
- avoiding merge conflicts
- collaborator request HOT 1
- Ask to be Added as a Collaborator HOT 1
- help wanted: rendering book locally
- update branch name instructions
- Issue rendering 'speed-up-in-r-programming.Rmd' HOT 1
- 'speed-up-in-r-programming.Rmd' writes files to root directory HOT 2
- .Rmd files missing from _bookdown.yml HOT 2
- Ask to be added as a collaborator
- Thank you to all the collaborators! If you'd like to be removed from the repo lmk.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cc20.