Hello everyone,
I would like to share a suggestion that could help both new and experienced users of GDevelop.
After spending some time exploring the engine structure and the documentation, I noticed that sometimes the documentation does not fully match the current version of the editor. Because GDevelop evolves quickly with frequent updates, certain tutorials, features, or workflows can become outdated or behave differently compared to what the documentation describes.
From a technical perspective, GDevelop is composed of multiple parts: the core architecture, the JavaScript runtime (GDJS), the editor interface, and the extensions system. These components evolve continuously, which means that documentation needs to evolve at the same pace to remain reliable for users. ([docs.gdevelop.io][1])
Why this matters
For many users, the documentation is the primary learning resource. When examples or instructions correspond to older versions, it can cause:
- Confusion for beginners following tutorials
- Incorrect usage of features that changed in recent versions
- Extra questions in the forum about problems caused by outdated documentation
Possible improvements
Here are a few ideas that might help:
-
Version tagging in documentation
Each article could indicate the version of GDevelop it was written for (for example: Tested with GDevelop 5.x.x). -
Version sections for major features
When an important system changes (extensions, behaviors, new editors, etc.), documentation could show notes like:
“In versions before 5.x this worked differently.” -
Community maintenance tags
Articles could include labels such as:
Verified for latest version
Needs update
Written for older versions
-
Link documentation updates with releases
When a new engine version introduces feature changes, documentation updates could be part of the release checklist.
Benefits for the community
This would help:
- beginners learn faster
- extension developers avoid API confusion
- forum support become easier
- tutorials remain reliable long-term
GDevelop already has a strong community-driven documentation system, which is great because it allows contributors to improve it through GitHub pull requests. ([gdevelop.io][2])
Maybe adding a stronger connection between engine versioning and documentation updates could make the ecosystem even better.
Thanks to the developers and contributors for all the work on GDevelop. I hope this suggestion can help improve the learning experience for everyone.
Best regards.