Merge pull request #46 from abap2UI5/claude/analyze-documentation-gYG3b

Reorganize documentation images into section-specific directories

Author: oblomov-dev

docs/.vitepress/config.mjs

@@ -205,7 +205,7 @@ export default defineConfig({
       },
       {
         text: "Advanced Topics",
-        link: "/advanced/advanced",
+        link: "/advanced/downporting",
         collapsed: true,
         items: [
           { text: "Downporting", link: "/advanced/downporting" },

docs/advanced/rfc.md

@@ -24,7 +24,7 @@ The system that calls the app (the frontend system) includes the UI5 library and
 _Prerequisite: Set up a destination in SM59 so the source system can be called via RFC. abap2UI5 needs to be installed in both systems._
 
 Steps:
-1. Install the [abap2UI5 RFC Connector](https://github.com/abap2UI5-addons/rfc-connector) via abapGit on both system
+1. Install the [abap2UI5 RFC Connector](https://github.com/abap2UI5-addons/rfc-connector) via abapGit on both systems
 2. Replace in the HTTP handler the destination `NONE` with your Source System Destination
 3. Call in your browser the endpoint `.../sap/bc/2ui5_rfc`
 

docs/configuration/productive_usage.md

@@ -18,7 +18,7 @@ The project will be continuously further developed, so there's no specific "stab
 
 #### Transport
 Install the project using abapGit into your development system. Then, use the normal transport process for deployment to production:
-![Transport process from development to production via abapGit](image-3.png){ width=80% }
+![Transport process from development to production via abapGit](/configuration/image-3.png){ width=80% }
 
 #### Renaming
 If you're starting new development but already have abap2UI5 apps running in production, and you're worried about updating to the latest release, consider installing abap2UI5 multiple times in your system using the [renaming feature](/advanced/renaming). This way, you can safely continue development without affecting your existing apps in production.

docs/configuration/troubleshooting.md

@@ -13,7 +13,7 @@ On the frontend, abap2UI5 behaves like a standard UI5 app, so you can use all ty
 
 ##### Debugging Tools
 To begin, press `Ctrl+F12` to open the built-in debugger tools in abap2UI5
-![Built-in debugger showing XML View and Data Model inspection](debug.png)
+![Built-in debugger showing XML View and Data Model inspection](/configuration/debug.png)
 Here, you can inspect the XML View and check the Data Model bound to the view.
 
 ##### UI5 Inspector

docs/development/messages.md

@@ -44,7 +44,7 @@ ENDMETHOD.
 
 #### SY, BAPIRET, CX_ROOT
 You can directly pass common message structures, objects, and variables to the functions:
-###### SY
+#### SY
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -53,7 +53,7 @@ METHOD z2ui5_if_app~main.
 
 ENDMETHOD.
 ```
-###### BAPIRET
+#### BAPIRET
 ```abap
 METHOD z2ui5_if_app~main.
 
@@ -67,7 +67,7 @@ METHOD z2ui5_if_app~main.
 
 ENDMETHOD.
 ```
-###### CX_ROOT
+#### CX_ROOT
 ```abap
 METHOD z2ui5_if_app~main.
 

docs/get_started/quickstart.md

@@ -8,10 +8,10 @@ outline: [2, 4]
 
 Install [abap2UI5](https://github.com/abap2UI5/abap2UI5) with [abapGit](https://abapgit.org):
 
-![abapGit repository installation screen for abap2UI5](image.png)
+![abapGit repository installation screen for abap2UI5](/get_started/image.png)
 
 ::: details ABAP Cloud
-![abapGit installation for ABAP Cloud environments](image-4.png)
+![abapGit installation for ABAP Cloud environments](/get_started/image-4.png)
 :::
 
 
@@ -50,7 +50,7 @@ ENDCLASS.
 Next use the transaction SICF to create a new HTTP service with the handler above:
 
 ![SICF service creation dialog in transaction SICF](https://github.com/user-attachments/assets/b76d9459-79be-40e1-a00e-b4e8cbbab9d4) <br>
-![HTTP handler class assignment in SICF service configuration](image-5.png)
+![HTTP handler class assignment in SICF service configuration](/get_started/image-5.png)
 
 ::: details ABAP Cloud
 For ABAP Cloud environments, follow [this guide](https://developers.sap.com/tutorials/abap-environment-create-http-service.html).

docs/get_started/samples.md

@@ -8,11 +8,11 @@ With over 250 samples, the [samples repository](https://github.com/abap2UI5/samp
 
 ### Samples
 Try out samples for tables, lists, trees, and many other UI5 controls. Copy and paste code snippets to accelerate your development:
-![Sample apps overview showing tables, lists, trees and other UI5 controls](image-1.png)
+![Sample apps overview showing tables, lists, trees and other UI5 controls](/get_started/image-1.png)
 
 ### Jump into the Code
 Press `CTRL+F12` to open the source code, view, and model for each sample:
-![Source code viewer opened with CTRL+F12 showing code, view and model](image-2.png)
+![Source code viewer opened with CTRL+F12 showing code, view and model](/get_started/image-2.png)
 
 _Don't have a system available? You can also run the samples directly in your browser [here](https://abap2ui5.github.io/web-abap2ui5-samples/)._
 

docs/get_started/use_cases.md

@@ -12,26 +12,26 @@ For a comprehensive overview, see [this article](https://www.linkedin.com/pulse/
 
 #### Tier 1 Extension
 For clean-core compliance, develop applications that follow "keep the core clean" principles, ensuring your apps stay cloud-ready and upgrade-stable:
-![Tier 1 on-stack extension architecture diagram](image-11.png){ width=60% }
+![Tier 1 on-stack extension architecture diagram](/get_started/image-11.png){ width=60% }
 
 #### Tier 2 Extension
 If certain APIs you need are not yet released, you can still create a cloud-ready abap2UI5 app by accessing these APIs through a separate Tier 2 wrapper:
-![Tier 2 on-stack extension with wrapper for unreleased APIs](image-21.png){ width=60% }
+![Tier 2 on-stack extension with wrapper for unreleased APIs](/get_started/image-21.png){ width=60% }
 
 #### Tier 3 Extension
 For a classic extension approach, you can use unreleased APIs, giving you greater freedom to customize and extend your system:
-![Tier 3 on-stack extension with unreleased API access](image-10.png){ width=60% }
+![Tier 3 on-stack extension with unreleased API access](/get_started/image-10.png){ width=60% }
 
 ### Side-by-Side Extension
 
 #### Tier 1 Extension
 Develop applications separately from your S/4 system's lifecycle using only remote API calls. Stick to released APIs and your apps will work with S/4HANA Public Cloud too:
-![Tier 1 side-by-side extension with remote API calls](image-22.png){ width=60% }
+![Tier 1 side-by-side extension with remote API calls](/get_started/image-22.png){ width=60% }
 
 #### Tier 3 Extension
 For more flexibility, develop applications with an independent lifecycle from your S/4 system using remote API calls:
-![Tier 3 side-by-side extension with remote API calls](image-23.png){ width=60% }
+![Tier 3 side-by-side extension with remote API calls](/get_started/image-23.png){ width=60% }
 
 ### Software as a Service
 With a Tier 1 side-by-side extension, you can connect the same abap2UI5 app to multiple S/4 systems. Use the same abap2UI5 code across different customer tenants and remote systems to create a true SaaS scenario:
-![SaaS architecture connecting one abap2UI5 app to multiple S/4 tenants](image-9.png){ width=60% }
+![SaaS architecture connecting one abap2UI5 app to multiple S/4 tenants](/get_started/image-9.png){ width=60% }