0
0
Blender user manual
Go to file
2024-02-17 04:19:44 +01:00
.gitea Fix wrong URL in Gitea commit message templates 2023-05-15 17:36:58 +02:00
build_files revert split limit (not like py), redundant slice end 2024-02-17 04:19:44 +01:00
manual Merge branch 'blender-v4.1-release' 2024-02-13 19:39:55 +02:00
tools Tools: Move script to translations sub directory 2024-02-04 14:13:13 -05:00
.editorconfig editorconfig: add HTML (matching Blender's settings) 2023-12-08 13:12:30 +11:00
.gitattributes Git: Remove gitattributes 2023-04-21 00:58:21 +00:00
.gitignore Add support for python virtual environments 2024-01-20 15:15:17 -05:00
LICENSE Cleanup: Non-unicode characters 2024-01-19 18:51:01 -05:00
make.bat Restructure Scripts and Resources 2024-01-14 01:58:54 -05:00
Makefile Fix update_po after recent refactors. 2024-01-22 12:32:07 +01:00
pyproject.toml Restructure Scripts and Resources 2024-01-14 01:58:54 -05:00
README.md Cleanup: Non-unicode characters 2024-01-19 18:51:01 -05:00
requirements.txt Build: Update theme to latest official version 2024-01-14 14:45:16 -05:00

Blender Documentation (latest manual)

Welcome to the Blender User Documentation project. We are actively searching for contributors and documentation module owners.

The Blender Manual is written using reStructuredText (RST) and is built with Sphinx.

If you want to start contributing or want to have a look at the manual, here we have some instructions:

How to build & edit the docs locally

Before you start contributing it may be helpful to read the style guides which give instructions on how to write with RST and some goals of the manual.

Now that you are familiar with the process, you can get setup, edit, and contribute your changes by following these links:

Note: We realize this may be intimidating if you're not familiar with Git or making patches, you may also submit the modified file as an Issue.

Documentation Team

The coordination of the Blender Manual is run by a set of Administrators, which are responsible for managing the whole project and infrastructures (listed above).

If you are interested in becoming a contributor, please contact us on the developer forum.

Translations

For translations, we use Sphinx's internationalization package. To get started see the contribution guide for translations.

*Note: If you are a new translator who wants to start translating a new language that is not listed open an issue on the issue tracker and we would be glad to set it up for you.