Currently, stride has an issue: the Editor extension documentation is too limited.

main issues with stride：
The document limitations of the stride engine：
For example, if we want to develop a plugin, such as an extension compiler, the Stride documentation is too limited. For instance, the documentation for registering Add Component, custom components, registering menus, registering Inspector, registering Gizmo, and capturing SceneView mouse is too scarce. This limits our plugin to the game itself and prevents it from fully integrating into the game compiler. We suggest that the official team provide more extension documentation for the Editor.
Is stride really that bad? Is it really inferior to other engines?：
Compared to the Godot engine, there isn't much difference between stride and the Godot engine. The reason why Godot engine extension plugins are so simple is because they provide more extension documentation, which stride lacks. It's a major shortcoming that the engine has the capability but can't fully utilize it.
stride functionality and development
The official documentation should provide extensive extensions to facilitate plugin development, such as the terrain plugin. The official team only needs to improve stride, while we create plugins to provide better convenience and enhancements to stride.

Start by reviewing the existing Stride Editor extension documentation and inventory coverage for Add Component, custom components, menus, Inspector, Gizmo, and SceneView mouse capture. Define the documentation scope and add practical plugin-development guidance, including the terrain-plugin use case, so contributors can integrate extensions with the Editor and compiler.