-
Notifications
You must be signed in to change notification settings - Fork 63
Clarify more concisely how concepts relate to each other #64
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At first glance, i thought this acted almost as a table of contents; however, as it references non-design pages, this should maybe live elsewhere
@itowlson @kate-goldenring should this be rebased/merged or closed? |
I think we should still add this in as a TOC for the design section. This needs to be rebased, filenames updated, and this added to |
@itowlson can we revisit this and see if we can fit in this glossary? It is a great overview for someone who is learning what WASI, WIT and the component model are. I think the |
@itowlson what are your thoughts on moving this to the Introduction page (almost as a preface to help readers know where to go with these new terms in their lexicon)? |
@kate-goldenring I feel like it might be overwhelming in the intro - create the feeling of "you have to know these before you can read the book" possibly. I am no longer quite sure where it would go though. It could possibly be kludged in on the "why the component model" page, even though it's more "what" than why, perhaps? |
Maybe this should go under the Reference section under a new definitions page? |
This is a great addition--I think the introduction is the right place for this, since these terms are ultimately critical vocabulary for understanding what follows. |
Fixes #59.