Adds a new page which gives a summary of the three renderers. This page briefly
describes the renderers, gives some guidance on how to choose a renderer. It also
contains a comparison table between the renderers.
Adds an entry in the FAQ which links to this new page.
Adds a note about subsurface scattering limitations to the Standard Material page.
Adjusts some other pages which had incorrect information.
The new text puts the focus on the most salient reason for using GDScript. The old examples covered almost all cases (every case except for AAA games), which made for awkward wording that was not relevant to most readers. Fixes#6651
Command used:
lychee **/*.rst --github-token="..." --accept="100..=103,200..=299,429"
429 error codes were allowed due to a high number of false positives,
even with a GitHub token specified.
We're close to beta, but not started yet, so it's definitely not releasing in April.
A release in May is plausible, but I don't want to make too optimistic promises, so
let's communicate June as a more realistic estimate.
The three libraries which had been singled out are just a small portion of
what actually requires attribution. Listing them all would basically duplicate
all of COPYRIGHT.txt, aside from CCO/PD licensed stuff.
Clarify that this is no legal advice.
Also merge in grammar and clarity improvements by John from another PR.
Co-authored-by: John Veness <john.veness.github@pelago.org.uk>
This allows users to leave comments on pages that don't have
`:allow_comments: False` somewhere in the page's source.
Both manual and class reference pages can receive comments.
Index pages cannot have comments, as discussion should occur on "leaf" pages.
GitHub Discussions is used as a backend on the same repository. This means
that Discussions *must* be enabled on godotengine/godot-docs before this
commit is merged to `master`. Users can choose to use the "Custom" watch
mode if they don't want to get notifications for discussion updates,
but still get notifications for issue and pull request updates.
User comments are intended to be used for the following purposes:
- Add a clarification or correct something in the documentation,
without having to open a pull request. Contributors are encouraged to
take a look at discussions from time to time, and see if there's information
worth incorporating in the pages themselves. Don't forget to reply to
the comment when doing so :)
- Mention a workaround for a common issue.
- Link to useful third-party resources that are relevant to the current page,
such as tutorials or add-ons.
User comments should *not* be used for technical support. Other community
platforms should be used for that.
Page-to-discussion matching is done using the `pagename` Sphinx variable,
which is independent of the Godot version and documentation language.
Being independent of the Godot version allows keeping old comments
when the Godot version changes, while also allowing users from `/stable`
and `/4.1` to "see" each other in discussions.
See https://giscus.app for more information.
* Update list_of_features.rst
In 4.2 release notes, debugging threads is listed as a new feature.
Yet in documentation about Godot editor capabilities the opposite was state.
Co-authored-by: A Thousand Ships <96648715+AThousandShips@users.noreply.github.com>
