This guide explains how to contribute to Godot's documentation, be it by writing or reviewing pages.
If you want to translate pages or the class reference from English to other languages, read Editor and docs localization.
To modify or create pages in the reference manual, you need to edit
files in the godot-docs GitHub repository. Modifying those pages in a pull
request triggers a rebuild of the online documentation upon merging.
For details on Git usage and the pull request workflow, please refer to the Pull request workflow page. Most of what it describes regarding the main godotengine/godot repository is also valid for the docs repository.
Co to jest dokumentacja Godota¶
The Godot documentation is intended as a comprehensive reference manual for the Godot game engine. It is not meant to contain step-by-step tutorials, except for two game creation tutorials in the Getting Started section.
We strive to write factual content in an accessible and well-written language. To contribute, you should also read:
The Porady dotyczące pisania dokumentacji. There, you will find rules and recommendations to write in a way that everyone understands.
The content guidelines. They explain the principles we follow to write the documentation and the kind of content we accept.
Pull Requests should use the
master branch by default. Only make Pull
Requests against other branches (e.g.
3.0) if your changes only
apply to that specific version of Godot.
Though less convenient to edit than a wiki, this Git repository is where we write the documentation. Having direct access to the source files in a revision control system is a plus to ensure our documentation quality.
Editing existing pages¶
To edit an existing page, locate its
.rst source file and open it in your
favorite text editor. You can then commit the changes, push them to your fork,
and make a pull request. Note that the pages in
classes/ should not be
edited here. They are automatically generated from Godot’s XML class
See Contributing to the class reference for details.
To build the manual and test changes on your computer, see Building the manual with Sphinx.
Editing pages online¶
You can edit the documentation online by clicking the Edit on GitHub link in the top-right of every page.
Doing so takes you to the GitHub text editor. You need to have a GitHub account and to log in to use it. Once logged in, you can propose change like so:
Click the Edit on GitHub button.
On the GitHub page you're taken to, click the pencil icon in the top-right corner near the Raw, Blame, and Delete buttons. It has the tooltip "Fork this project and edit the file".
Edit the text in the text editor.
At the bottom of the web page, summarize the changes you made and click the button Propose file change. Make sure to replace the placeholder "Update file.rst" by a short but clear one-line description, as this is the commit title.
On the following screens, click the Create pull request button until you see a message like Username wants to merge 1 commit into godotengine:master from Username:patch-1.
Another contributor will review your changes and merge them into the docs if they're good. They may also make changes or ask you to do so before merging.
Adding new pages¶
Before adding a new page, please ensure that it fits in the documentation:
Look for existing issues or open a new one to see if the page is necessary.
Ensure there isn't a page that already covers the topic.
Read our Content guidelines.
To add a new page, create a
.rst file with a meaningful name in the section you
want to add a file to, e.g.
You should then add your page to the relevant "toctree" (table of contents,
tutorials/3d/index.rst). Add your new filename to the list on a new
line, using a relative path and no extension, e.g. here
Always begin pages with their title and a Sphinx reference name:
.. _doc_insert_your_title_here: Insert your title here ======================
_doc_insert_your_title_here and the title should match.
The reference allows linking to this page using the
: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).
Write your titles like plain sentences, without capitalizing each word:
Good: Understanding signals in Godot
Bad: Understanding Signals In Godot
Only propers nouns, projects, people, and node class names should have their first letter capitalized.
Sphinx and reStructuredText syntax¶
Sphinx uses specific reST comments to do specific operations, like defining the
table of contents (
.. toctree::) or cross-referencing pages. Check the
official Sphinx documentation for more details. To learn
how to use Sphinx directives like
.. note:: or
.. seealso::, check out
the Sphinx directives documentation.
Adding images and attachments¶
To add images, please put them in an
img/ folder next to the
.rst file with
a meaningful name and include them in your page with:
.. image:: img/image_name.png
Similarly, you can include attachments, like assets as support material for a
tutorial, by placing them into a
files/ folder next to the
.rst file, and
using this inline markup:
This documentation and every page it contains is published under the terms of the Creative Commons Attribution 3.0 license (CC-BY-3.0), with attribution to "Juan Linietsky, Ariel Manzur and the Godot community".
Pisząc dokumentację w repozytorium GitHub, zgadzasz się na dystrybuowanie twoich zmian z powyższą licencją.