Community
#Join the discussion
We discuss on Discord and on GitHub issues:
- Discord
- Issues: WESL design, specification, and documentation
- Issues: WESL for JavaScript/TypeScript
- Issues: WESL for Rust
Questions welcome, we’re eager to help. File an issue on any of the GitHub repos or ask in the help channel on Discord.
#Make Something with WESL
Build sample programs using WESL and tell us how it goes. We’ll help share your examples with the community.
Find bugs and rough spots in the tools and docs and let us know!
Our test suite needs more cases. And the docs on wesl-lang.dev now can surely be improved.
We also track some community projects for continuous integration testing and benchmarking. Can we add your WESL project?
#Help Design WESL
Please tell us about something you’ve found that doesn’t work smoothly in WGSL/WESL that we might be able to fix.
File an issue with the tag ‘use case’. Or add your scenario in a comment to up one of the existing ‘use case’ issuess. We want to prioritize the most import community features, so tell us.
Or share an idea for improving WESL. Perhaps a feature you’ve used in other languages that you’d like to see available in the WebGPU community? Pair your improvement idea with a ‘use case’ issue showing shader code problem.
#Help Build Tools and Docs
There’s plenty to do on existing projects, and new ones to start.. a few places to start:
- wesl-lang.dev this website. Help make it more clear.
- wesl-rs WESL library and tools in Rust.
- wesl-js WESL library and tools in TypeScript.
- Tree-Sitter grammar for WESL for external editor support.
- wgsl-analyzer language server IDE support for WESL in VSCode.
- TextMate WESL grammar for web syntax highlighting.