Revise introduction #280
Merged
Revise introduction #280
Conversation
This file contains hidden or 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
vados-cosmonic
approved these changes
Jul 15, 2025
There was a problem hiding this comment.
LGTM 🚀
Thanks for working on this @catamorphism it looks great so far. I left a couple nits/questions but these are more worth pondering on.
Co-authored-by: Victor Adossi <[email protected]>
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.
By way of introduction, I'm Tim Chevalier at Igalia; we're being sponsored to work on improving the component model documentation, especially with an eye towards making it more understandable by WebAssembly beginners.
This PR reorganizes the introduction by defining WASI before it's mentioned, and making a few other changes to make the text flow better. I also changed "Component Model" to "WebAssembly Components" in the sidebar per #122. Finally, I fixed a broken link in the FAQ section.
I attempted to use semantic line breaks in my changes, but if there's a preferred style for these docs that precludes that, let me know.