odoo · guga-odoo · Jan 22, 2026 · Jan 21, 2026 · Jan 20, 2026 · Jan 20, 2026
diff --git a/.weblate.json b/.weblate.json
@@ -1,6 +1,6 @@
 {
     "projects": {
-        "odoo-19-doc": [
+        "odoo-master-doc": [
             {
                 "name": "administration",
                 "filemask": "locale/*/LC_MESSAGES/administration.po",
@@ -61,16 +61,16 @@
                 "filemask": "locale/*/LC_MESSAGES/services.po",
                 "new_base": "locale/sources/services.pot"
             },
+            {
+                "name": "sphinx",
+                "filemask": "locale/*/LC_MESSAGES/sphinx.po",
+                "new_base": "locale/sources/sphinx.pot"
+            },
             {
                 "name": "studio",
                 "filemask": "locale/*/LC_MESSAGES/studio.po",
                 "new_base": "locale/sources/studio.pot"
             },
-            {
-                "name": "user_settings",
-                "filemask": "locale/*/LC_MESSAGES/settings.po",
-                "new_base": "locale/sources/settings.pot"
-            },
             {
                 "name": "websites",
                 "filemask": "locale/*/LC_MESSAGES/websites.po",

diff --git a/Makefile b/Makefile
@@ -13,6 +13,10 @@ ifndef CURRENT_LANG
   CURRENT_LANG = en
 endif
 
+ifndef EXPORT_PATH
+  EXPORT_PATH = locale/sources
+endif
+
 SPHINX_BUILD   = sphinx-build
 CONFIG_DIR     = .
 SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
@@ -27,7 +31,7 @@ SOURCE_DIR     = content
 
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
-  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
+  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/saas-19.2
 endif
 ifneq ($(CURRENT_LANG),en)
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
@@ -69,7 +73,7 @@ latexpdf:
 
 gettext:
 	@echo "Generating translatable files..."
-	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
+	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) $(EXPORT_PATH)
 	@echo "Generation finished."
 
 $(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
@@ -91,7 +95,8 @@ static: $(HTML_BUILD_DIR)/_static/style.css
 test:
 	@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer redirects
 
-# Similar as `test`, but called only manually by content reviewers to trigger extra checks.
+# Similar to `test`, but called only manually by content reviewers to specify a path and a max line
+# length.
 review:
 	@read -p "Enter relative content path: " path; read -p "Enter max line length (default: 100): " line_length; \
 	if [ -z "$$path" ]; then echo "Error: Path cannot be empty"; exit 1; fi; \

diff --git a/README.md b/README.md
@@ -1,38 +1,67 @@
 # Odoo documentation
 
-## Build the documentation locally
+## Build the documentation
 
 ### Requirements
 
-- Git
-- Python 3.6, 3.7, or 3.8
-- Python dependencies listed in the file `requirements.txt`.
+- [Git](https://git-scm.com/install)
+- [Python 3.10 to 3.14](https://www.python.org/downloads/).
 - Make
-- A local copy of the [odoo/odoo repository](https://github.com/odoo/odoo) (optional)
-- A local copy of the [odoo/upgrade-util repository](https://github.com/odoo/upgrade-util) (optional)
+- Python dependencies from `requirements.txt` (see instructions below)
+- A local copy of the [odoo/odoo](https://github.com/odoo/odoo) repository (optional)
+- A local copy of the [odoo/upgrade-util](https://github.com/odoo/upgrade-util) repository
+  (optional)
 
-### Instructions
+### Quick start
 
-1. In a terminal, navigate to the root directory of the documentation and build it `make`.
-   Additional commands are available with `make help`.
-2. Open the file `documentation/_build/html/index.html` in your web browser.
-3. See [this guide](https://www.odoo.com/documentation/latest/contributing/documentation.html)
-   for more detailed instructions.
+1. Create and activate a virtual environment.
+   - On Linux and macOS: `python3 -m venv .venv && source .venv/bin/activate`
+   - On Windows (PowerShell): `py3 -m venv .venv; .\.venv\Scripts\Activate.ps1`
+2. Install the Python dependencies: `pip install -r requirements.txt`
+3. Build the documentation: `make html` (see more commands with `make help`)
+4. Open `documentation/_build/html/index.html` in your web browser.
 
-Optional: place your local copy of the `odoo/odoo` and `odoo/upgrade-util` repositories in
-the parent directory or in the root directory of the documentation to build the latter
-with the documented Python docstrings.
+### Additional build options
 
-## Contribute to the documentation
+- `make fast` to build the documentation with a shallow menu (faster).
+- `make clean` to delete the build files.
+- `make test` to run the guidelines tests.
+- `make html CURRENT_LANG=fr` to build the documentation only in French.
+- `make html CURRENT_LANG=fr LANGUAGES=en,fr,de` to build the documentation in French and enable the
+  language switcher, with the specified LANGUAGES as available languages. This command must be
+  invoked for each CURRENT_LANG you want to build.
+- `make html VERSIONS=17.0,18.0,saas-18.4,19.0,master` to build the documentation in the **current
+  version** and enable the version switcher, with the specified VERSIONS as available versions. This
+  command must be invoked for each of the VERSIONS you want to build.
 
-For contributions to the content of the documentation, please refer to the
-[Introduction Guide](https://www.odoo.com/documentation/latest/contributing/documentation.html).
+The list of available languages can be found in `conf.py`, in the `languages_names` variable.
+
+When building the documentation for a specific language or version, the build files are created in
+`documentation/_build/html/<language>/`, `documentation/_build/html/<version>/` or
+`documentation/_build/html/<version>/<language>/`.
+
+### Using local Odoo sources
+
+If you have local checkouts of `odoo/odoo` and/or `odoo/upgrade-util`, place them either:
+- as siblings of this repository (in the parent directory), or
+- inside the `documentation` directory.
 
-To **report a content issue**, **request new content** or **ask a question**, use the
-[repository's issue tracker](https://github.com/odoo/documentation/issues).
+When present in one of these locations, the build will include Python docstrings from those
+repositories if their version matches the documentation's version.
 
-## Learn More
+### Troubleshooting
+
+- Verify your Python version: `python3 --version` (must be 3.10–3.14)
+- Ensure your virtual environment is active and dependencies are installed.
+- If you have made changes to the file structure, try `make clean` before building.
+- If the language or version switchers redirect to a missing file, check that you have built the
+  documentation for all available languages and versions.
+- The "Developer" documentation is only available in English.
+
+## Contribute to the documentation
+
+For contributions to the content of the documentation, see the
+[Introduction Guide](https://www.odoo.com/documentation/latest/contributing/documentation.html).
 
-To learn more about Odoo, in addition to the documentation, have a look at
-[the official eLearning](https://odoo.com/slides) and
-[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
+To report a content issue, request new content, or ask a question, use the
+[issue tracker](https://github.com/odoo/documentation/issues).
diff --git a/conf.py b/conf.py
@@ -22,7 +22,7 @@
 # `version` is the version info for the project being documented, acts as replacement for |version|,
 # also used in various other places throughout the built documents.
 # `release` is the full version, including a/b/rc tags. Acts as replacement for |release|.
-version = release = 'master'
+version = release = 'saas-19.2'
 
 # `current_branch` is the technical name of the current branch.
 # E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
@@ -232,12 +232,13 @@
 # option. If a provided version has no label, the version string is used as label.
 versions_names = {
     'master': "Master",
+    'saas-19.2': "Odoo 19.2",
+    'saas-19.1': "Odoo 19.1",
+    '19.0': "Odoo 19",
     'saas-18.4': "Odoo 18.4",
     'saas-18.3': "Odoo 18.3",
     'saas-18.2': "Odoo 18.2",
-    'saas-18.1': "Odoo 18.1",
     '18.0': "Odoo 18",
-    'saas-17.4': "Odoo 17.4",
     '17.0': "Odoo 17",
     '16.0': "Odoo 16",
 }
@@ -390,11 +391,13 @@ def source_read_replace(app, docname, source):
 def upgrade_util_signature_rewrite(app, domain, objtype, contentnode):
     # Same as add_module_names=False but **only** for odoo.upgrade.util functions or classes
     signature = contentnode.parent[0]
-    if objtype == 'function' and signature.astext().startswith('odoo.upgrade.util.'):
+    if objtype == 'function' and signature.astext().startswith(('odoo.upgrade.util.', 'odoo.upgrade.testing.')):
         # <odoo.upgrade.util.modules>, <modules_installed>, <(cr, *modules)>
+        # <odoo.upgrade.testing>, <change_version>, <(version_str)>
         signature.pop(0)
-    if objtype == 'class' and signature.astext().startswith('class odoo.upgrade.util.'):
+    if objtype == 'class' and signature.astext().startswith(('class odoo.upgrade.util.', 'class odoo.upgrade.testing.')):
         # <class >, <odoo.upgrade.util.pg.>, <PGRegexp>
+        # <class >, <odoo.upgrade.testing.>, <UpgradeCase>
         signature.pop(1)
 
 def setup(app):

diff --git a/content/administration.rst b/content/administration.rst
@@ -10,7 +10,7 @@ Database management
 These guides provide instructions on how to install, maintain and upgrade Odoo databases.
 
 .. seealso::
-    :doc:`History of Versions <administration/supported_versions>`
+    :doc:`History of Versions <administration/standard_extended_support>`
 
 Installation
 ============
@@ -60,6 +60,6 @@ functionalities, including functional support, upgrades, and hosting. `Pricing
     administration/on_premise
     administration/upgrade
     administration/neutralized_database
-    administration/supported_versions
+    administration/standard_extended_support
     administration/mobile
     administration/odoo_accounts
diff --git a/content/administration/hosting.rst b/content/administration/hosting.rst
@@ -18,7 +18,7 @@ To Odoo Online
 
 .. important::
    - Odoo Online is *not* compatible with **non-standard apps**.
-   - The database's current version must be :doc:`supported <supported_versions>`.
+   - The database's current version must be :doc:`supported <standard_extended_support>`.
 
 #. Create a :ref:`duplicate of the database <on-premise/duplicate>`.
 #. In this duplicate, uninstall all **non-standard apps**.
@@ -39,17 +39,17 @@ To Odoo Online
 To Odoo.sh
 ----------
 
-Follow the instructions found in :ref:`the Import your database section
-<odoo_sh_import_your_database>` of the Odoo.sh *Create your project* documentation.
+Follow the instructions found in :ref:`the Import a database section <odoo-sh/create/import>` of the
+Odoo.sh *Create a project* documentation.
 
 Transferring an Odoo Online database
 ====================================
 
 .. important::
-   Odoo Online's :ref:`intermediary versions <supported_versions>` are not supported by Odoo.sh or
-   on-premise. Therefore, if the database to transfer is running an intermediary version, it must be
-   upgraded first to the next :ref:`major version <supported_versions>`, waiting for its release if
-   necessary.
+   Odoo Online's :doc:`intermediary versions <standard_extended_support>` are not supported by
+   Odoo.sh or on-premise. Therefore, if the database to transfer is running an intermediary version,
+   it must be upgraded first to the next :doc:`major version <standard_extended_support>`, waiting
+   for its release if necessary.
 
    .. example::
       Transferring an online database running on Odoo 16.3 would require first upgrading it to Odoo
@@ -82,8 +82,8 @@ To Odoo.sh
    next to the database name, then selecting :icon:`fa-cloud-download` :guilabel:`Download`. If the
    download fails due to the file being too large, `contact Odoo support
    <https://www.odoo.com/help>`_.
-#. Follow the instructions found in :ref:`the Import your database section
-   <odoo_sh_import_your_database>` of the Odoo.sh *Create your project* documentation.
+#. Follow the instructions found in :ref:`the Import a database section <odoo-sh/create/import>` of
+   the Odoo.sh *Create a project* documentation.
 
 Transferring an Odoo.sh database
 ================================
@@ -119,5 +119,5 @@ To Odoo Online
 To on-premise
 -------------
 
-#. Download a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
+#. Download a :ref:`backup of your Odoo.sh production database <odoo-sh/branches/tabs/backups>`.
 #. Restore the database from the database manager on your local server using the backup.
diff --git a/content/administration/mobile.rst b/content/administration/mobile.rst
@@ -61,7 +61,4 @@ The Odoo mobile apps are available for download on the `Google Play Store
 <https://play.google.com/store/apps/details?id=com.odoo.mobile>`_ and `Apple App Store
 <https://apps.apple.com/app/odoo/id1272543640>`_.
 
-.. important::
-   The iOS app might not be updated and might be deprecated at some point in the future.
-
 While the store apps support multi-accounts, they are not compatible with SSO authentication.