Three.js official references
Start here when an implementation detail depends on the current Three.js API rather than a copied snippet.
Reference library
Primary sources for Three.js builders.
Vavist articles are written from practical testing and primary documentation. This page collects the references used most often when a WebGL scene needs accurate API behavior, browser constraints, asset-format context, or publishing guidance.
Asset formats and loading
Use these references when GLB, GLTF, texture compression, or geometry compression choices affect delivery size and runtime behavior.
Browser APIs around WebGL
Three.js scenes live inside ordinary browser pages. These APIs matter when the canvas resizes, exports screenshots, pauses offscreen, or handles input.
Publishing and site quality
These references guide how Vavist structures static pages around the WebGL demos so the site remains useful without relying on canvas pixels alone.
How these references are used
Vavist does not copy documentation into article pages. The guides translate recurring Three.js problems into checklists, workflows, and small code patterns, then link back to the primary source when API behavior matters. That keeps each page useful as an explanation while still making it easy to verify details against the official docs.
When a topic depends on browser behavior, MDN is treated as the source of truth. When a topic depends on asset format, Khronos glTF material is preferred. When a topic depends on advertising or search review, Google documentation is cited directly. This source hierarchy keeps the site practical without turning it into a pile of unsupported tips.