Hugo Locurcio

> Wouldn't documentation on this require access to each consoles SDK's themselves then, and therefore still not be possible as an open source project? The documentation wouldn't be about porting...

The Android export pages have received many updates over the years, so this issue is likely not relevant in its current state. Please open separate issues if you still encounter...

I suppose we should have a dedicated page on setting up various CI services with Godot for automated exporting.

There's now documentation for exporting to dedicated servers: https://docs.godotengine.org/en/stable/tutorials/export/exporting_for_dedicated_servers.html There's still no page about exporting using CI platforms, but there is no official template for this yet. [godot-ci](https://github.com/abarichello/godot-ci) is technically...

This documentation already exists: https://docs.godotengine.org/en/stable/development/cpp/index.html Please be more specific if you need documentation on a subject that isn't already covered. The rendering pipeline is likely the main aspect that isn't...

> This is not a documentation issue, but I suppose the naming should be changed to "Convert to Meshinstance2D" instead of "Mesh2D", since the Mesh2D does not actually exist. This...

cc @ellenhp

The table of contents' scroll bar is already customized, but the main document scrollbar isn't.

> Also `pinned_points: PoolIntArray` is not documented yet. > >  > > Godot version: 3.2.1 The property is registered dynamically, which means `--doctool` has no chance to list it...

To avoid this kind of Control node creation (which I always found uncanny), I wonder if we should expose the default project font as a SceneTree property or getter method.