Commit Graph
12 Commits
Author SHA1 Message Date
Hugo Locurcio 8a6ad4c926 Replace uses of shorthand codeblock syntax to avoid issues with localization
Previously, many paragraphs in the documentation used `::` at the end of a line
as a replacement for a single colon (and `::` on the following line).
Due to this, the `::` was part of the extracted string for localization.
Weblate also showed a warning about the trailing `::`, as it's not
normally expected to be there.

This change requires translators to revalidate all modified strings.
However, considering many of those have broken code blocks due to translators
replacing `::` with `:`, it can be a good idea.

This also adds documentation writing guidelines for code blocks and admonitions.
This commit does not modify existing admonitions in any way (as this would
lead to a much larger diff, and require more localizable text to be revalidated
by translators).
2025-05-30 02:02:30 +02:00
tetrapod00 c4d3aa134a Standardize RST header syntax 2024-12-29 13:44:09 -08:00
Wilson E. AlvarezandMax Hilbrunner feeea91cdf Add ThreadSanitizer usage note under Linux (#8908)
* Add ThreadSanitizer usage note under Linux

---------

Co-authored-by: Max Hilbrunner <mhilbrunner@users.noreply.github.com>
2024-11-17 14:50:17 +01:00
Hugo Locurcio 93261ab5d7 Harmonize Bash command syntax for easier line selection and copy-pasting
- Remove prompt or `$` sign which makes triple-click based selection
  more difficult and time-consuming.
- Use `platform` instead of `p` alias in all SCons examples.
2024-09-15 16:27:34 +02:00
Hugo Locurcio 95fb178429 Add support for user-provided comments with Giscus
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.
2024-01-11 17:51:53 +01:00
danfountgames 4367d18826 The most important line was missing from the example entitlements file. 2023-11-02 11:48:14 +00:00
Hugo Locurcio 338c1f6351 Update SCons link-time optimization option for 3.5 and later 2023-06-30 12:55:41 +02:00
Hugo Locurcio b5e9b75bec Document setting up Vulkan validation layers on desktop platforms 2023-05-05 19:54:37 +02:00
Hugo Locurcio 123fce7e07 Add a page on using GCC/Clang/MSVC sanitizers
This also covers Web-specific Emscripten options to enable its own
sanitizers.
2023-04-08 20:08:24 +02:00
John Veness 08498ef96a Change capitalization of Project Manager 2023-03-13 20:08:49 +00:00
Yuri SizovandCalebJohn 6c08ab05d2 Split general debugging and architecture diagram documentation
Co-authored-by: CalebJohn <git@calebjohn.ca>
2023-01-10 03:26:04 +03:00
Yuri Sizov dbfe3b1d26 Reorganize documentation for contributors
- Merge Community/Contributing and Engine Development into one top-level section, Contributing.
- Structure it in a way that gives equal priority to various ways to contribute, including documentation.
- Rename several articles to be more comprehensive and in line with the overall state of the documentation.
- Rewrite the guide for class reference contributions.
2023-01-10 01:49:30 +03:00