Accepting feedback that inline comment expands the block unnecessarily. Perhaps the better edit here is to explicitly state that the comment is about the following boolean statement rather than the prior.
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.
Commenting out code from the previous exercise that causes the icon to float up, making it difficult for users to see the example of directional input.
Many people have reported having issues connecting HUD's start_game and the main node's new_game() in the next step of this tutorial. This occurred for me because the documentation states that "new_game()" should be removed from the _ready() function, but does not include instructions to add "pass" back (and pass is not left in the example code when "new_game()" is added to the function, so the initial one will not remain). Having the function declaration without "pass" breaks all the following functions, preventing new_game() (or any Main functions) from being connected.
The order of mentioned nodes (SpawnPath and SpawnLocation) does not match the previous sentence when using "respectively". The following image confirms the order may be backwards.
The existing text reads "Select the Mob node and set it's Gravity Scale..."
It is instead grammatically correct to say "and set its" without an apostrophe.
Changes a hyperlink In the tutorial for Your First 2D game, Dodge the Creeps, to link directly to the Dodge the Creeps folder of the Godot demo projects page instead of the main repository page that contains multiple games.
