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.
HTML5/Web moved to their own subfolder
Global Illumination moved to their own subfolder
UI, IO, Inputs sections titles adjusted
2D, 3D tutorials grouped to improve navigation
Renames from GDNative to GDExtension
Add Pictures/Gifs and clarified compatability
Remove GDNative language bindings from GDExtension docs
Update SConstruct and AddingProperties section
updated with suggestions
Added property hint example + updated to API naming changes
Fixed redirect.csv
- Link to Console support in Godot documentation.
- In the Console support in Godot page, link to the
"Godot and consoles, all you need to know" blog post as it contains
additional context.
- Link to Importing 3D scenes documentation directly to avoid copypasting
the answer.
- Replace uses of "open-source" with "open source" for consistency.
The link to https://github.com/godotengine/godot-google-play-billing/releases is misleading, because the releases there are to old. You have to compile the project yourself, because otherwise google rejects the .aar upload because of using old api. Furthermore the described methods and signals correspond to the new Version and not the released Version 1.0.1
Hope my English will do.
Flynn's Arcades actually only does publishing, with porting being
done by RAWRLAB games.
The list should only contain companies that have actually developed
ports, rather than companies who are just publishing games to consoles
using third-party ports.
We've recently completed tech which enables us to port Godot Mono games to Nintendo Switch and Xbox family of consoles so we wanted to reflect that in the docs.
Also added GDK next to Xbox consoles to signify that we do native Xbox ports and not just use the deprecated UWP technology.
Tried to make the line as short and concise as possible, but am open to further modifications if deemed more optimal.
Found via `codespell -q 3 -S ./LICENSE.txt,./tutorials/i18n,./_tools/codespell-ignore-lines.txt -L doubleclick,findn,lod,inout,nd,raison,te` and other means
These doc changes are dependent on the following PR:
https://github.com/godotengine/godot-google-play-billing/pull/25
Summary of changes:
* Update queryPurchases section to reflect API change to be async
* Added details on functions added to v1.1
* Expanded detail on operation and options of the plugin
