OWD project: WebXR docs #158
Labels
needs funding
proposal (actionable)
Enough information is provided and the work is scoped well. Actionable but not prioritized right now
Problem statement
In 2021, we worked with Meta on creating WebXR browser compat data and MDN WebXR reference docs, see #35.
We documented features from 10 WebXR specifications and wrote 131 new MDN reference pages.
Since then, a few things have evolved. There is now https://wolvic.com/en/ and in 2024 we will see Apple Vision Pro and visionOS. They all support WebXR, so it will become a standard with multiple implementations.
We haven't updated the WebXR guide pages, there are no how-tos, and there is no coherent WebXR tutorial. Also, it is likely that the WebXR standard has evolved and that reference pages need updating and new features need to be documented.
Proposed solutions
The Divio system describes a 4-part scheme and has been guiding us to create great sets of documentation (https://documentation.divio.com/).
We should make sure to have updated reference docs and compatibility information for all relevant XR devices in 2023/2024.
We should create guides that describe the different WebXR modules for VR, AR, Inputs, and integration with APIs like WebGL, WebGPU, Gamepad, and more.
Task list
There are ideas from two years ago when we worked with Meta, see this MDN content issue mdn/content#7276
We should talk to Wolvic, and Apple Vision Pro, and other XR Subject Matter Experts to figure out a good content plan for WebXR docs now that the technology becomes available more broadly.
Roughly, we would need:
Priority assessment
More information
Open Web Docs (OWD) is a non-profit collective funded by corporate and individual donations.
In order for this project to happen, please consider donating to OWD on https://opencollective.com/open-web-docs.
For more information on sponsorship and membership tiers, see https://openwebdocs.org/membership/
More information is available at https://openwebdocs.org/.
For questions, please reach out to [email protected].
The text was updated successfully, but these errors were encountered: