-
Notifications
You must be signed in to change notification settings - Fork 3.6k
[Discussion] Structure #50
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
Comments
I'm not totally sure yet. One major issue here is that each chapter has to go to No Starch in one chunk, and I don't want to be going back and forth and back and forth splitting and re-assembling. But beyond that, until I actually come up with new drafts of each chapter, I don't know how many sub-headings they have, which is why I haven't done a whole lot. |
@azerupi Just for reference, the intended TOC is here: https://public.etherpad-mozilla.org/p/trpltoc |
Interesting! What format do you have to deliver in?
Ok thanks! The reason I asked is because I read the primitive types chapter (and your comment about it) and as I imagine more info will be added in the future about some types, that chapter will become quite long with well defined sub-sections. Splitting into sub-sections would allow to go more in depth and give more examples without having abnormally long pages. For example:
Lastly, two neat tricks (at least I find it neat) you can do with mdBook, just mentioning in case you didn't know :)
|
In Markdown, they just want to read whole chapters at once and so they can do it or I can, and I feel bad making them do it.
This is like, my favorite feature 👍
Ohhh cool. I will probably do this too. |
I can understand it's not easy to target both media at the same time. Even though they are both "books", a paper and an online version still differ a lot in their format and philosophy.
Thanks 😊 |
I think this issue can be closed now, yeah? |
Proofread ch03-00
Hi Steve,
A couple of thoughts about the structure:
As of now, all source files reside in the root
src
folder. Do you plan on adding a bit more hierarchy? For example, every chapter / section could be moved into it's own directory, so that files about similar subjects reside closer to each other and are more easily found.The current version (old book) is pretty "flat", there is only one sub-level to the chapters. I would personally subdivide the longer chapters, were you have multiple sub-parts, into actual sub-chapters.
Shorter chapters, focussing on one specific subject, are more comprehensive. You clearly see where the current subject stops and were the next begins. Reading a chapter feels lighter and less involved, which is good when you read on-the-go, in situations were your time is limited or when there is a lot of distraction.
Because sub-chapters would be shown in the sidebar, it would also enhance the structure and navigation.
What is your view about this?
The text was updated successfully, but these errors were encountered: