introduction.rst 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. .. _doc_about_intro:
  2. Introduction
  3. ============
  4. ::
  5. func _ready():
  6. $Label.text = "Hello world!"
  7. Welcome to the official documentation of Godot Engine, the free and open source
  8. community-driven 2D and 3D game engine! Behind this mouthful, you will find a
  9. powerful yet user-friendly tool that you can use to develop any kind of game,
  10. for any platform and with no usage restriction whatsoever.
  11. This page aims at giving a broad presentation of the engine and of the contents
  12. of this documentation, so that you know where to start if you are a beginner or
  13. where to look if you need info on a specific feature.
  14. About Godot Engine
  15. ------------------
  16. A game engine is a complex tool, and it is therefore difficult to present Godot
  17. in a few words. Here's however our PR presentation, which you are free to reuse
  18. if you need a quick writeup about Godot Engine.
  19. Godot Engine is a feature-packed, cross-platform game engine to create 2D
  20. and 3D games from a unified interface. It provides a comprehensive set of
  21. common tools, so that users can focus on making games without having to
  22. reinvent the wheel. Games can be exported in one click to a number of
  23. platforms, including the major desktop platforms (Linux, macOS, Windows)
  24. as well as mobile (Android, iOS) and web-based (HTML5) platforms.
  25. Godot is completely free and open source under the permissive MIT
  26. license. No strings attached, no royalties, nothing. Users' games are
  27. theirs, down to the last line of engine code. Godot's development is fully
  28. independent and community-driven, empowering users to help shape their
  29. engine to match their expectations. It is supported by the `Software
  30. Freedom Conservancy <https://sfconservancy.org>`_ not-for-profit.
  31. For a more in-depth view of the engine, you are encouraged to read this
  32. documentation further, especially the :ref:`Step by step
  33. <toc-learn-step_by_step>` tutorial.
  34. About the documentation
  35. -----------------------
  36. This documentation is continuously written, corrected, edited and revamped by
  37. members of the Godot Engine community. It is edited via text files in the
  38. `reStructuredText <http://www.sphinx-doc.org/en/stable/rest.html>`_ markup
  39. language and then compiled into a static website/offline document using the
  40. open source `Sphinx <http://www.sphinx-doc.org>`_ and `ReadTheDocs
  41. <https://readthedocs.org/>`_ tools.
  42. .. note:: You can contribute to Godot's documentation by opening issue tickets
  43. or sending patches via pull requests on its GitHub
  44. `source repository <https://github.com/godotengine/godot-docs>`_, or
  45. translating it into your language on `Hosted Weblate
  46. <https://hosted.weblate.org/projects/godot-engine/godot-docs/>`_.
  47. All the contents are under the permissive Creative Commons Attribution 3.0
  48. (`CC-BY 3.0 <https://creativecommons.org/licenses/by/3.0/>`_) license, with
  49. attribution to "Juan Linietsky, Ariel Manzur and the Godot Engine community".
  50. Organisation of the documentation
  51. ---------------------------------
  52. This documentation is organised in five sections with an impressively
  53. unbalanced distribution of contents – but the way it is split up should be
  54. relatively intuitive:
  55. - The :ref:`sec-general` section contains this introduction as well as
  56. information about the engine, its history, its licensing, authors, etc. It
  57. also contains the :ref:`doc_faq`.
  58. - The :ref:`sec-learn` section is the main *raison d'être* of this
  59. documentation, as it contains all the necessary information on using the
  60. engine to make games. It starts with the :ref:`Step by step
  61. <toc-learn-step_by_step>` tutorial which should be the entry point for all
  62. new users.
  63. - The :ref:`sec-tutorials` section, on the other hand, can be read as needed,
  64. in any order. It contains many feature-specific tutorials and documentations.
  65. - The :ref:`sec-devel` section is intended for advanced users and contributors
  66. to the engine development, with information on compiling the engine,
  67. developing C++ modules or editor plugins.
  68. - The :ref:`sec-community` gives information related to contributing to the
  69. engine development and the life of its community, e.g. how to report bugs,
  70. help with the documentation, etc. It also points to various community channels
  71. like IRC and Discord and contains a list of recommended third-party tutorials
  72. outside of this documentation.
  73. - Finally, the :ref:`sec-class-ref` is the documentation of the Godot API,
  74. which is also available directly within the engine's script editor. It is
  75. generated automatically from a file in the main source repository, therefore
  76. the generated files of the documentation are not meant to be modified. See
  77. :ref:`doc_updating_the_class_reference` for details.
  78. In addition to this documentation you may also want to take a look at the
  79. various `Godot demo projects <https://github.com/godotengine/godot-demo-projects>`_.
  80. Have fun reading and making games with Godot Engine!