-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Book structure #154
Merged
Merged
Book structure #154
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 25, 2021
Closed
As you can see by the ridiculous screen shots, #153 is needed to make this expanded structure at all sensible to navigate 😆 |
5 tasks
cart
reviewed
May 28, 2021
Solve the "mouse" thing and I think this is good to merge! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created the skeleton of the new book following bevyengine/rfcs#23, and added brief notes to each chapter on what I think should be covered and in what order.
Merging this in will allow us to start writing in a nice, distributed fashion. If you want to tackle a chapter, please mention it in #158 so we don't duplicate effort. I would particularly appreciate help with the platform-specific chapters, rendering and assets, as those are the areas I know least about.
There were two areas of content that were lost from the old book: