I've put up a PR with P3 updates for WASI.dev: https://github.com/bytecodealliance/wasi.dev/pull/58
I'd also like to follow up on a conversation from the last meeting -- I investigated the feasibility of versioning mdbook, and while it's technically doable, there isn't really built-in support, and it may introduce unnecessary implementation and maintenance burden. Since there are relatively few places where P3 and <P3 content will differ, what do we think of using tabbed content blocks for WASI version-sensitive sections? I think this would be relatively easy to implement, maintain, and eventually deprecate, and it would also make it a little easier for users to compare approaches or differences side by side. If everyone is all right with this approach, I'd be happy to take on implementation.
Tabbed content blocks or just separate sections both sound great to me personally!
Going for what is easier to maintain sounds good to me. Thank you Eric
A couple updates here -- I implemented the URL and tab block styling issues we discussed at the last meeting, if anyone would like to take a look. The component-docs PR is here: https://github.com/bytecodealliance/component-docs/pull/340
I also added a tracking issue with proposed component-docs updates for P3: https://github.com/bytecodealliance/component-docs/issues/341 Feel free to toss comments on the issue, and perhaps we can discuss at the next meeting.
Last updated: May 03 2026 at 21:15 UTC