- Update the page to match the new versioning policy.
- Add a Bash function to retrieve alpha/beta/RC commit hashes
from the command line.
- Mention caveats related to project compatibility and
output binary names.
* Moved icon spec to itemised list
The icon specifications should not be considered a recommendation, but rather a requirement. Either way, the details of its ratio and size should be included with each form entry is described - as that is the natural place to look for it.
* Update community/asset_library/submitting_to_assetlib.rst
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
* Streamline “Building the manual with Sphinx”
The goal of this commit is to make the instructions in “Building the
manual with Sphinx” easier to follow. It does so by
1. Removing items from the prerequisites list that would get installed by
requirements.txt anyway.
2. Adding items to the prerequisites list that were missing.
3. Making it possible to follow the instructions by reading them from
top to bottom without jumping around.
4. Putting the meat of the instructions into an ordered list (this will
make it easier for readers to not lose their place).
* Minor English fix for “Building the manual with Sphinx”
This commit simplfies many sentences and rewords many sentences to make
them sound more natural. In some places, this commit rewords sentences
to make their structure more parallel. The goal of all of these changes
is to make the content guidelines easier to understand.
Before this commit, the paragraph at the bottom of “Guidelines and
principles” said pretty much the same thing that the paragraph at the
bottom of “Limiting cognitive load” said. This commit combines those two
paragraphs to reduce redundancy.
This commit simplfies many sentences and rewords many sentences to make
them sound more natural. In some places, this commit rewords sentences to make
their structure more parallel. The goal of all of these changes is to
make “Best practices for engine contributors” easier to understand.
This change makes the docs repo always use the official abbreviation (CC BY 3.0)
for its license. Previously, it would sometimes use “CC-BY 3.0” or
“CC-BY-3.0”. This change also make the docs repo always point to the
official Commons deed [1] for more information about CC BY 3.0.
Previously, it would sometimes link to an unofficial source [2].
[1]: <https://creativecommons.org/licenses/by/3.0/>
[2]: <https://tldrlegal.com/license/creative-commons-attribution-(cc)>
The old URL linked to a YouTube playlist (by Miziziziz) named "tutorials" whose subject matters only tenuously relate to Godot implementation. I've substituted a URL to the same creator's playlist "godot tutorials", which I contend is more relevant to the Godot beginner reading this page.
In the section "Filing an issue on GitHub", the subsection "How to reproduce the bug" says "Even if you think that the issue is trivial to reproduce, adding a minimal project that lets reproduce it is a big added value." which is missing a word. Changing it to "...lets everyone reproduce it..." fixes the grammatical error.
Stating that "Solution must be local" is denying the fact that some problems
cannot be solved locally. Therefore, documentation should recommend
contributors to first look at solutions which are closer to the problem first,
and only go for solution that touch core if a problem cannot be solved
locally, for instance.
