Collect content for homepage

[stefnotch]

We should start out by collecting the content, and politely asking the committee.

For the design and amount of content, we can take inspiration from the https://immersiveweb.dev/ and the https://webassembly.org/ homepages.

Relevant issue:
gpuweb/gpuweb#5324

[k2d222]

My initial curation. I suggest 3 content categories:

• Learning resources, split by actor: Official, Vendors and Community
• Ecosystem (libraries, frameworks, platforms, tools)
• Spotlight (demos, use-cases, websites, commercial products, )

Maybe we should also distinguish WGSL and WebGPU content.

---

Learning resourcees by W3C:

• WebGPU specification
• WGSL specification
• WebGPU explainer (community)

Learning resources by vendors:

• WebGPU Fundamentals
• WebGPU samples
• WebGPU on MDN
• Chrome's 'Your first WebGPU app'
• Chrome's Tour of WGSL
• wgpu.rs

Community learning resources:

• awesome-webgpu - curated list of WebGPU content
• Compute.toys - Online shader sandbox (shadertoy-like)

Ecosystem:

• THREE.js - Web 3D engine
• babylon.js - Web 3D engine
• PlayCanvas - Web 3D engine & editor
• Bevy - Rust game engine
• Tensorflow - Machine learning library
• Use.GPU - React-like declarative WebGPU library
• TypeGPU - Type-safe declarative WebGPU library
• WESL - WGSL lang extensions
• wgsl-analyzer - IDE WGSL support

Spotlight:

• TBD

(State of WebGPU):

• Caniuse WebGPU
• webgpureport.org
• WebGPU CTS

---

This list is missing a lot, has a selection bias, etc. It's a starting point.

Then I think we should establish a basic, informal process for curation and contribution guidelines. Such as:

• Anyone can submit content via Issues/PRs.
• Content must be accepted by website maintainers.
• Content must be actively maintained/used, and have value to community.
• Content can be removed if it becomes outdated.

[stefnotch]

Another thing that I'd want is "which extensions are supported on which platforms". If we cannot get that data, it'd be nice to just have a little dynamic table with "your browser supports these extensions".

[kainino0x]

There are a few links at the bottom of webgpu.io that I would like to move here and remove from there.
Pasting them here.

---

Materials

Samples

• webgpu-samples for Chrome and Firefox (uses WGSL, or GLSL via SPIR-V)
• wgpu-rs samples for Firefox and Chrome (uses GLSL via SPIR-V), compiled from Rust
• WebKit/Safari Demos See above samples

Demos

• webgpu-clustered-shading
• Meta-balls
• Spookyball - 3D version of "Breakout", Halloween theme.
• WebGPU Playground - a student project at Imperial College London. feedback
• three.js WebGPURenderer

Articles

• Get started with GPU Compute on the Web
• WebGPUFundamentals

Frameworks

• Babylon.js
  • WebGPU documentation
  • Performance comparison demo of WebGL Forest vs WebGPU Forest

[kainino0x]

There might be a few more things in my most recent WebGPU slides. Pasting those here too.

---

• Official/Semi-Official Learning Materials
  • WebGPU spec & WGSL spec
  • WebGPU "Correspondence" Reference (contributions wanted)
  • WebGPU Fundamentals (contributions wanted)
  • WebGPU Best Practices by Brandon Jones
  • Tour of WGSL
  • WebGPU on MDN
• Unofficial Learning Materials
  • Awesome WebGPU
  • WebGPU/WGSL Reference
• News
  • What's New in WebGPU in Chrome

---

• Samples and Demos
  • WebGPU Samples (contributions wanted)
  • compute.toys
• Developer Tools
  • WebGPUReport.org
  • WGSL Inspector
  • WebGPU-Dev-Extension
  • WebGPUReconstruct
• Libraries
  • Dawn (C++ and webgpu.h, over C++)
  • wgpu (Rust) and wgpu-native (webgpu.h, over Rust)
  • WESL
  • Slang (experimental WGSL support)
  • wgsl_reflect
  • React Native WebGPU
  • Toucan! (up next)