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>
- Update type names in question about GDScript and other languages.
- Move question about plugins to be located just below the question
about SDKs.
- Mention that using C++ exceptions would increase compile times,
as evidenced by Godot's SCons setup recently disabling exception
handling by default.
- Replace potentially misleading "2K" term with 1440p, assuming
the question has mobile devices in mind (current flagships are 1440p).
- Remove question about RTTI not being used in Godot, as RTTI
is now always used to ensure type safety in projects exported
in release mode.
- Remove reference to option to shrink images on load, which was
removed in Godot 4.0 (devices with such low resolutions are
very uncommon nowadays anyway).
This also documents using glow as a blurring solution
(e.g. for menu background blur), which is a common question
on support platforms.
The reference to an outdated quality setting in the depth of field
properties was also updated.
