Should webgpu.dev redirect to webgpu.github.io, instead of the spec?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- web-dev
Research direction
Start by checking the current redirect configuration for webgpu.dev and the webgpu.org repository's hosting or domain settings. Confirm whether the intended destination is webgpu.github.io or webgpu.org, then verify that webgpu.dev redirects there instead of gpuweb.github.io/gpuweb/.
Written by the indexing model from the issue text.
Description
Right now, the description for https://github.com/webgpu has a link to https://webgpu.dev, which redirects to https://gpuweb.github.io/gpuweb/. If webgpu.github.io and webgpu.org are going to be a thing, I think webgpu.dev should redirect there instead.
- Dominant language
- CSS
- Stars
- 21
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from webgpu/webgpu.org
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
webgpu/webgpu.org#3 · 2 reactions ·
-
webgpu/webgpu.org#2 · 4 comments · 3 assignees ·
All issues in webgpu/webgpu.org
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·