[IMP] spreadsheet: expanding pivot table documentation

.weblate.json

@@ -1,6 +1,6 @@
 {
     "projects": {
-        "odoo-19-doc": [
+        "odoo-s19-1-doc": [
             {
                 "name": "administration",
                 "filemask": "locale/*/LC_MESSAGES/administration.po",
@@ -61,6 +61,11 @@
                 "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",

Makefile

@@ -31,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.1
 endif
 ifneq ($(CURRENT_LANG),en)
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)

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.1'
 
 # `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,13 +232,18 @@
 # option. If a provided version has no label, the version string is used as label.
 versions_names = {
     'master': "Master",
+    'saas-19.3': "Odoo 19.3",
+    '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",
     '18.0': "Odoo 18",
     '17.0': "Odoo 17",
     '16.0': "Odoo 16",
+    '15.0': "Odoo 15",
+    '14.0': "Odoo 14",
 }
 
 # The labels used in the language switcher to show the languages provided with the `languages`

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.

content/administration/odoo_online.rst

@@ -175,6 +175,6 @@ To retrieve a list of all databases displayed under the `database manager
           headers={
               "Authorization": f"bearer {APIKEY}",
               "X-Odoo-Database": "openerp",
-          }
+          },
           json={},
       )

content/administration/odoo_sh/first_module.rst

@@ -172,11 +172,8 @@ From an Odoo.sh editor terminal:
 
   $ git push https HEAD:feature-1
 
-The above command is explained in the section
-:ref:`Commit & Push your changes
-<odoosh-gettingstarted-online-editor-push>` of the
-:ref:`Online Editor <odoosh-gettingstarted-online-editor>`
-chapter.
+The above command is explained in the section :ref:`Commit and push changes
+<odoo-sh/editor/commit>` of the :doc:`Online editor page <getting_started/online_editor>`.
 It includes the explanation regarding the fact you will be prompted to type your username and
 password, and what to do if you use the two-factor authentication.
 

content/administration/odoo_sh/getting_started.rst

@@ -53,6 +53,5 @@ Odoo.sh involves different types of users, each with a specific role in the proj
    getting_started/create
    getting_started/branches
    getting_started/builds
-   getting_started/status
    getting_started/settings
-   getting_started/online-editor
+   getting_started/online_editor

content/administration/odoo_sh/getting_started/branches.rst

@@ -113,9 +113,8 @@ been accidentally deleted from the production database. It is possible to create
 staging databases.
 
 .. warning::
-   Databases created for staging branches are intended to last up to three months. After that, they
-   can be automatically blocked without prior notice. Only rebuilding the branch will allow you to
-   use that specific branch again.
+   Databases created for staging branches are automatically deleted after one month. To use the
+   branch again, you must rebuild it.
 
 .. _odoo-sh/branches/stages/development:
 
@@ -289,7 +288,7 @@ shell consoles.
 You can open multiple tabs and drag and drop them to arrange the layout as you wish.
 
 .. seealso::
-   :doc:`Online editor documentation <online-editor>`.
+   :doc:`Online editor documentation <online_editor>`.
 
 .. _odoo-sh/branches/tabs/monitor: