Doc/#1007 improve navigability

.gitignore

@@ -111,21 +111,22 @@ site/
 mkdocs.yml
 /taipy
 /taipy-fe
-/docs/manuals/userman/gui/viselements/index.md
-docs/manuals/userman/gui/viselements/generic/*.md
-!docs/manuals/userman/gui/viselements/generic/index.md
-docs/manuals/userman/gui/viselements/generic/charts/*.md
-docs/manuals/userman/gui/viselements/corelements/*.md
-!docs/manuals/userman/gui/gui_example.ipynb
-docs/manuals/xrefs
-docs/manuals/refmans/reference/**/*.md
-!docs/manuals/refmans/reference/index.md
-docs/manuals/refmans/reference_rest/*.md
-!docs/manuals/refmans/reference_rest/index.md
-docs/manuals/refmans/reference_guiext/
+/docs/refmans/gui/viselements/index.md
+docs/refmans/gui/viselements/generic/*.md
+!docs/refmans/gui/viselements/generic/index.md
+docs/refmans/gui/viselements/generic/charts/*.md
+docs/refmans/gui/viselements/corelements/*.md
+!docs/userman/gui/gui_example.ipynb
+docs/userman/xrefs
+docs/refmans/reference/**/*.md
+!docs/refmans/reference/index.md
+docs/refmans/reference_rest/*.md
+!docs/refmans/reference_rest/index.md
+docs/refmans/reference_guiext/
 docs/contributing/contributors.md
 fe_node_modules/
 docs/tutorials/index.md
+docs/tutorials/getting_started/index.md
 docs/tutorials/scenario_management/index.md
 docs/tutorials/visuals/index.md
 docs/tutorials/integration/index.md

CONTRIBUTING.md

@@ -164,7 +164,7 @@ Create a folder to organize your application description. Use a clear and concis
 for the folder that represents the content. For example:
 
 ```
-docs/gallery/{category}/your_folder/
+docs/gallery/articles/your_folder/
 ```
 
 Category is the category of the article (finance, decision_support, llm,
@@ -184,6 +184,7 @@ integration or large data)
 - type: The type of the item (code, video or article)
 - data-keywords: A comma separated list of keywords
 - short-description: A short description of the item
+- order: The order of the item in the gallery
 - img: The path to the image associated with the item
 
 This header will be used to display the article in the correct pages.
@@ -196,6 +197,7 @@ title: Realtime Pollution Dashboard
 category: visualization
 data-keywords: dashboad
 short-description: Streams real-time pollution data from sensors and shows air quality on a map.
+order: 26
 img: pollution_sensors/images/pollution_dashboard.png
 ---
 
@@ -223,7 +225,7 @@ You shall then describe your application in more details.
 Add the new Markdown file to the "mkdocs.yml_template" file in the appropriate section.
 
 ```
-"Title of the Application": gallery/{category}/your_folder/index.md
+"Title of the Application": gallery/articles/your_folder/index.md
 ```
 
 #### Checklist:
@@ -233,8 +235,8 @@ Add the new Markdown file to the "mkdocs.yml_template" file in the appropriate s
 if any are present.
 - Break lines in the Markdown file before 100 characters.
 - Use relative links to taipy doc (.md). To express
-`https://docs.taipy.io/en/latest/manuals/studio/config/` in a tip article, write
-`../../../manuals/studio/config/index.md`.
+`https://docs.taipy.io/en/latest/userman/ecosystem/studio/config/` in a tip article, write
+`../../../userman/ecosystem/studio/config/index.md`.
 - Follow conventions for styling code, variables, etc.
 - Check the level of titles in the Markdown file.
 - Build the doc and test the page. See [INSTALLATION.md](INSTALLATION.md)
@@ -254,7 +256,7 @@ Create a folder to organize your tutorial. Use a clear and concise name for the
 folder that represents the content. For example:
 
 ```
-docs/tutorials/{category}/your_folder/
+docs/tutorials/articles/your_folder/
 ```
 
 Category is the category of the article (fundamentals, visuals, scenario
@@ -273,6 +275,7 @@ The header contains the following information:
 integration or large data)
 - data-keywords: A comma separated list of keywords
 - short-description: A short description of the item
+- order: The order of the item in the tutorials
 - img: The path to the image associated with the item
 
 This header will be used to display the article in the correct pages.
@@ -285,7 +288,8 @@ title: Scenarios
 category: scenario_management
 data-keywords: scenario cycle configuration datanode dag
 short-description: A Taipy scenario models an instance of your end-user business problem to solve on data and parameter sets.
-img: 1_scenarios/images/scenario.png
+order: 26
+img: scenarios/images/scenario.png
 ---
 
 And here is the content of my article...
@@ -296,7 +300,7 @@ And here is the content of my article...
 Add the new Markdown file to the "mkdocs.yml_template" file in the appropriate section.
 
 ```
-"Title of the Article": tutorials/{category}/your_folder/index.md
+"Title of the Article": tutorials/articles/your_folder/index.md
 ```
 
 #### Checklist:
@@ -306,8 +310,8 @@ Add the new Markdown file to the "mkdocs.yml_template" file in the appropriate s
 if any are present.
 - Break lines in the Markdown file before 100 characters.
 - Use relative links to taipy doc (.md). To express
-`https://docs.taipy.io/en/latest/manuals/studio/config/` in a tip article, write
-`../../../manuals/studio/config/index.md`.
+`https://docs.taipy.io/en/latest/userman/ecosystem/studio/config/` in a tip article, write
+`../../../userman/ecosystem/studio/config/index.md`.
 - Follow conventions for styling code, variables, etc.
 - Check the level of titles in the Markdown file.
 - Build the doc and test the page. See [INSTALLATION.md](INSTALLATION.md)

docs/index.md

@@ -52,19 +52,19 @@ from initial prototypes to production-ready applications.
 
 <ul class="tp-pills-list">
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/chart/">
+    <a class="tp-pill" href="refmans/gui/viselements/generic/chart/">
       <span>Chart</span>
       <div class="tp-tooltip">
-        <img src="manuals/userman/gui/viselements/generic/chart-d.png"/>
+        <img src="refmans/gui/viselements/generic/chart-d.png"/>
         <p>A chart visually depicts data through graphs, charts, or plots.</p>
       </div>
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/table/">
+    <a class="tp-pill" href="refmans/gui/viselements/generic/table/">
       <span>Table</span>
       <div class="tp-tooltip">
-        <img src="manuals/userman/gui/viselements/generic/table-d.png"/>
+        <img src="refmans/gui/viselements/generic/table-d.png"/>
         <p>
           A table presents data in rows and columns, often used in web applications for structured
           data display and interaction.
@@ -73,34 +73,34 @@ from initial prototypes to production-ready applications.
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/button/">
+    <a class="tp-pill" href="refmans/gui/viselements/generic/button/">
       <span>Button</span>
       <div class="tp-tooltip">
-        <img src="manuals/userman/gui/viselements/generic/button-d.png" alt="">
+        <img src="refmans/gui/viselements/generic/button-d.png" alt="">
         <p>You can employ this class name to target the buttons on your page and apply styling.</p>
       </div>
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/input/">
+    <a class="tp-pill" href="refmans/gui/viselements/generic/input/">
       <span>Input</span>
       <div class="tp-tooltip">
-        <img src="manuals/userman/gui/viselements/generic/input-d.png"/>
+        <img src="refmans/gui/viselements/generic/input-d.png"/>
         <p>A control that displays some text that can potentially be edited.</p>
       </div>
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/slider/">
+    <a class="tp-pill" href="refmans/gui/viselements/generic/slider/">
       <span>Slider</span>
       <div class="tp-tooltip">
-        <img src="manuals/userman/gui/viselements/generic/slider-d.png"/>
+        <img src="refmans/gui/viselements/generic/slider-d.png"/>
         <p>Displays and allows the user to set a value within a range.</p>
       </div>
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/controls/">
+    <a class="tp-pill" href="refmans/gui/viselements/">
       <span>…</span>
       <div class="tp-tooltip">
         <p>Browse the complete list of visual elements.</p>
@@ -113,34 +113,42 @@ from initial prototypes to production-ready applications.
 
 <ul class="tp-pills-list">
   <li>
-    <a class="tp-pill" href="manuals/userman/gui/viselements/generic/blocks/">
+    <a class="tp-pill" href="refmans/gui/viselements/#block-elements">
       <span>Structure Pages</span>
     </a>
   </li>
-    <li>
-      <div class="tp-pill">
-        <a href="manuals/userman/sdm/scenario/#scenario-configuration">Configure</a>,
-        <a href="manuals/userman/sdm/scenario/#scenario-creation">instantiate</a> and
-        <a href="manuals/userman/sdm/scenario/#scenario-submission">submit</a> Scenario
-      </div>
-    </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/versioning/">
-      <span>Manage versions</span>
+    <a class="tp-pill" href="userman/scenario_features/data-integration/">
+      <span>Data integration</span>
+    </a>
+  </li>
+  <li>
+    <a class="tp-pill" href="userman/scenario_features/task-orchestration/">
+      <span>Task orchestration</span>
+    </a>
+  </li>
+  <li>
+    <a class="tp-pill" href="userman/scenario_features/what-if-analysis/">
+      <span>What if analysis</span>
+    </a>
+  </li>
+  <li>
+    <a class="tp-pill" href="userman/advanced_features/versioning/">
+      <span>Version management</span>
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/cli/">
+    <a class="tp-pill" href="userman/ecosystem/cli/">
       <span>Taipy command-line interface (CLI)</span>
     </a>
   </li>
   <li>
-    <a class="tp-pill" href="manuals/userman/rest/">
+    <a class="tp-pill" href="userman/scenario_features/rest/">
       <span>Expose Taipy's REST APIs</span>
     </a>
   </li>
     <li>
-    <a class="tp-pill" href="manuals/userman/">
+    <a class="tp-pill" href="userman/">
       <span>…</span>
       <div class="tp-tooltip">
         <p>Browse the complete list of features.</p>

docs/manuals/userman/gui/viselements/corelements/scenario_dag.md_template → docs/refmans/gui/viselements/corelements/scenario_dag.md_template

@@ -13,7 +13,7 @@ Here is what the control looks like when connected to a scenario instance:
 </figure>
 
 The visual representation of the Data Nodes and Tasks is the same as the one used in the
-[Taipy Studio extension](../../../../studio/config/graphview.md).
+[Taipy Studio extension](../../../../userman/ecosystem/studio/config/graphview.md).
 
 The toolbar, which can be removed by setting the [*show_toolbar*](#p-show_toolbar) property to
 False, contains a button that adapts the rendering area zoom factor to the graph representation.

docs/manuals/userman/gui/viselements/generic/button.md_template → docs/refmans/gui/viselements/generic/button.md_template

@@ -5,9 +5,9 @@ A control that can trigger a function when pressed.
 All the button controls are generated with the "taipy-button" CSS class. You can use this class
 name to select the buttons on your page and apply style.
 
-## [Stylekit](../../styling/stylekit.md) support
+## [Stylekit](../../../../userman/gui/styling/stylekit.md) support
 
-The [Stylekit](../../styling/stylekit.md) provides specific classes that you can use to style buttons:
+The [Stylekit](../../../../userman/gui/styling/stylekit.md) provides specific classes that you can use to style buttons:
 
 * *secondary*<br/>*error*<br/>*warning*<br/>*success*<br/>
     Buttons are normally displayed using the value of the *color_primary* Stylekit variable.

docs/manuals/userman/gui/viselements/generic/chart.md_template → docs/refmans/gui/viselements/generic/chart.md_template

@@ -284,9 +284,9 @@ button, the page will reflect the change without explicit refresh:
 All the chart controls are generated with the "taipy-chart" CSS class. You can use this class
 name to select the charts on your page and apply style.
 
-## [Stylekit](../../styling/stylekit.md) support
+## [Stylekit](../../../../userman/gui/styling/stylekit.md) support
 
-The [Stylekit](../../styling/stylekit.md) provides a specific class that you can use to style charts:
+The [Stylekit](../../../../userman/gui/styling/stylekit.md) provides a specific class that you can use to style charts:
 
 * *has-background*<br/>
     When the chart control uses the *has-background* class, the rendering of the chart

docs/manuals/userman/gui/viselements/generic/charts/advanced.md_template → docs/refmans/gui/viselements/generic/charts/advanced.md_template

@@ -270,7 +270,7 @@ def on_change(state, var, val):
 ```
 
 The part you should be looking at is the use of the default callback property
-[*on_change*](../../../callbacks.md#variable-value-change): it detects the changes in
+[*on_change*](../../../../../userman/gui/callbacks.md#variable-value-change): it detects the changes in
 *selected_indices* and calculates the mean, which updates the text in the title.
 
 We also create two objects (*layout* and *config*) used to remove the mode