Doc/#1007 improve doc navigability (#1743)

* Fix links for new doc

* Fix links

* Fix links

* Fix link

* Fix link

* Apply suggestions from code review

Max line length

* Update config.pyi

* Fix links to refman guiext

* Fix viselements for unknown crossref

* Fix linter issues

* Update config.pyi

* chore: increase node space size on actions

---------

Co-authored-by: Jean-Robin <jeanrobin.medori@avaiga.com>
Co-authored-by: jrobinAV <jrobinAV@users.noreply.github.com>
Co-authored-by: Joao Andre <joao.dasilva@avaiga.com>

.github/workflows/packaging.yml

@@ -12,6 +12,9 @@ on:
         required: false
         default: ""
 
+env:
+  NODE_OPTIONS: --max-old-space-size=4096
+
 jobs:
   standard-packages:
     timeout-minutes: 30

.github/workflows/partial-tests.yml

@@ -3,6 +3,9 @@ name: Partial Tests Workflow
 on:
   workflow_call:
 
+env:
+  NODE_OPTIONS: --max-old-space-size=4096
+
 jobs:
   linter:
     runs-on: ubuntu-latest

frontend/taipy-gui/extension-index.md

@@ -49,7 +49,7 @@ has the name that the Python script has created it with, the equivalent to this
 on the front-end might have a different name, for technical reasons.
 
 Note that controls that hold dynamic properties have two generated properties called
-*updateVars* and *updateVarName*, that are used to ensure a proper update of variable changes. The function [getUpdateVar()](modules/#getupdatevar) uses that property.
+*updateVars* and *updateVarName*, that are used to ensure a proper update of variable changes. The function [getUpdateVar()](functions/getUpdateVar.md) uses that property.
 
 Components dynamic properties are tied to the State: all updates of the State will
 automatically be propagated to the relevant components and the component is in charge

taipy/config/config.pyi

@@ -267,7 +267,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -318,7 +320,9 @@ class Config:
                 `(Config.)set_default_data_node_configuration()^`).
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -351,7 +355,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -383,7 +389,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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:
@@ -426,7 +434,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -460,7 +470,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -495,7 +507,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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:
@@ -523,7 +537,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -554,7 +570,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -611,7 +629,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -674,7 +694,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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:
@@ -722,7 +744,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -759,7 +783,9 @@ class Config:
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -881,7 +907,8 @@ class Config:
             mode (Optional[str]): Indicates the mode of the version management system.
                 Possible values are *"development"* or *"experiment"*. On Enterprise edition of Taipy,
                 *production* mode is also available. Please refer to the
-                [Versioning management](../../userman/versioning/index.md) documentation page for more details.
+                [Versioning management](../../userman/advanced_features/versioning/index.md)
+                documentation page for more details.
             version_number (Optional[str]): The string identifier of the version.
                  In development mode, the version number is ignored.
             force (Optional[bool]): If True, Taipy will override a version even if the configuration

taipy/core/__init__.py

@@ -20,9 +20,9 @@ To build a Taipy Core application, the first step consists of setting up the Tai
 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](../../../userman/data-integration/data-node-config.md),
-[tasks](../../../userman/task-orchestration/scenario-config.md),
-and [scenarios](../../../userman/sdm/scenario/scenario-config.md).
+[data nodes](../../../userman/scenario_features/data-integration/data-node-config.md),
+[tasks](../../../userman/scenario_features/task-orchestration/scenario-config.md),
+and [scenarios](../../../userman/scenario_features/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 [Function](#functions). In particular, the most used functions are `tp.create_scenario()`,
@@ -35,7 +35,8 @@ in the following section on [Function](#functions). In particular, the most used
     executor for their execution.
 
     In particular, this `Orchestrator^` service is automatically run when 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.
+    See the [running services](../../../userman/run-deploy/run/running_services.md) page of the user
+    manual for more details.
 """
 
 from ._init import *

taipy/core/config/core_section.py

@@ -47,10 +47,11 @@ class CoreSection(UniqueSection):
         read_entity_retry (int): Number of retries to read an entity from the repository before return failure.
             The default value is 3.
         mode (str): The Taipy operating mode. By default, the `Orchestrator^` service runs in "development" mode.
-            Please refer to the [Versioning management](../../userman/versioning/index.md)
+            Please refer to the [Versioning management](../../userman/advanced_features/versioning/index.md)
             documentation page for more details.
         version_number (str)): The identifier of the user application version. Please refer to the
-            [Versioning management](../../userman/versioning/index.md) documentation page for more details.
+            [Versioning management](../../userman/advanced_features/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.
@@ -374,7 +375,8 @@ class CoreSection(UniqueSection):
             mode (Optional[str]): Indicates the mode of the version management system.
                 Possible values are *"development"* or *"experiment"*. On Enterprise edition of Taipy,
                 *production* mode is also available. Please refer to the
-                [Versioning management](../../userman/versioning/index.md) documentation page for more details.
+                [Versioning management](../../userman/advanced_features/versioning/index.md)
+                documentation page for more details.
             version_number (Optional[str]): The string identifier of the version.
                  In development mode, the version number is ignored.
             force (Optional[bool]): If True, Taipy will override a version even if the configuration

taipy/core/config/data_node_config.py

@@ -411,7 +411,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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 +472,9 @@ class DataNodeConfig(Section):
                 `(Config.)set_default_data_node_configuration()^`).
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -521,7 +525,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -563,7 +569,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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:
@@ -616,7 +624,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -664,7 +674,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -709,7 +721,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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:
@@ -747,7 +761,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -782,7 +798,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -845,7 +863,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -936,7 +956,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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:
@@ -1015,7 +1037,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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.
 
@@ -1077,7 +1101,9 @@ class DataNodeConfig(Section):
                 The default value is `Scope.SCENARIO`.
             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](../../userman/task-orchestration/scenario-config.md#from-task-configurations) for more details).
+                relevant tasks will run even if they are skippable (see the Task configuration
+                [page](../../userman/scenario_features/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/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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

@@ -123,7 +123,8 @@ 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 orchestration](../../userman/sdm/task/index.md#task-configuration) page for more details).
+            [Task orchestration](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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](../../userman/sdm/task/index.md) page for more details).
+            [Task management](../../userman/scenario_features/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/gui/__init__.py

@@ -48,8 +48,8 @@ application.
     add functionality to Taipy GUI:
 
     - [`python-magic`](https://pypi.org/project/python-magic/): identifies image format
-      from byte buffers so the [`image`](../../../userman/gui/viselements/generic/image.md) control can
-      display them, and so that [`file_download`](../../../userman/gui/viselements/generic/file_download.md)
+      from byte buffers so the [`image`](../../../refmans/gui/viselements/generic/image.md) control can
+      display them, and so that [`file_download`](../../../refmans/gui/viselements/generic/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

@@ -52,8 +52,8 @@ 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](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
+                Please refer to the gui config section
+                [page](../../userman/advanced_features/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/gui.py

@@ -289,7 +289,7 @@ 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](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
+                [Configuration](../../userman/advanced_features/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
@@ -2045,7 +2045,7 @@ class Gui:
     ) -> Partial:
         """Create a new `Partial^`.
 
-        The [User Manual section on Partials](../../userman/gui/pages/index.md#partials) gives details on
+        The [User Manual section on Partials](../../userman/gui/pages/partial/index.md) gives details on
         when and how to use this class.
 
         Arguments:
@@ -2620,7 +2620,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](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
+        [Configuration](../../userman/advanced_features/configuration/gui-config.md#configuring-the-gui-instance)
         section of the User Manual for details).
 
         Arguments:
@@ -2645,8 +2645,8 @@ class Gui:
                 ignored.<br/>
                 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](../../userman/configuration/gui-config.md#configuring-the-gui-instance)
+                Please refer to the gui config section
+                [page](../../userman/advanced_features/configuration/gui-config.md#configuring-the-gui-instance)
                 of the User Manual for more information.
 
         Returns:

taipy/gui/gui_actions.py

@@ -33,27 +33,27 @@ def download(
     - *content*: this parameter can hold several values depending on your use case:
         - 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*](../../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
-           the relevant type, and a base64-encoded version of the buffer content.<br/>
-           If the buffer is too large, its content is transferred after saving it in a temporary
-           server file.
-      - *on_action*: this callback is triggered when the transfer of the content is achieved.</br>
-           In this function, you can perform any clean-up operation that could be required after
-           the download is completed.<br/>
-           This callback can use three optional parameters:
-           - *state*: the `State^` instance of the caller.
-           - *id* (optional): a string representing the identifier of the caller. If this function
-             is called directly, this will always be "Gui.download". Some controls may also trigger
-             download actions, and then *id* would reflect the identifier of those controls.
-           - *payload* (optional): an optional payload from the caller.<br/>
-             This is a dictionary with the following keys:
-              - *action*: the name of the callback;
-              - *args*: an array of two strings. The first element reflects the *name* parameter,
-                and the second element reflects the server-side URL where the file is located.
+        - a buffer (such as a `bytes` object): if the size of the buffer is smaller than the
+          [*data_url_max_size*](../../userman/advanced_features/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
+          the relevant type, and a base64-encoded version of the buffer content.<br/>
+          If the buffer is too large, its content is transferred after saving it in a temporary
+          server file.
+        - *on_action*: this callback is triggered when the transfer of the content is achieved.</br>
+          In this function, you can perform any clean-up operation that could be required after
+          the download is completed.<br/>
+          This callback can use three optional parameters:
+            - *state*: the `State^` instance of the caller.
+            - *id* (optional): a string representing the identifier of the caller. If this function
+              is called directly, this will always be "Gui.download". Some controls may also trigger
+              download actions, and then *id* would reflect the identifier of those controls.
+            - *payload* (optional): an optional payload from the caller.<br/>
+              This is a dictionary with the following keys:
+                - *action*: the name of the callback;
+                - *args*: an array of two strings. The first element reflects the *name* parameter,
+                  and the second element reflects the server-side URL where the file is located.
     """
     if state and isinstance(state._gui, Gui):
         state._gui._download(content, name, on_action)

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](../../userman/gui/viselements/generic/button.md)
-    or items in a [menu](../../userman/gui/viselements/generic/menu.md).
+    Icons are typically used in controls like [button](../../refmans/gui/viselements/generic/button.md)
+    or items in a [menu](../../refmans/gui/viselements/generic/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`](../../userman/gui/viselements/generic/part.md),
-    [`dialog`](../..//userman/gui/viselements/generic/dialog.md) or
-    [`pane`](../../userman/gui/viselements/generic/pane.md) can use Partials.
+    Visual elements such as [`part`](../../refmans/gui/viselements/generic/part.md),
+    [`dialog`](../../refmans/gui/viselements/generic/dialog.md) or
+    [`pane`](../../refmans/gui/viselements/generic/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/viselements.json

@@ -1504,7 +1504,7 @@
                         "name": "lov",
                         "default_property": true,
                         "type": "dict[str, any]",
-                        "doc": "The list of pages. The keys should be:\n<ul>\n<li>page id (start with \"/\")</li>\n<li>or full URL</li>\n</ul>\nThe values are labels. See the <a href=\"../../binding/#list-of-values\">section on List of Values</a> for details."
+                        "doc": "The list of pages. The keys should be:\n<ul>\n<li>page id (start with \"/\")</li>\n<li>or full URL</li>\n</ul>\nThe values are labels. See the <a href=\"../../../../userman/gui/binding/#list-of-values\">section on List of Values</a> for details."
                     }
                 ]
             }
@@ -1590,7 +1590,7 @@
                     {
                         "name": "users",
                         "type": "dynamic(list[Union[str,Icon]])",
-                        "doc": "The list of users. See the <a href=\"../../binding/#list-of-values\">section on List of Values</a> for details."
+                        "doc": "The list of users. See the <a href=\"../../../../userman/gui/binding/#list-of-values\">section on List of Values</a> for details."
                     },
                     {
                         "name": "sender_id",
@@ -1918,7 +1918,7 @@
                     {
                         "name": "lov",
                         "type": "dict[str, any]",
-                        "doc": "The list of values. See the <a href=\"../../binding/#list-of-values\">section on List of Values</a> for details."
+                        "doc": "The list of values. See the <a href=\"../../../../userman/gui/binding/#list-of-values\">section on List of Values</a> for details."
                     },
                     {
                         "name": "adapter",

taipy/gui_core/viselements.json

@@ -549,7 +549,7 @@
                     {
                         "name": "on_details",
                         "type": "Union[Callback, bool]",
-                        "doc": "The name of a function that is triggered when the details icon is pressed.<br/>The parameters of that function are all optional:\n<ul>\n<li>state (<code>State^</code>): the state instance.</li>\n<li>id (str): the id of the control.</li>\n<li>payload (<code>dict^</code>): a dictionary that contains the Job Id in the value for key <i>args<i>.</li>\n</ul></br>If False, the icon is not shown.",
+                        "doc": "The name of a function that is triggered when the details icon is pressed.<br/>The parameters of that function are all optional:\n<ul>\n<li>state (<code>State^</code>): the state instance.</li>\n<li>id (str): the id of the control.</li>\n<li>payload (<code>dict</code>): a dictionary that contains the Job Id in the value for key <i>args<i>.</li>\n</ul></br>If False, the icon is not shown.",
                         "signature": [
                             [
                                 "state",

taipy/rest/__init__.py

@@ -13,7 +13,7 @@
 
 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)).
+on the [user manual](../../../userman/scenario_features/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