docs: split Messages, Errors into Messages/Errors sub-pages and move Logging in

Author: claude

docs/.vitepress/config.mjs

@@ -150,7 +150,15 @@ export default defineConfig({
               },
             ],
           },
-          { text: "Messages, Errors", link: "/development/messages" },
+          {
+            text: "Messages, Errors",
+            collapsed: true,
+            items: [
+              { text: "Messages", link: "/development/messages/messages" },
+              { text: "Errors", link: "/development/messages/errors" },
+              { text: "Logging", link: "/development/messages/logging" },
+            ],
+          },
           { text: "Translation, i18n", link: "/development/translation" },
           { text: "Popups, Popovers", link: "/development/popups" },
           {
@@ -197,7 +205,6 @@ export default defineConfig({
             text: "Misc Topics",
             collapsed: true,
             items: [
-              { text: "Logging", link: "/development/specific/logging" },
               { text: "XLSX", link: "/development/specific/xlsx" },
               { text: "Locks", link: "/development/specific/locks" },
               { text: "Statefulness", link: "/development/specific/statefulness" },

docs/development/messages/errors.md

@@ -0,0 +1,42 @@
+---
+outline: [2, 4]
+---
+# Errors
+
+Beyond plain messages, abap2UI5 ships dedicated popups and fallbacks for handling exceptions and unexpected failures.
+
+#### Error Popup
+To display full details of your exception:
+```abap
+METHOD z2ui5_if_app~main.
+
+  TRY.
+    DATA(lv_val) = 1 / 0.
+  CATCH cx_root INTO DATA(lx).
+    client->nav_app_call( z2ui5_cl_pop_error=>factory( lx ) ).
+  ENDTRY.
+
+ENDMETHOD.
+```
+
+#### Uncaught Errors
+When your code doesn't catch exceptions, the framework catches them and displays the standard error popup. Try this:
+
+```abap
+METHOD z2ui5_if_app~main.
+
+    RAISE EXCEPTION NEW cx_sy_itab_line_not_found( ).
+
+ENDMETHOD.
+```
+
+#### Uncatchable Exceptions / Short Dumps
+What happens if your code raises uncatchable exceptions? The default HTTP handler exception output appears. Processing halts, and the user has to reload the browser. Reserve this for unexpected cases:
+
+```abap
+METHOD z2ui5_if_app~main.
+
+    ASSERT 1 = `This is an error message!`.
+
+ENDMETHOD.
+```

docs/development/specific/logging.md docs/development/messages/logging.mddocs/development/specific/logging.md renamed to docs/development/messages/logging.md

@@ -1,9 +1,9 @@
 ---
 outline: [2, 5]
 ---
-# Messages, Errors
+# Messages
 
-Showing messages and errors is an everyday task for ABAP developers. The functions below cover the most common cases.
+Showing messages is an everyday task for ABAP developers. The functions below cover the most common cases.
 
 #### Message Toast
 
@@ -86,41 +86,6 @@ METHOD z2ui5_if_app~main.
 
   client->nav_app_call( z2ui5_cl_pop_messages=>factory( lt_msg ) ).
 
-ENDMETHOD.
-```
-#### Error Popup
-To display full details of your exception:
-```abap
-METHOD z2ui5_if_app~main.
-
-  TRY.
-    DATA(lv_val) = 1 / 0.
-  CATCH cx_root INTO DATA(lx).
-    client->nav_app_call( z2ui5_cl_pop_error=>factory( lx ) ).
-  ENDTRY.
-
-ENDMETHOD.
-```
-
-#### Uncaught Errors
-When your code doesn't catch exceptions, the framework catches them and displays the standard error popup. Try this:
-
-```abap
-METHOD z2ui5_if_app~main.
-
-    RAISE EXCEPTION NEW cx_sy_itab_line_not_found( ).
-
-ENDMETHOD.
-```
-
-#### Uncatchable Exceptions / Short Dumps
-What happens if your code raises uncatchable exceptions? The default HTTP handler exception output appears. Processing halts, and the user has to reload the browser. Reserve this for unexpected cases:
-
-```abap
-METHOD z2ui5_if_app~main.
-
-    ASSERT 1 = `This is an error message!`.
-
 ENDMETHOD.
 ```