Maintainer access for the WebGPU landing page

[stefnotch]

Hello,

We, the WESL team, would love to help maintain the https://github.com/webgpu organisation and keep it up to date. This should involve creating a homepage, which points people in all the right directions

• An overview
• Tutorials, grouped by programming language
• Samples
• Useful libraries and tools, such as Brendan Duncan's WebGPU Inspector
• A link to the specification
• Community channels, mainly the official Matrix channel

Would it be possible for us to get maintainer access to the GitHub organization?

[mehmetoguzderin]

I think the model of the Specs, WebGPU Fundamentals, and WebGPU Samples could also work well for a portal, where a public repository can allow anyone with a contribution to file a PR, and then, if merged, GH Pages reflect it without the need for org access. Though I think current forwarding of webgpu(dot)dev to spec is also sth nice as a shortcut, and a portal/landing page would need to be scoped down a lot probably, esp. featuring libraries could come off with the sense of "officially boosted" to people where there might be multiple alternatives. The arewe{concept}yet in Rust and other ecosystems is quite nice; however, they are explicitly community pages for the most part. I think if there is something helpful and gaining traction, whether it be a tutorial or a tool/sample, search engines index well with reasonable flexibility these days, and LLM search agents make it even easier for queries with less clarity when it comes to terminology (for example, if I ask "tutorial to unlock infinite depth in WebGPU" bluntly, all three large LLM providers did return the Reverse Z method). Although this is just one opinion, and I'm also unsure if this should be a discussion thread rather than an issue.

[stefnotch]

Very valid point regarding the libraries. I was hoping to do it similarly to the wasm homepage, which points you in the right overarching direction, but avoids getting into the details.

So we could likely only include de-facto standard libraries, and would have to tread with caution when there is no clear cut winner. The wasm analogues would be "emscripten for C++, Pyodide for Python".

And I agree about keeping the scope small. It saves us a lot of difficult editorial decisions. Plus, it avoids overwhelming newcomers with choices.

[kainino0x]

I have created https://github.com/webgpu/webgpu.github.io and am slowly working on setting it up to live at webgpu.org. Feel free to make a PR to that site to start adding some basic content! One thing I'd specifically like to have is a webgpu test on the homepage (like https://get.webgl.org).

[greggman]

fwiw, there's a WebGPU logo model here

[jimblandy]

I'm +1 on adding Lee and Stefan to github.com/webgpu. Officially, the W3C GPU For The Web Working Group decides github.com/webgpu's membership. @Kangz has put this on the agenda for this Wednesday's meeting.

[kainino0x]

https://webgpu.org (and https://www.webgpu.org) are live from https://github.com/webgpu/webgpu.github.io, with HTTPS enforced so we can use WebGPU on the homepage. Didn't take quite as long as I expected to get that working :)

[jimblandy]

The WebGPU committee discussed this today and approved adding @mighdoll, @stefnotch, and @k2d222.

[kainino0x]

Done.

[kainino0x]

BTW I renamed https://github.com/webgpu/webgpu.github.io to https://github.com/webgpu/webgpu.org because it avoids a redirect on https://webgpu.github.io which I think was impacting https://webgpu.github.io/webgpu-samples which I don't want to relocate (at least not right now). Also calling the webgpu.org repo webgpu.org is less confusing.

[Kangz]

GPU Web WG 2025-10-01 Atlantic-time

• JB: Rubber stamp for this?
  • CW / KN / BJ: thumbs up
• JB: Mozilla in favor
• Added Lee Mighdoll (@mighdoll), Stefan (@stefnoch), Mathis Brossier (@k2d222)