From 78a4676e00776807e9bc17623d38d41c24453cb4 Mon Sep 17 00:00:00 2001
From: qsm-odoo <qsm@odoo.com>
Date: Thu, 23 Oct 2025 13:54:35 +0000
Subject: [PATCH] [IMP] developer: explain the new `<asset>` tag added as a fix

Also removes outdated things in the `<template>` tag documentation and
reviews it a bit.

See https://github.com/odoo/odoo/pull/104836

task-2963840

closes odoo/documentation#15215

X-original-commit: f7777d9a36abbcc4f02f14e1efcc77e773b04478
Related: odoo/odoo#235124
Related: odoo/enterprise#99190
Related: odoo/design-themes#1177
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
---
 .../howtos/website_themes/theming.rst         |  8 +++
 content/developer/reference/backend/data.rst  | 66 +++++++++++++++++--
 .../developer/reference/frontend/assets.rst   | 12 ++++
 3 files changed, 79 insertions(+), 7 deletions(-)

diff --git a/content/developer/howtos/website_themes/theming.rst b/content/developer/howtos/website_themes/theming.rst
index 845d6f497..418478c38 100644
--- a/content/developer/howtos/website_themes/theming.rst
+++ b/content/developer/howtos/website_themes/theming.rst
@@ -750,6 +750,14 @@ By reading the source code, templates related to options are easily found.
    <template id="..." inherit_id="..." name="..." active="True"/>
    <template id="..." inherit_id="..." name="..." active="False"/>
 
+.. seealso::
+
+   In such cases, the ``<template id="...">`` syntax should be preferred over
+   the ``<record id="..." model="ir.ui.view">`` syntax when defining the record
+   in XML.
+
+   See :ref:`reference/data/template`, especially about the ``active`` value.
+
 .. _theming/module/views/presets:
 
 Presets
diff --git a/content/developer/reference/backend/data.rst b/content/developer/reference/backend/data.rst
index dcfc40d85..c057395c6 100644
--- a/content/developer/reference/backend/data.rst
+++ b/content/developer/reference/backend/data.rst
@@ -208,6 +208,8 @@ data files provide shorter alternatives to defining them using
 
 Defines an ``ir.ui.menu`` record with a number of defaults and fallbacks:
 
+.. rst-class:: o-definition-list
+
 ``parent``
     * If a ``parent`` attribute is set, it should be the :term:`external id`
       of an other menu item, used as the new item's parent
@@ -239,6 +241,8 @@ Defines an ``ir.ui.menu`` record with a number of defaults and fallbacks:
 Creates a :ref:`QWeb view <reference/view_architectures/qweb>` requiring only the ``arch``
 section of the view, and allowing a few *optional* attributes:
 
+.. rst-class:: o-definition-list
+
 ``id``
     the view's :term:`external identifier`
 ``name``, ``inherit_id``, ``priority``
@@ -249,13 +253,61 @@ section of the view, and allowing a few *optional* attributes:
     as a primary
 ``groups``
     comma-separated list of group :term:`external identifiers`
-``page``
-    if set to ``"True"``, the template is a website page (linkable to,
-    deletable)
-``optional``
-    ``enabled`` or ``disabled``, whether the view can be disabled (in the
-    website interface) and its default status. If unset, the view is always
-    enabled.
+``active``
+    indicates whether the view is active. If inactive, its XPath rules won’t be
+    applied, which is thus mainly relevant for views with ``inherit_id``
+
+    .. note::
+
+        Defining the ``active`` value on the ``<template>`` node itself comes
+        with a subtlety: it is only considered when creating the record. On
+        subsequent updates, the view will be updated but not its ``active``
+        status.
+
+.. _reference/data/asset:
+
+``asset``
+---------
+
+Creates an :ref:`asset <frontend/assets/ir_asset>`.
+
+.. example::
+    .. code-block:: xml
+
+        <asset id="website_something.some_style_asset" name="Some style asset" active="False">
+            <bundle>web.assets_frontend</bundle>
+            <path>website_something/static/src/some_style.scss</path>
+        </asset>
+
+**Attributes**
+
+.. rst-class:: o-definition-list
+
+``id``
+    the asset's :term:`external identifier`
+``name``
+    same as the corresponding field on ``ir.asset``
+``active`` (optional)
+    indicates whether the asset is active
+
+    .. note::
+
+        Same as ``<template>``, defining the ``active`` value on the ``<asset>``
+        node itself comes with a subtlety: it is only considered when creating
+        the record. On subsequent updates, the asset will be updated but not its
+        ``active`` status.
+
+**Child elements**
+
+.. rst-class:: o-definition-list
+
+``<bundle>`` and ``<path>``
+    required to define the corresponding fields on ``ir.asset`` (the
+    ``directive`` field can be controlled using the ``directive`` attribute on
+    the ``<bundle>`` child)
+
+``<field>`` (optional)
+    just like in a normal ``<record>``, to define more field values as needed
 
 .. _reference/data/csvdatafiles:
 
diff --git a/content/developer/reference/frontend/assets.rst b/content/developer/reference/frontend/assets.rst
index 7f28b412c..76e3a52df 100644
--- a/content/developer/reference/frontend/assets.rst
+++ b/content/developer/reference/frontend/assets.rst
@@ -362,3 +362,15 @@ manifest counterparts.
 `sequence` (default= `16`)
     Loading order of the asset records (ascending). A sequence lower than 16 means
     that the asset will be processed *before* the ones declared in the manifest.
+
+.. seealso::
+
+    Note that the ``ir.asset`` use case is mainly for website-related
+    applications, as it allows for conditional assets (for example, when a style
+    option is enabled).
+
+    In such cases, the ``<asset id="...">`` syntax should be preferred over the
+    ``<record id="..." model="ir.asset">`` syntax when defining the record in
+    XML.
+
+    See :ref:`reference/data/asset`, especially about the ``active`` value.