Previously, many paragraphs in the documentation used `::` at the end of a line
as a replacement for a single colon (and `::` on the following line).
Due to this, the `::` was part of the extracted string for localization.
Weblate also showed a warning about the trailing `::`, as it's not
normally expected to be there.
This change requires translators to revalidate all modified strings.
However, considering many of those have broken code blocks due to translators
replacing `::` with `:`, it can be a good idea.
This also adds documentation writing guidelines for code blocks and admonitions.
This commit does not modify existing admonitions in any way (as this would
lead to a much larger diff, and require more localizable text to be revalidated
by translators).
This is done for several reasons:
- Recent CPython versions such as 3.13 have mostly caught up
with Pyston in terms of performance. If the trend continues,
CPython may supersede Pyston's performance in the long term.
This is especially the case if the experimental JIT is
eventually able to run Godot's SCons setup.
- Pyston is not maintained anymore (its last release was in 2022),
and the last Python version it can run is 3.8. Python 3.8 is now
end-of-life. Godot's SCons setup (as well as SCons itself) will
eventually require Python versions newer than 3.8.
- Reorder instructions to mention ARM64 builds first in macOS,
as this is the primary architecture in use now (with all new Macs
since 2023 being sold with Apple Silicon only). The `lipo` command still
works as before, as it infers the architecture from the input files.
- Remove the manual bundle generation steps to make the page shorter
(similar to Compiling for Android).
- Remove references to the master branch (this was only relevant when
4.0 was still in development).
The Introduction to the buildsystem page still mentions this parameter
in case it needs to be changed, but in most situations, the default
value of `(number of CPU threads) - 1` does a good job.
- Merge Community/Contributing and Engine Development into one top-level section, Contributing.
- Structure it in a way that gives equal priority to various ways to contribute, including documentation.
- Rename several articles to be more comprehensive and in line with the overall state of the documentation.
- Rewrite the guide for class reference contributions.
Danil Alexeev