Merge View > Overview into Definition

Absorb the UI5 1:1 framing, the 'Where to Look for Controls' pointers,
and the 'Choosing a Control' table into definition.md. Delete the
separate overview page and update the sidebar.

Author: claude

docs/.vitepress/config.mjs

@@ -124,10 +124,9 @@ export default defineConfig({
         items: [
           {
             text: "View",
-            link: "/cookbook/view/overview",
+            link: "/cookbook/view/definition",
             collapsed: true,
             items: [
-              { text: "Overview", link: "/cookbook/view/overview" },
               { text: "Definition", link: "/cookbook/view/definition" },
               { text: "Nested Views", link: "/cookbook/view/nested_views" },
               { text: "XML Templating", link: "/cookbook/view/xml_templating" },

docs/cookbook/view/definition.md

@@ -3,7 +3,13 @@ outline: [2, 4]
 ---
 # Definition
 
-In abap2UI5, UI5 renders the UI from an XML view that you build in ABAP. A simple example with raw XML:
+abap2UI5 uses [SAP UI5](https://sapui5.hana.ondemand.com) on the frontend without modification. Whatever your ABAP code sends to the browser is a **standard UI5 XML view** — the same XML you would write in any UI5 freestyle project.
+
+The consequence: **everything in the UI5 SDK works in abap2UI5 1:1**. Any control, any property, any namespace from the [UI5 Demo Kit](https://sapui5.hana.ondemand.com/sdk) is available. Copy the XML, paste it into your ABAP class, and it renders.
+
+#### Sending a View
+
+The simplest case: build an XML string and ship it to the client.
 
 ```abap
   METHOD z2ui5_if_app~main.
@@ -20,7 +26,12 @@ In abap2UI5, UI5 renders the UI from an XML view that you build in ABAP. A simpl
 
 ENDMETHOD.
 ```
-You can use any UI5 control from the [UI5 SDK](https://sapui5.hana.ondemand.com). But writing raw XML quickly turns cumbersome. A handier approach is the `Z2UI5_CL_XML_VIEW` helper class, with a fluent API for building views. The `stringify( )` method at the end converts the view tree into an XML string that the framework sends to the frontend:
+
+Swap `<Text>` for any other control from the SDK; the framework doesn't care.
+
+#### Helper Class
+
+Writing raw XML by hand quickly turns cumbersome. abap2UI5 ships the helper class `z2ui5_cl_xml_view` with a fluent API that mirrors the XML structure and gives you code completion. The `stringify( )` method at the end converts the view tree into an XML string that the framework sends to the frontend:
 
 ```abap
   METHOD z2ui5_if_app~main.
@@ -35,6 +46,8 @@ You can use any UI5 control from the [UI5 SDK](https://sapui5.hana.ondemand.com)
   ENDMETHOD.
 ```
 
+Both snippets produce the exact same view. Use whichever you prefer — raw strings are fine for a handful of lines, the fluent API scales better for real apps.
+
 Tips for working with views:
 - Use code completion on `Z2UI5_CL_XML_VIEW` to find controls and properties
 - See the [samples repository](/get_started/next#sample-apps) for ready-made XML examples to copy and adapt
@@ -52,6 +65,39 @@ Combining controls in a way that violates these rules can lead to broken renderi
 The ABAP compiler cannot catch these mistakes — they are pure UI5 concerns and must be verified against the SDK documentation.
 :::
 
+#### Where to Look for Controls
+
+Because UI5 XML is used 1:1, **the UI5 documentation is your reference** for anything visual:
+
+- [UI5 Demo Kit](https://sapui5.hana.ondemand.com/sdk) — interactive samples for every control
+- [UI5 Control API](https://sapui5.hana.ondemand.com/sdk/#/api) — properties, aggregations, events
+
+Find a control you like in the UI5 docs, copy its XML, paste it into `view_display( )` — done. abap2UI5 has no separate control catalog to learn.
+
+#### Choosing a Control
+
+The UI5 SDK is large. The table below covers the choices that come up in almost every abap2UI5 app — use it as a starting point before diving into the SDK.
+
+| Need                              | Use                                                   | Notes                                                                              |
+| --------------------------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------- |
+| Tabular data, columns, sorting    | `sap.m.Table`                                         | Responsive, supports growing/p13n. Default choice for business data.               |
+| Flat list with icons/avatars      | `sap.m.List` with `StandardListItem`                  | Lighter than `Table` when columns are not needed.                                  |
+| Hierarchical data (parent/child)  | `sap.m.Tree` or `sap.ui.table.TreeTable`              | `Tree` is responsive; `TreeTable` shows fixed columns.                             |
+| Form with labels + inputs         | `sap.ui.layout.form.SimpleForm`                       | Use this 90% of the time — auto-layouts labels and fields responsively.            |
+| Form with custom grid layout      | `sap.ui.layout.form.Form`                             | When `SimpleForm` is not flexible enough.                                          |
+| App page with title and content   | `sap.m.Page`                                          | The standard container. Wrap in `sap.m.Shell` for the SAP frame.                   |
+| Page with collapsible header      | `sap.f.DynamicPage`                                   | For object pages and analytics screens.                                            |
+| Page with action toolbar          | `sap.f.semantic.SemanticPage`                         | Adds semantic actions (edit, delete, share) in the footer.                         |
+| Vertical / horizontal stack       | `sap.m.VBox` / `sap.m.HBox`                           | Quick layout without a form.                                                       |
+| Tabs                              | `sap.m.IconTabBar`                                    | Use `IconTabFilter` for each tab.                                                  |
+| Single-select dropdown            | `sap.m.Select` (≤ 20 items) / `sap.m.ComboBox`        | `ComboBox` allows typing and filtering.                                            |
+| Multi-select dropdown             | `sap.m.MultiComboBox`                                 | Pills appear inside the field.                                                     |
+| Date / time input                 | `sap.m.DatePicker` / `sap.m.TimePicker` / `sap.m.DateTimePicker` | Needs a formatter — see [Binding → Data-Type Mapping](/cookbook/model/binding#data-type-mapping). |
+| Status indicator                  | `sap.m.ObjectStatus`                                  | Colored text + icon for state.                                                     |
+| Modal dialog                      | `sap.m.Dialog` (built with `factory_popup`)           | See [Popover](/cookbook/popup_popover/popover).                                    |
+
+When two controls fit, prefer the simpler one: `Table` over `TreeTable`, `SimpleForm` over `Form`, `Select` over `ComboBox`. Switch to the richer variant only when a concrete requirement justifies it.
+
 ## Mapping UI5 XML ↔ ABAP Fluent API
 
 `Z2UI5_CL_XML_VIEW` is a hand-curated wrapper around UI5 controls. It does not cover every UI5 control, and the naming is not always a strict 1:1 mapping of the UI5 SDK: