Support for seamless AR/VR content integration in articles
backlog
Janeera D A
Industries are increasingly using 3D, AR, and VR content to explain complex concepts, especially in hardware documentation, troubleshooting guides, and training material. Currently, Document360 does not natively support embedding immersive content from tools like Sketchfab, Echo3D, 8thWall, Unity WebGL, MAKAR, Blippbuilder (BlippAR), or MyWebAR exports. While HTML blocks and iFrames are technically supported, they are often inconsistent across article views (especially in preview vs. publish modes), and there is no UX guidance or safe wrapper for such embeds.
This limits our ability to deliver interactive, real-time learning experiences directly within the knowledge base, pushing us to host such content externally and break the continuity of the documentation.
Proposal:
Introduce a dedicated AR/VR Embed Block in the article editor that:
- Allows safe and responsive embedding of third-party AR/VR experiences using iFrame or WebXR links.
- Provides default support for Sketchfab, Echo3D, 8thWall, Unity WebGL, MAKAR, Blippbuilder (BlippAR), MyWebAR, or similar platforms.
- Offers fallback messaging for unsupported browsers/devices.
- Includes a preview mode within the editor.
Impact:
- Enables richer documentation with interactive, visual-first learning.
- Supports use cases like hardware walkthroughs, visual product demos, and immersive training, all within the documentation platform.
- Reduces writer dependence on external tools or engineering support for integration.
This feature would position Document360 as a future-ready documentation platform that leverages immersive technology, especially valuable in industries such as IoT, manufacturing, automotive, healthcare, and EdTech.
Log In
Shakeer Hussain S
backlog
Shakeer Hussain S
Hi Janeera - Thank you for taking the time to share such a detailed and forward-thinking proposal regarding AR/VR content integration within Document360. We truly appreciate your perspective and the depth of context you've provided around the use cases and limitations of the current iFrame/HTML block approach.
We understand the growing need for immersive content—especially in industries like manufacturing, healthcare, automotive, and EdTech—and agree that enabling seamless AR/VR experiences could significantly enhance how complex topics are explained within knowledge bases.
At this point, native support for AR/VR embedding is not on our immediate roadmap, but we recognize the potential impact this could have on documentation quality and user engagement. We’ve added your proposal to our feature backlog, and we will closely monitor interest from other customers in this space.
Your suggestions around a dedicated embed block, responsive preview, fallback messaging, and platform compatibility (e.g., Sketchfab, Unity WebGL, Echo3D) are particularly helpful and will be considered if we move forward with this initiative.
Thanks again for your valuable input. Please continue to share your ideas—they help us shape a better product.