You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're interested in collaboration on making the WebAssembly website better, please sign up by adding a comment and the area(s) you want to improve.
I'm definitely interested in contributing, particularly to a wasm playground, but I'd also be happy to help organize the site's content. In particular I think the website generally just does a poor job conveying what wasm actually is, and I'd like to help with that one way or another.
I'm definitely interested in contributing, particularly to a wasm playground, but I'd also be happy to help organize the site's content. In particular I think the website generally just does a poor job conveying what wasm actually is, and I'd like to help with that one way or another.
Thanks for making me aware of this issue. I am happy to see a team forming to work on the contents of the page. I can offer to share my ideas and donate prior work on a playground I developed for my own purposes. For now just very briefly:
Regarding the features page, I noticed there are some runtimes missing, in particular interpreters and know that some of them would be interested to be listed there but hesistant to add themselves. I would suggest to make the process known how to get added there. Same goes for languages.
I'm definitely interested in contributing, particularly to a wasm playground, but I'd also be happy to help organize the site's content. In particular I think the website generally just does a poor job conveying what wasm actually is, and I'd like to help with that one way or another.
I developed a playground that might be worth sharing if there is interest so you dont have to start from scratch. The only dependency is Monaco (the visual editor of VSCode, the rest is custom Typescript. We could add support for more languages here while the .wat, .wasm and treemap are agnostic of the source language. Panels can be rearranged and hovering or clicking on sections navigates to them in the other views. I have also added some quick documentation in the tooltips and human readable readouts for byte groups on the binary format.
The AssemblyScript playground is also very neat. It allows developers to see a program written in a higher level programming language they are familiar with compiled to .wat, so they can learn Wasm by seeing the compiled output and iterating.
For the playground, would you like to consider integrating wasm-language-tools (a language server for WebAssembly Text Format) into the .wat editor? Maybe switching to Monaco Editor is required for better experience. Here's another project PlayWat whose .wat editor is powered by wasm-language-tools.
Activity
tomayac commentedon Apr 10, 2025
bvisness commentedon Apr 10, 2025
I'm definitely interested in contributing, particularly to a wasm playground, but I'd also be happy to help organize the site's content. In particular I think the website generally just does a poor job conveying what wasm actually is, and I'd like to help with that one way or another.
tomayac commentedon Apr 10, 2025
Feel free to use or modify https://web.dev/articles/what-is-webassembly (What is Wasm) and https://web.dev/articles/compiling-mkbitmap-to-webassembly for (Getting started [with emscripten]).
sunfishcode commentedon Apr 10, 2025
The MDN site on WebAssembly is a great resource here.
tomayac commentedon Apr 10, 2025
I agree. I think it's a balance of not repeating what is solved well elsewhere already and making the site somewhat self-contained.
pdubroy commentedon Oct 22, 2025
I'm also interested in contributing. One specific thing I'd be happy to tackle is helping to keep https://webassembly.org/features/ up to date. Right now there is some discrepancy with https://github.com/WebAssembly/proposals (which AFAIK is the source of truth).
Will see if I can send a PR later today.
ttraenkler commentedon Mar 7, 2026
Thanks for making me aware of this issue. I am happy to see a team forming to work on the contents of the page. I can offer to share my ideas and donate prior work on a playground I developed for my own purposes. For now just very briefly:
Regarding the features page, I noticed there are some runtimes missing, in particular interpreters and know that some of them would be interested to be listed there but hesistant to add themselves. I would suggest to make the process known how to get added there. Same goes for languages.
I developed a playground that might be worth sharing if there is interest so you dont have to start from scratch. The only dependency is Monaco (the visual editor of VSCode, the rest is custom Typescript. We could add support for more languages here while the .wat, .wasm and treemap are agnostic of the source language. Panels can be rearranged and hovering or clicking on sections navigates to them in the other views. I have also added some quick documentation in the tooltips and human readable readouts for byte groups on the binary format.
tomayac commentedon Mar 9, 2026
An additional playground idea I had for the website was always to integrate something like runno.
ttraenkler commentedon Mar 9, 2026
I could make it a web component like runno. If you can compile the interpreter or compiler to WASM the rest is browser native anyways.
tomayac commentedon Mar 9, 2026
The AssemblyScript playground is also very neat. It allows developers to see a program written in a higher level programming language they are familiar with compiled to
.wat, so they can learn Wasm by seeing the compiled output and iterating.g-plane commentedon Mar 14, 2026
For the playground, would you like to consider integrating wasm-language-tools (a language server for WebAssembly Text Format) into the
.wateditor? Maybe switching to Monaco Editor is required for better experience. Here's another project PlayWat whose.wateditor is powered by wasm-language-tools.