Documentation guidelines

godot-docs GitHub repository and the docs front page on what steps to follow and how to contact the docs team.

How to contribute

godot-docs GitHub repository. The HTML (or PDF and EPUB) documentation is generated from the .rst files (reStructuredText markup language) in that repository. Modifying those pages in a pull request and getting it merged will trigger a rebuild of the online documentation. See also Pull request workflow page. Most of what it describes regarding the main godotengine/godot repository is also valid for the docs repository. Warning Godot engine repository. We generate the Godot API section of this documentation from them. If you want to update the description of a class, its methods, or properties, read Contributing to the class reference. Warning API reference, please note that it should not be done in the godot-docs repository. Instead, you should edit the doc/classes/* XML files of Godot’s main repository. These files are then later used to generate the in-editor documentation as well as the API reference of the online docs. Read more here: Contributing to the class reference.

docs.godotengine.org, you’ll see an Edit on GitHub hyperlink at the top right of the page. Once you’ve created a GitHub account, you can propose changes to a page you’re reading as follows:

  1. Edit on GitHub button.
  2. Raw, Blame and History buttons. It has the tooltip “Edit the file in a fork of this project”.
  3. Complete all the edits you want to make for that page.
  4. Propose file change when done.
  5. Create pull request button until you see a message like Username wants to merge 1 commit into godotengine:master from Username:patch-6.
  6. A reviewer will evaluate your changes and incorporate them into the docs if they’re acceptable. You might also be asked to make modifications to your changes before they’re included.

    What makes good documentation?

    Docs writing guidelines. We differentiate tutorial pages from other documentation pages by these definitions:
  • Tutorial: a page aiming at explaining how to use one or more concepts in the editor or scripts in order to achieve a specific goal with a learning purpose (e.g. “Making a simple 2d Pong game”, “Applying forces to an object”).
  • Documentation: a page describing precisely one and only one concept at a time, if possible exhaustively (e.g. the list of methods of the Sprite class, or an overview of the input management in Godot). You are free to write the kind of documentation you wish, as long as you respect the following rules (and the ones on the repo).

    Titles

    Always begin pages with their title and a Sphinx reference name:
    1. .. _doc_insert_your_title_here:Insert your title here======================
    :ref: format, e.g. :ref:doc_insert_your_title_here`` would link to the above example page (note the lack of leading underscore in the reference). Also, avoid American CamelCase titles: title’s first word should begin with a capitalized letter, and every following word should not. Thus, this is a good example: - And this is a bad example: - Only project, people and node class names should have capitalized first letter.

    Translating existing pages

    Hosted Weblate. Godot i18n repository where you can see when the data was last synchronized.

    License

    Creative Commons Attribution 3.0 license (CC-BY-3.0)), with attribution to “Juan Linietsky, Ariel Manzur and the Godot community”. By contributing to the documentation on the GitHub repository, you agree that your changes are distributed under this license.