// the take
This is the source for Godot Engine's official docs at docs.godotengine.org — reST files built with Sphinx, covering the manual, tutorials, and the full class reference. It's for Godot users who want to read, fix, or translate the docs, not something you'd pull into a project.
Class reference pages are generated from the engine's own XML doc comments via a sync workflow, so API docs stay tied to actual signatures rather than hand-maintained prose drifting from the code. Docs are versioned per Godot release (3.6, 4.x, latest) with redirects handled through a dedicated CSV-driven tool, which is a real solution to the usual 'which version is this page for' mess. Offline HTML and ePub builds are generated weekly via CI and linked directly in the README, and there's an actual translation pipeline with per-language style guides rather than just a folder of half-finished locale forks.
Coverage is uneven in the way community-contributed docs always are: core manual pages get attention while niche class reference entries are often just the auto-generated signature with no usage example or gotchas. Being split across multiple maintained versions (3.6 vs 4.x vs latest) means fixes and improvements don't automatically propagate backward, so older-version pages can lag significantly behind. There's no interactive or runnable code in the docs themselves — every example is static text, so you're copy-pasting GDScript/C# into the editor to verify it still behaves as documented. Link rot and broken external references are an ongoing problem, mitigated only by a periodic CI link-checker rather than prevented structurally.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →