Doc/709 reference man cross ref (#1548)

* Refman fixes

* Update config.pyi

---------

Co-authored-by: jrobinAV <jrobinAV@users.noreply.github.com>

taipy/config/common/_config_blocker.py

@@ -41,8 +41,7 @@ class _ConfigBlocker:
                 if cls.__block_config_update:
                     error_message = (
                         "The Core service should be stopped by running core.stop() before"
-                        " modifying the Configuration. For more information, please refer to:"
-                        " https://docs.taipy.io/en/latest/manuals/running_services/#running-core."
+                        " modifying the Configuration."
                     )
                     cls.__logger.error(f"ConfigurationUpdateBlocked: {error_message}")
                     raise ConfigurationUpdateBlocked(error_message)

taipy/config/config.pyi

@@ -272,7 +272,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -324,7 +324,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -358,7 +358,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -391,7 +391,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
         Returns:
@@ -435,7 +435,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -470,7 +470,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -506,7 +506,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
         Returns:
@@ -535,7 +535,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -567,7 +567,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -625,7 +625,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -689,7 +689,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
         Returns:
@@ -738,7 +738,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -776,7 +776,7 @@ class Config:
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 

taipy/core/__init__.py

@@ -14,19 +14,18 @@
 The Taipy Core package is a Python library designed to build powerful, customized, data-driven back-end
 applications. It provides the tools to help Python developers transform their algorithms into a
 complete back-end application.
-More details on the [Taipy Core](../../core/index.md) functionalities are available in the user manual.
+More details on the Core functionalities are available in the user manual.
 
 To build a Taipy Core application, the first step consists of setting up the Taipy configuration to design
 your application's characteristics and behaviors.
 Import `Config^` from the `taipy.config^` module, then use the various methods of the `Config^` singleton class to
 configure your core application. In particular, configure the
-[data nodes](../../core/config/data-node-config.md), [tasks](../../core/config/task-config.md),
-and [scenarios](../../core/config/scenario-config.md).
-Please refer to the [Core configuration user manual](../../core/config/index.md) for more information and
-detailed examples.
+[data nodes](../../../userman/data-integration/data-node-config.md),
+[tasks](../../../userman/task-orchestration/scenario-config.md),
+and [scenarios](../../../userman/sdm/scenario/scenario-config.md).
 
 Once your application is configured, import module `import taipy as tp` so you can use any function described
-in the following section on [Functionc](#functions). In particular, the most used functions are `tp.create_scenario()`,
+in the following section on [Function](#functions). In particular, the most used functions are `tp.create_scenario()`,
 `tp.get_scenarios()`, `tp.get_data_nodes()`, `tp.submit()`, used to get, create, and submit entities.
 
 !!! Note
@@ -35,7 +34,7 @@ in the following section on [Functionc](#functions). In particular, the most use
     have a dedicated thread responsible for dispatching the submitted jobs to an available executor for their execution.
 
     In particular, this `Core^` service is automatically run when Core is used with Taipy REST or Taipy GUI. See the
-    [running services](../../run-deploy/run/running_services.md) page of the user manual for more details.
+    [running services](../../../run-deploy/run/running_services.md) page of the user manual for more details.
 """
 
 from ._init import *

taipy/core/config/core_section.py

@@ -40,9 +40,9 @@ class CoreSection(UniqueSection):
             The default value is 3.
         mode (str): The Taipy operating mode. By default, the `Core^` service runs in "development" mode.
             An "experiment" and a "production" mode are also available. Please refer to the
-            [Versioning management](../core/versioning/index.md) documentation page for more details.
+            [Versioning management](../../userman/versioning/index.md) documentation page for more details.
         version_number (str)): The identifier of the user application version. Please refer to the
-            [Versioning management](../core/versioning/index.md) documentation page for more details.
+            [Versioning management](../../userman/versioning/index.md) documentation page for more details.
         force (bool): If True, force the application run even if there are some conflicts in the
             configuration.
         core_version (str): The Taipy Core package version.

taipy/core/config/data_node_config.py

@@ -412,7 +412,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -472,7 +472,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -524,7 +524,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -567,7 +567,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
         Returns:
@@ -621,7 +621,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -670,7 +670,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -716,7 +716,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
         Returns:
@@ -755,7 +755,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -791,7 +791,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -855,7 +855,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -947,7 +947,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
         Returns:
@@ -1027,7 +1027,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 
@@ -1090,7 +1090,7 @@ class DataNodeConfig(Section):
             validity_period (Optional[timedelta]): The duration since the last edit date for which the data node can be
                 considered up-to-date. Once the validity period has passed, the data node is considered stale and
                 relevant tasks will run even if they are skippable (see the
-                [Task configs page](../core/config/task-config.md) for more details).
+                [Task configs page](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
                 If *validity_period* is set to None, the data node is always up-to-date.
             **properties (dict[str, any]): A keyworded variable length list of additional arguments.
 

taipy/core/cycle/cycle.py

@@ -64,7 +64,7 @@ class Cycle(_Entity, _Labeled):
 
     !!! example "Example for January cycle"
 
-        ![cycles](../refmans/img/cycles_january_colored.svg){ align=left width="250" }
+        ![cycles](../img/cycles_january_colored.svg){ align=left width="250" }
 
         Let's assume an end-user publishes production orders (i.e., a production plan) every
         month. During each month (the cycle), he/she will be interested in experimenting with
@@ -82,7 +82,7 @@ class Cycle(_Entity, _Labeled):
 
     !!! example "Example for February cycle"
 
-        ![cycles](../pic/cycles_colored.svg){ align=left width="250" }
+        ![cycles](../img/cycles_colored.svg){ align=left width="250" }
         Now the user starts working on the February work cycle. He or she creates two
         scenarios for the February cycle (one with a low capacity assumption and one with
         a high capacity assumption). The user can then decide to elect the low capacity

taipy/core/data/aws_s3.py

@@ -44,7 +44,7 @@ class S3ObjectDataNode(DataNode):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/csv.py

@@ -44,7 +44,7 @@ class CSVDataNode(DataNode, _FileDataNodeMixin, _TabularDataNodeMixin):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/data_node.py

@@ -122,7 +122,7 @@ class DataNode(_Entity, _Labeled):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task orchestration](../../userman/sdm/task/index.md#task-configuration) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if the data node is locked for modification. False
             otherwise.

taipy/core/data/excel.py

@@ -48,7 +48,7 @@ class ExcelDataNode(DataNode, _FileDataNodeMixin, _TabularDataNodeMixin):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/generic.py

@@ -40,7 +40,7 @@ class GenericDataNode(DataNode):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/in_memory.py

@@ -44,7 +44,7 @@ class InMemoryDataNode(DataNode):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/json.py

@@ -42,7 +42,7 @@ class JSONDataNode(DataNode, _FileDataNodeMixin):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/mongo.py

@@ -46,7 +46,7 @@ class MongoCollectionDataNode(DataNode):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/parquet.py

@@ -45,7 +45,7 @@ class ParquetDataNode(DataNode, _FileDataNodeMixin, _TabularDataNodeMixin):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/pickle.py

@@ -40,7 +40,7 @@ class PickleDataNode(DataNode, _FileDataNodeMixin):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/sql.py

@@ -40,7 +40,7 @@ class SQLDataNode(_AbstractSQLDataNode):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/data/sql_table.py

@@ -41,7 +41,7 @@ class SQLTableDataNode(_AbstractSQLDataNode):
         validity_period (Optional[timedelta]): The duration implemented as a timedelta since the last edit date for
             which the data node can be considered up-to-date. Once the validity period has passed, the data node is
             considered stale and relevant tasks will run even if they are skippable (see the
-            [Task management page](../core/entities/task-mgt.md) for more details).
+            [Task management](../../userman/sdm/task/index.md) page for more details).
             If _validity_period_ is set to `None`, the data node is always up-to-date.
         edit_in_progress (bool): True if a task computing the data node has been submitted
             and not completed yet. False otherwise.

taipy/core/reason/reason.py

@@ -88,7 +88,7 @@ class EntityIsNotSubmittableEntity(Reason):
     An entity is not a submittable entity, which prevents specific actions from being performed.
 
     Attributes:
-        entity_id (str): The identifier of the `Entity^`.
+        entity_id (str): The entity identifier.
     """
 
     def __init__(self, entity_id: str):

taipy/core/sequence/sequence.py

@@ -54,7 +54,7 @@ class Sequence(_Entity, Submittable, _Labeled):
         the forecasts, planning its production. Three task are configured and linked
         together through data nodes.
 
-        ![sequences](../refmans/img/sequences.svg){ align=left }
+        ![sequences](../img/sequences.svg){ align=left }
 
         First, the sales sequence (boxed in green in the picture) contains **training**
         and **predict** tasks. Second, a production sequence (boxed in dark gray in the

taipy/gui/__init__.py

@@ -46,8 +46,8 @@ application.
     add functionality to Taipy GUI:
 
     - [`python-magic`](https://pypi.org/project/python-magic/): identifies image format
-      from byte buffers so the [`image`](../../gui/viselements/image.md) control can
-      display them, and so that [`file_download`](../../gui/viselements/file_download.md)
+      from byte buffers so the [`image`](../../../userman/gui/viselements/standard-and-blocks/image.md) control can
+      display them, and so that [`file_download`](../../../userman/gui/viselements/standard-and-blocks/file_download.md)
       can request the browser to display the image content when relevant.<br/>
       You can install that package with the regular `pip install python-magic` command
       (then potentially `pip install python-magic` on Windows),

taipy/gui/_gui_section.py

@@ -53,7 +53,7 @@ class _GuiSection(UniqueSection):
         Parameters:
             **properties (dict[str, any]): Keyword arguments that configure the behavior of the `Gui^` instances.<br/>
                 Please refer to the
-                [Configuration section](../gui/configuration.md#configuring-the-gui-instance)
+                [Configuration section](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
                 of the User Manual for more information on the accepted arguments.
         Returns:
             The GUI configuration.

taipy/gui/_renderers/__init__.py

@@ -139,7 +139,7 @@ class Markdown(_Renderer):
     user interfaces.
 
     You can find details on the Taipy Markdown-specific syntax and how to add
-    Taipy Visual Elements in the [section on Markdown](../gui/pages/markdown.md)
+    Taipy Visual Elements in the [section on Markdown](../../userman/gui/pages/markdown.md)
     of the User Manual.
     """
 
@@ -167,7 +167,7 @@ class Html(_Renderer):
     user interfaces.
 
     You can find details on HTML-specific constructs and how to add
-    Taipy Visual Elements in the [section on HTML](../gui/pages/html.md)
+    Taipy Visual Elements in the [section on HTML](../../userman/gui/pages/html.md)
     of the User Manual.
     """
 

taipy/gui/gui.py

@@ -288,8 +288,8 @@ class Gui:
                 of the main Python file is allowed.
             env_filename (Optional[str]): An optional file from which to load application
                 configuration variables (see the
-                [Configuration](../gui/configuration.md#configuring-the-gui-instance) section
-                of the User Manual for details.)<br/>
+                [Configuration](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
+                section of the User Manual for details.)<br/>
                 The default value is "taipy.gui.env"
             libraries (Optional[List[ElementLibrary]]): An optional list of extension library
                 instances that pages can reference.<br/>
@@ -1505,7 +1505,7 @@ class Gui:
         """Invoke a user callback for a given state.
 
         See the
-        [section on Long Running Callbacks in a Thread](../gui/callbacks.md#long-running-callbacks-in-a-thread)
+        [section on Long Running Callbacks in a Thread](../../userman/gui/callbacks.md#long-running-callbacks-in-a-thread)
         in the User Manual for details on when and how this function can be used.
 
         Arguments:
@@ -2012,7 +2012,7 @@ class Gui:
     ) -> Partial:
         """Create a new `Partial^`.
 
-        The [User Manual section on Partials](../gui/pages/index.md#partials) gives details on
+        The [User Manual section on Partials](../../userman/gui/pages/index.md#partials) gives details on
         when and how to use this class.
 
         Arguments:
@@ -2581,7 +2581,7 @@ class Gui:
         URL that `Gui` serves. The default is to listen to the *localhost* address
         (127.0.0.1) on the port number 5000. However, the configuration of this `Gui`
         object may impact that (see the
-        [Configuration](../gui/configuration.md#configuring-the-gui-instance)
+        [Configuration](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
         section of the User Manual for details).
 
         Arguments:
@@ -2607,7 +2607,7 @@ class Gui:
                 Also note that setting the *debug* argument to True forces *async_mode* to "threading".
             **kwargs (dict[str, any]): Additional keyword arguments that configure how this `Gui` is run.
                 Please refer to the
-                [Configuration section](../gui/configuration.md#configuring-the-gui-instance)
+                [Configuration section](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
                 of the User Manual for more information.
 
         Returns:

taipy/gui/gui_actions.py

@@ -34,7 +34,7 @@ def download(
         - a string: the value must be an existing path name to the file that gets downloaded or
           the URL to the resource you want to download.
         - a buffer (such as a `bytes` object): if the size of the buffer is smaller than
-           the [*data_url_max_size*](../gui/configuration.md#p-data_url_max_size) configuration
+           the [*data_url_max_size*](../../userman/configuration/gui-config.md#p-data_url_max_size) configuration
            setting, then the [`python-magic`](https://pypi.org/project/python-magic/) package is
            used to determine the [MIME type](https://en.wikipedia.org/wiki/Media_type) of the
            buffer content, and the download is performed using a generated "data:" URL with
@@ -205,7 +205,7 @@ def get_state_id(state: State) -> t.Optional[str]:
     The state identifier is a string generated by Taipy GUI for a given `State^` that is used
     to serialize callbacks.
     See the
-    [User Manual section on Long Running Callbacks](../gui/callbacks.md#long-running-callbacks)
+    [User Manual section on Long Running Callbacks](../../userman/gui/callbacks.md#long-running-callbacks)
     for details on when and how this function can be used.
 
     Arguments:
@@ -334,7 +334,7 @@ def invoke_long_callback(
     *user_function* is finished (successfully or not), or periodically (using the *period* parameter).
 
     See the
-    [User Manual section on Long Running Callbacks](../gui/callbacks.md#long-running-callbacks)
+    [User Manual section on Long Running Callbacks](../../userman/gui/callbacks.md#long-running-callbacks)
     for details on when and how this function can be used.
 
     Arguments:

taipy/gui/icon.py

@@ -15,8 +15,8 @@ import typing as t
 class Icon:
     """Small image in the User Interface.
 
-    Icons are typically used in controls like [button](../gui/viselements/button.md)
-    or items in a [menu](../gui/viselements/menu.md).
+    Icons are typically used in controls like [button](../../userman/gui/viselements/standard-and-blocks/button.md)
+    or items in a [menu](../../userman/gui/viselements/standard-and-blocks/menu.md).
 
     Attributes:
         path (str): The path to the image file.

taipy/gui/partial.py

@@ -28,9 +28,9 @@ class Partial(_Page):
     and not related pages. This allows not to have to repeat yourself when
     creating your page templates.
 
-    Visual elements such as [`part`](../gui/viselements/part.md),
-    [`dialog`](../gui/viselements/dialog.md) or
-    [`pane`](../gui/viselements/pane.md) can use Partials.
+    Visual elements such as [`part`](../../userman/gui/viselements/standard-and-blocks/part.md),
+    [`dialog`](../..//userman/gui/viselements/standard-and-blocks/dialog.md) or
+    [`pane`](../../userman/gui/viselements/standard-and-blocks/pane.md) can use Partials.
 
     Note that `Partial` has no constructor (no `__init__()` method): to create a
     `Partial`, you must call the `Gui.add_partial()^` function.

taipy/gui/state.py

@@ -29,14 +29,14 @@ class State:
     """Accessor to the bound variables from callbacks.
 
     `State` is used when you need to access the value of variables
-    bound to visual elements (see [Binding](../gui/binding.md)).<br/>
+    bound to visual elements (see [Binding](../../userman/gui/binding.md)).<br/>
     Because each browser connected to the application server may represent and
     modify any variable at any moment as the result of user interaction, each
     connection holds its own set of variables along with their values. We call
     the set of these the application variables the application _state_, as seen
     by a given client.
 
-    Each callback (see [Callbacks](../gui/callbacks.md)) receives a specific
+    Each callback (see [Callbacks](../../userman/gui/callbacks.md)) receives a specific
     instance of the `State` class, where you can find all the variables bound to
     visual elements in your application.
 

taipy/rest/__init__.py

@@ -11,8 +11,9 @@
 
 """# Taipy Rest
 
-The Taipy Rest package exposes the Runnable `Rest^` service to provide REST APIs on top of Taipy Core. (more details
-on Taipy Core functionalities in the [user manual](../../../manuals/core/index.md)).
+The Taipy Rest package exposes the Runnable `Rest^` service to expose REST APIs on top of Taipy Core
+functionalities, in particular the scenario and data management. (more details
+on the [user manual](../../../userman/sdm/index.md)).
 
 Once the `Rest^` service runs, users can call REST APIs to create, read, update, submit and remove Taipy entities
 (including cycles, scenarios, sequences, tasks, jobs, and data nodes). It is handy when it comes to integrating a

taipy/templates/default/{{cookiecutter.__root_folder_name}}/pages/page_example/page_example.py

@@ -13,7 +13,7 @@
 A page of the application.
 Page content is imported from the page_example.md file.
 
-Please refer to https://docs.taipy.io/en/latest/manuals/gui/pages for more details.
+Please refer to https://docs.taipy.io/en/latest/manuals/userman/gui/pages for more details.
 """
 
 from taipy.gui import Markdown

taipy/templates/default/{{cookiecutter.__root_folder_name}}/pages/root.py

@@ -13,7 +13,7 @@
 The root page of the application.
 Page content is imported from the root.md file.
 
-Please refer to https://docs.taipy.io/en/latest/manuals/gui/pages for more details.
+Please refer to https://docs.taipy.io/en/latest/manuals/userman/gui/pages for more details.
 """
 
 from taipy.gui import Markdown

tools/gui/generate_pyi.py

@@ -59,7 +59,7 @@ with open("./taipy/gui/version.json", "r") as vfile:
         current_version = "develop"
     else:
         current_version = f'release-{version.get("major", 0)}.{version.get("minor", 0)}'
-taipy_doc_url = f"https://docs.taipy.io/en/{current_version}/manuals/gui/viselements/"
+taipy_doc_url = f"https://docs.taipy.io/en/{current_version}/manuals/userman/gui/viselements/standard-and-blocks/"
 
 
 # ############################################################