immersive-web / immersive-web/immersiveweb.dev
Two <Model> Source Formats?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 110
- Forks
- 55
- Avg merge
- 5h 44m
- Merged PRs (30d)
- 1
Description
https://immersiveweb.dev/model
This new page has every source include two formats. Does the page explain why two formats are required?
If a GLTF can be converted to USDZ, why can the implementation not handle this conversion?
Is the expectation that every site maker needs to take their model and convert it to two formats?
If that expectation is realistic for developers then why isn't it realistic for the browser to be able to open either format and / or convert them too?
What should the site say to explain this?
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.
Research direction
Start by reading the model page at https://immersiveweb.dev/model and review how it currently presents the two source formats. Clarify why both formats are listed, whether site authors are expected to provide both, and what the page should say about browser conversion; done means the page answers these questions for site makers.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100