itowlson

Thanks for this @ritesh089! I'm afraid I'm not quite getting how this connects up to the book at the moment. For example, is the reason for it to illustrate something...

Thanks @ritesh089 - I see what you mean about showing how this works across multiple packages and repos. What I'd suggest is making those documentation changes as part of this...

To me, worlds and components are different things. A world is a contract; a component is a thing that implements that contract. Many different components, for example, can implement the...

@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...

@vados-cosmonic Thanks for picking up this languishing PR! However, my objection to putting it in the introduction remains the one I mentioned in https://github.com/bytecodealliance/component-docs/pull/64#issuecomment-2791052373 - I feel like this is...

@vados-cosmonic That seems well worth exploring! When you say "a new section header," are you thinking e.g. a new page after "Why the Component Model", and then the bullets from...

@vados-cosmonic Your proposed structure looks promising to me. My bullets will certainly need expanding to make it work but I feel much more comfortable with that than with having them...

Resources are in progress at https://github.com/bytecodealliance/component-docs/pull/103

I wrote a bit on Wasmtime host implementation which is in the Rust pages for now, but some people felt that, in the long term, content like that should move...

This looks good to me. One perhaps personal preference: I would be inclined to put the "why" ahead of the quick start unless the introduction contains enough "why" material to...