update

Author: oblomov-dev

docs/.vitepress/config.mjs

@@ -105,17 +105,19 @@ export default defineConfig({
         text: 'Configuration',
         link: '/configuration/configuration',
         collapsed: true,
-        items: [
-          { text: 'Installation', link: '/configuration/installation'},
-          { text: 'Setup', link: '/configuration/setup' },
+        items: [      
+          { text: 'Settings', link: '/configuration/setup' },
           { text: 'Security', link: '/configuration/security' },
           { text: 'Authorization', link: '/configuration/authorization' },
           { text: 'Performance', link: '/configuration/performance' },
           { text: 'UI5 Versions', link: '/configuration/ui5_versions' },
-          { text: 'S/4 Public Cloud', link: '/configuration/s4_public_cloud' },
-          { text: 'Fiori Launchpad', link: '/configuration/launchpad', },
-          { text: 'BTP Workzone', link: '/configuration/btp' },
           { text: 'Productive Usage', link: '/configuration/productive_usage' },
+          { text: 'Installation', link: '/configuration/installation' , items: [
+            { text: 'Fiori Launchpad', link: '/configuration/launchpad', },
+            { text: 'S/4 Public Cloud', link: '/configuration/s4_public_cloud' },
+            { text: 'BTP Workzone', link: '/configuration/btp' },
+           ]
+          },
         ]
       },
       {

docs/configuration/authorization.md

@@ -1,8 +1,11 @@
+---
+outline: [2, 4]
+---
 # Authorization
 
 abap2UI5 offers flexible ways to manage authorization handling. It doesn’t include a built-in authorization mechanism, allowing developers to create their own solutions either at the service or application level.
 
-### Service-Level Authorization
+### Service-Level 
 One of the easiest ways to manage access to different apps is by implementing checks within the HTTP handler. This approach allows the developer to restrict access to individual apps based on the APP_START parameter, directly in the ICF service handler class.
 
 ##### Example: Restricting Access Based on URL Parameters
@@ -73,7 +76,7 @@ CLASS z2ui5_cl_launchpad_handler IMPLEMENTATION.
 ENDCLASS.
 ```
 
-### Application-Level Authorization
+### Application-Level
 Alternatively, you can handle authorization within individual app classes. This approach is useful if you want to delegate authorization to each app, ensuring that it checks user permissions before performing any actions.
 
 ##### Example: Authorization Check in an App Class

docs/configuration/btp.md

@@ -1,3 +1,6 @@
+---
+outline: [2, 4]
+---
 # BTP Build Workzone
 
 Integrate your abap2UI5 apps into BTP Services like Build Workzone. Find all information here:<br>

docs/configuration/launchpad.md

@@ -1,3 +1,6 @@
+---
+outline: [2, 4]
+---
 # Fiori Launchpad
 
 Integrate your abap2UI5 apps into SAP Fiori Launchpads. Find all information here: <br>

docs/configuration/performance.md

@@ -1,6 +1,14 @@
+---
+outline: [2, 4]
+---
+
 # Performance
 
-abap2UI5 is fast! Nearly everything is done in the backend, and the ABAP stack is much faster than any client or browser. Frontend logic is kept to a minimum: no loops are executed, and no extra logic is added. Everything is prepared in the backend and then directly übergeben into the UI5 framework at the client side. abap2UI5 has been successfully tested with tables containing a large number of entries and columns. So, just develop your app, and you can assume that performance will not be an issue.<br>
+abap2UI5 is fast! Almost everything is processed in the backend, with the ABAP stack performing significantly faster than any client or browser. <br>
+
+Frontend logic is kept to a minimum: no loops are executed, no extra logic is added, and everything is passed directly to the UI5 framework. <br>
+
+abap2UI5 has been successfully tested with tables containing a large number of entries and columns. So, just develop your app confidently — performance should not be an issue.
 
 ### Suggestions
 If you still want to optimize your app, consider the following points:
@@ -10,4 +18,4 @@ If you still want to optimize your app, consider the following points:
 * Follow the usual ABAP best practices: reduce loops, use sorted tables, etc., just like with ALV in the past
 
 ### Performance Issues?
-Try to minimize them and create a sample. We are happy to analyze and check if we can make abap2UI5 run even faster.
+If you encounter performance issues, try creating a sample and submitting a pull request to the samples repository. We’d be happy to analyze and see if we can make abap2UI5 even faster.

docs/configuration/productive_usage.md

@@ -1,3 +1,7 @@
+---
+outline: [2, 4]
+---
+
 # Use in Production
 
 abapUI5 is technically just an implementation of an HTTP handler and can be used as any other HTTP Service also in a productive scenario.

docs/configuration/se80.md

@@ -1,3 +1,7 @@
+---
+outline: [2, 3]
+---
+
 # Security
 
 ### HTTP Endpoint

docs/configuration/security.md

@@ -2,7 +2,7 @@
 outline: [2, 4]
 ---
 
-# Setup
+# Settings
 
 abap2UI5 can be run with various custom configurations. This is the call for the default setup:
 ```abap

docs/configuration/setup.md

@@ -1,3 +1,6 @@
+---
+outline: [2, 4]
+---
 # UI5 Versions
 
 The frontend UI is created with the UI5 framework, which exists in different versions, and you can choose the version for abap2UI5 during bootstrapping. It’s recommended to bootstrap abap2UI5 using the same repository that you use for other UI5 apps in your system.