From a5102e0f4e0005fe0dfede5c66eb7aa67a93d6c1 Mon Sep 17 00:00:00 2001
From: Nicolas Lunet <nicolas.lunet@sap.com>
Date: Tue, 25 Oct 2022 10:23:52 +0200
Subject: [PATCH 1/2] Replace all reference to `custom` folder with `ext`

---
 docs/06_SAP_Fiori_Elements/actions-cbf16c5.md  | 18 +++++++++---------
 ...ding-a-section-to-an-object-page-a357047.md | 10 +++++-----
 ...m-actions-using-extension-points-7619517.md | 18 +++++++++---------
 ...-custom-fields-to-the-filter-bar-5fb9f57.md | 18 +++++++++---------
 ...-content-to-object-page-sections-8e01a46.md |  8 ++++----
 ...erties-in-the-navigation-context-199a496.md |  4 ++--
 ...ons-added-using-extension-points-dd78aca.md |  4 ++--
 ...igation-to-different-detail-page-75002b3.md |  4 ++--
 ...ponsive-table-in-the-list-report-a12ad60.md |  4 ++--
 ...ponsive-table-on-the-object-page-b20dc7a.md |  4 ++--
 ...ng-sap-fiori-elements-based-apps-358cf25.md |  4 ++--
 ...nts-for-forms-on-the-object-page-4e49753.md |  4 ++--
 ...ts-for-object-page-header-facets-61cf0ee.md | 16 ++++++++--------
 ...-for-sections-on-the-object-page-92ad996.md |  6 +++---
 ...r-subsections-on-the-object-page-ce8d468.md |  2 +-
 .../extension-points-for-tables-d525522.md     |  6 +++---
 ...nts-for-views-in-the-list-report-eb37203.md | 10 +++++-----
 ...en-sap-keep-alive-is-set-to-true-f1c2704.md |  2 +-
 .../share-functionality-022bf0d.md             |  4 ++--
 19 files changed, 73 insertions(+), 73 deletions(-)

diff --git a/docs/06_SAP_Fiori_Elements/actions-cbf16c5.md b/docs/06_SAP_Fiori_Elements/actions-cbf16c5.md
index 5af6f9b8..786cd081 100644
--- a/docs/06_SAP_Fiori_Elements/actions-cbf16c5.md
+++ b/docs/06_SAP_Fiori_Elements/actions-cbf16c5.md
@@ -1599,7 +1599,7 @@ The following default values are available:
     >                                 "@com.sap.vocabularies.UI.v1.LineItem": {
     >                                     "actions": {
     >                                         "DataFieldForAction::com.c_salesordermanage_sd.CreateWithSalesOrderType": {
-    >                                             "defaultValuesFunction": "SalesOrder.custom.CustomActions.getDefaultValues"
+    >                                             "defaultValuesFunction": "SalesOrder.ext.CustomActions.getDefaultValues"
     >                                         }
     >                                     }
     >                                 }
@@ -1775,11 +1775,11 @@ Make the following settings in the manifest to group actions under a menu button
 >               "header": {
 >                 "actions": {
 >                     "myFirstAction": {
->                         "press": "SalesOrder.custom.CustomActions.message",
+>                         "press": "SalesOrder.ext.CustomActions.message",
 >                         "text": "My First Action"
 >                     },
 >                     "mySecondAction": {
->                         "press": "SalesOrder.custom.CustomActions.message",
+>                         "press": "SalesOrder.ext.CustomActions.message",
 >                         "text": "My Second Action"
 >                     },
 >                     "MenuActions": {
@@ -1811,13 +1811,13 @@ Make the following settings in the manifest to group actions under a menu button
 >             "@com.sap.vocabularies.UI.v1.FieldGroup#OrderData": {
 >                 "actions": {
 >                     "myFirstAction": {
->                         "press": "SalesOrder.custom.CustomActions.getCustomerName",
+>                         "press": "SalesOrder.ext.CustomActions.getCustomerName",
 >                         "visible": true,
 >                         "enabled": true,
 >                         "text": "My First Action"
 >                     },
 >                     "mySecondAction": {
->                         "press": "SalesOrder.custom.CustomActions.message",
+>                         "press": "SalesOrder.ext.CustomActions.message",
 >                         "text": "My Second Action"
 >                     },
 >                     "MenuActions": {
@@ -1848,13 +1848,13 @@ Make the following settings in the manifest to group actions under a menu button
 >             "@com.sap.vocabularies.UI.v1.LineItem": {
 >                 "actions": {
 >                     "myFirstAction": {
->                         "press": "SalesOrder.custom.CustomActions.getCustomerName",
+>                         "press": "SalesOrder.ext.CustomActions.getCustomerName",
 >                         "visible": true,
 >                         "enabled": true,
 >                         "text": "My First Action"
 >                     },
 >                     "mySecondAction": {
->                         "press": "SalesOrder.custom.CustomActions.message",
+>                         "press": "SalesOrder.ext.CustomActions.message",
 >                         "text": "My Second Action"
 >                     },
 >                     "MenuActions": {
@@ -1928,8 +1928,8 @@ For certain properties, you can overwrite the annotation-based values via the ma
 >     "@com.sap.vocabularies.UI.v1.LineItem": {
 >         "actions": {
 >             "DataFieldForAction::com.c_salesordermanage_sd.CreateWithSalesOrderType": {
->                 "enabled": "SalesOrder.custom.CustomActions.enabledIfTwoSelected"
->                 "visible": "SalesOrder.custom.CustomActions.visibleIfAConditionIsTrue"
+>                 "enabled": "SalesOrder.ext.CustomActions.enabledIfTwoSelected"
+>                 "visible": "SalesOrder.ext.CustomActions.visibleIfAConditionIsTrue"
 >             }
 >         }
 >     }
diff --git a/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md b/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
index 974e4a0c..8438d6c3 100644
--- a/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
+++ b/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
@@ -149,14 +149,14 @@ The object page of the *Manage Products* app shows the new section *Product Desc
 
 In the editor of your choice, open the folder structure of the project where you want to make the adaptation and proceed as follows:
 
-1.  In the `webapp` folder, create a new subfolder called `custom`.
-2.  In the folder `custom`, create the file `CustomSection.view.xml`.
+1.  In the `webapp` folder, create a new subfolder called `ext`.
+2.  In the folder `ext`, create the file `CustomSection.view.xml`.
 3.  Define the view with its elements, in this example a `VerticalLayout` with several other controls is used. Bindings can be used as well.
 
     > ### Sample Code:  
     > ```xml
     > <core:FragmentDefinition xmlns:core="sap.ui.core" xmlns="sap.m" xmlns:l="sap.ui.layout">
-    > 	<l:VerticalLayout core:require="{handler: 'SalesOrder/custom/CustomColumn'}">
+    > 	<l:VerticalLayout core:require="{handler: 'SalesOrder/ext/CustomColumn'}">
     > 		<Button text="Custom Button" press="handler.buttonPressed" />
     > 	</l:VerticalLayout>
     > </core:FragmentDefinition>
@@ -215,7 +215,7 @@ The extension appears within the `ObjectPage.view` before or after the defined s
 > 									"sections": {
 > 										"customSection": {
 > 											"type": "XMLFragment",
-> 											"name": "SalesOrder.custom.CustomSection",
+> 											"name": "SalesOrder.ext.CustomSection",
 > 											"title": "{i18n>customSection}",
 > 											"position": {
 > 												"placement": "Before",
@@ -224,7 +224,7 @@ The extension appears within the `ObjectPage.view` before or after the defined s
 > 										},
 > 										"anotherCustomSection": {
 > 											"type": "XMLFragment",
-> 											"name": "SalesOrder.custom.CustomFieldForm",
+> 											"name": "SalesOrder.ext.CustomFieldForm",
 > 											"title": "Field Form",
 > 											"position": {
 > 												"placement": "After",
diff --git a/docs/06_SAP_Fiori_Elements/adding-custom-actions-using-extension-points-7619517.md b/docs/06_SAP_Fiori_Elements/adding-custom-actions-using-extension-points-7619517.md
index 3ea84397..f4adaba4 100644
--- a/docs/06_SAP_Fiori_Elements/adding-custom-actions-using-extension-points-7619517.md
+++ b/docs/06_SAP_Fiori_Elements/adding-custom-actions-using-extension-points-7619517.md
@@ -568,8 +568,8 @@ These custom actions are displayed as buttons on the UI. When the user selects t
     > 
     > ```
     > "myCustomEnablement": {
-    >      "press": "SalesOrder.custom.CustomActions.navigateExternal",
-    >      "enabled": "SalesOrder.custom.CustomActions.enabledForCompletedOnly",
+    >      "press": "SalesOrder.ext.CustomActions.navigateExternal",
+    >      "enabled": "SalesOrder.ext.CustomActions.enabledForCompletedOnly",
     >      "text": "Enabled for Completed"
     > }
     > ```
@@ -705,7 +705,7 @@ These custom actions are displayed as buttons on the UI. When the user selects t
         >      "<NavigationPropertyFromRootEntityType>/@com.sap.vocabularies.UI.v1.LineItem": {
         >           "actions": {
         >                "myCustomAction": {
-        >                     "press": "TestApplication.custom.CustomActions.message"
+        >                     "press": "TestApplication.ext.CustomActions.message"
         >                     ....
         >                }
         >           }
@@ -713,9 +713,9 @@ These custom actions are displayed as buttons on the UI. When the user selects t
         > }
         > ```
 
-    2.  Create a folder called *custom* in the webapp folder of the application.
+    2.  Create a folder called *ext* in the webapp folder of the application.
 
-    3.  Create a file called *CustomActions.js* in the *custom* folder.
+    3.  Create a file called *CustomActions.js* in the *ext* folder.
 
     4.  Create a method called *message* in the *CustomActions.js* file.
 
@@ -905,7 +905,7 @@ These custom actions are displayed as buttons on the UI. When the user selects t
     >                                 "@com.sap.vocabularies.UI.v1.FieldGroup#OrderData": {
     >                                     "actions": {
     >                                         "customSectionAction": {
-    >                                             "press": "SalesOrder.custom.CustomActions.alert",
+    >                                             "press": "SalesOrder.ext.CustomActions.alert",
     >                                             "visible": true,
     >                                             "enabled": true,
     >                                             "text": "Alert",
@@ -915,7 +915,7 @@ These custom actions are displayed as buttons on the UI. When the user selects t
     >                                             }
     >                                         },
     >                                         "sectionAction2": {
-    >                                             "press": "SalesOrder.custom.CustomActions.accountDetails",
+    >                                             "press": "SalesOrder.ext.CustomActions.accountDetails",
     >                                             "visible": true,
     >                                             "enabled": true,
     >                                             "text": "Display account details",
@@ -952,14 +952,14 @@ These custom actions are displayed as buttons on the UI. When the user selects t
     >                             "@com.sap.vocabularies.UI.v1.FieldGroup#OrderData": {
     >                                 "actions": {
     >                                     "customSectionAction": {
-    >                                         "press": "SalesOrder.custom.CustomActions.alert",
+    >                                         "press": "SalesOrder.ext.CustomActions.alert",
     >                                         "visible": true,
     >                                         "enabled": false,
     >                                         "text": "Action on Form",
     >                                         "inline": true
     >                                     },
     >                                     "customSectionAction2": {
-    >                                         "press": "SalesOrder.custom.CustomActions.alert",
+    >                                         "press": "SalesOrder.ext.CustomActions.alert",
     >                                         "visible": true,
     >                                         "enabled": true,
     >                                         "text": "Action not on Form"
diff --git a/docs/06_SAP_Fiori_Elements/adding-custom-fields-to-the-filter-bar-5fb9f57.md b/docs/06_SAP_Fiori_Elements/adding-custom-fields-to-the-filter-bar-5fb9f57.md
index b107f223..2623df3b 100644
--- a/docs/06_SAP_Fiori_Elements/adding-custom-fields-to-the-filter-bar-5fb9f57.md
+++ b/docs/06_SAP_Fiori_Elements/adding-custom-fields-to-the-filter-bar-5fb9f57.md
@@ -93,7 +93,7 @@ You can configure the `FilterBar` locally via the section `@com.sap.vocabularies
 >                                         "MyCustomRatingThing": {
 >                                             "label": "{i18n>CustomRatingFilter}",
 >                                             "property": "Rating",
->                                             "template": "SalesOrder.custom.CustomRatingFilter",
+>                                             "template": "SalesOrder.ext.CustomRatingFilter",
 >                                             "required": true,
 >                                             "position": {
 >                                                 "placement": "After",
@@ -116,7 +116,7 @@ You can use the `filterFields` setting to add custom filters. The pattern looks
 > "<key>": {
 >     "label": <UILabel>,                   // static string or i18n binding, e.g. "MyText" or "{i18n>MyCustomLabel}"
 >     "property": <FullPropertyPath>,       // the full path to the property to be filtered, e.g. "Rating" or "_Partner/Rating"
->     "template": <XmlFragmentPath>,        // the path to the Xml Template containing the filter control, e.g. "SalesOrder.custom.CustomRatingFilter"
+>     "template": <XmlFragmentPath>,        // the path to the Xml Template containing the filter control, e.g. "SalesOrder.ext.CustomRatingFilter"
 >     "required": (false) | true,           // filter field is (not) mandatory, i.e. it requires a value
 >     "position": {
 >         "placement": "Before"|"After",
@@ -134,7 +134,7 @@ The following sample code shows how you can build an XML template for an app cal
 > ### Sample Code:  
 > ```
 > <core:FragmentDefinition xmlns:core="sap.ui.core" xmlns="sap.m" xmlns:l="sap.ui.layout">
->     <HBox alignItems="Center" core:require="{handler: 'SalesOrder/custom/CustomRating'}" width="100%">
+>     <HBox alignItems="Center" core:require="{handler: 'SalesOrder/ext/CustomRating'}" width="100%">
 >  
 > <!--     // either handle value change in the handler... // -->
 > <!--     <RatingIndicator id="MyCustomRatingIndicatorId" value="{= ${filterValues>} ? ${filterValues>}.substring(1) : null }" change="handler.onValueChanged" />-->
@@ -153,7 +153,7 @@ The following sample code shows how you can build an XML template for an app cal
 > </core:FragmentDefinition>
 > ```
 
-You can build these custom filter fields for different properties of the `SalesOrder`. To facilitate this, ensure that the key specified in the `manifest.json` is a unique string. The previous sample code shows the usage of custom handlers, that is, handling value changes or handling a button click that resets the filters. Following the naming of this example, these handlers are defined in file `SalesOrder/custom/CustomRating.js`.
+You can build these custom filter fields for different properties of the `SalesOrder`. To facilitate this, ensure that the key specified in the `manifest.json` is a unique string. The previous sample code shows the usage of custom handlers, that is, handling value changes or handling a button click that resets the filters. Following the naming of this example, these handlers are defined in file `SalesOrder/ext/CustomRating.js`.
 
 > ### Sample Code:  
 > ```
@@ -188,8 +188,8 @@ If you want to avoid your users having to enter the exact values of a `SalesOrde
 >     
 >         <ComboBox
 >             id="MyCustomRatingComboBox"
->             core:require="{handler: 'SalesOrder/custom/CustomRating'}"
->             selectedKey="{path: 'filterValues>', type: 'sap.fe.macros.filter.type.Value', formatOptions: { operator: 'SalesOrder.custom.CustomRating.ratingLevels' }}"
+>             core:require="{handler: 'SalesOrder/ext/CustomRating'}"
+>             selectedKey="{path: 'filterValues>', type: 'sap.fe.macros.filter.type.Value', formatOptions: { operator: 'SalesOrder.ext.CustomRating.ratingLevels' }}"
 >         >
 >             <items>
 >                 <core:Item key="Low" text="Low Rating" />
@@ -200,7 +200,7 @@ If you want to avoid your users having to enter the exact values of a `SalesOrde
 > </core:FragmentDefinition>
 > ```
 
-In the following example, these custom filter operators are defined in function `ratingLevels()` of file `SalesOrder/custom/CustomRating.js` and returned as custom filter conditions containing the values that you want to define:
+In the following example, these custom filter operators are defined in function `ratingLevels()` of file `SalesOrder/ext/CustomRating.js` and returned as custom filter conditions containing the values that you want to define:
 
 > ### Sample Code:  
 > Implementation of the Custom Rating Operator
@@ -244,7 +244,7 @@ You can also define your custom filter as mandatory by setting it to `required =
 > ```
 > <core:FragmentDefinition xmlns:core="sap.ui.core" xmlns="sap.m">
 >     <Input
->         core:require="{handler: 'SalesOrder/custom/CustomRating'}"
+>         core:require="{handler: 'SalesOrder/ext/CustomRating'}"
 >         value="{path: 'filterValues>', type: 'sap.fe.macros.filter.type.Value', formatOptions: { operator: 'Contains' }}"
 >         valueState="{path: 'filterValues>', formatter: 'handler.onFilterInputFormatValue'}"
 >         placeholder="{i18n>customStringFilterPlaceholder}"
@@ -252,7 +252,7 @@ You can also define your custom filter as mandatory by setting it to `required =
 > </core:FragmentDefinition>
 > ```
 
-The red frame is switched on or off by the formatter `onFilterInputFormatValue()` in the file `SalesOrder/custom/CustomFilter.js` that updates the value state of the input field:
+The red frame is switched on or off by the formatter `onFilterInputFormatValue()` in the file `SalesOrder/ext/CustomFilter.js` that updates the value state of the input field:
 
 > ### Sample Code:  
 > ```
diff --git a/docs/06_SAP_Fiori_Elements/adding-dynamic-side-content-to-object-page-sections-8e01a46.md b/docs/06_SAP_Fiori_Elements/adding-dynamic-side-content-to-object-page-sections-8e01a46.md
index f4812ce5..fc70381d 100644
--- a/docs/06_SAP_Fiori_Elements/adding-dynamic-side-content-to-object-page-sections-8e01a46.md
+++ b/docs/06_SAP_Fiori_Elements/adding-dynamic-side-content-to-object-page-sections-8e01a46.md
@@ -137,14 +137,14 @@ You define the side content in the manifest as follows:
 >                            "sections": {
 >                               "<section-key>": {
 >                                  "sideContent": {
->                                     "template": "SalesOrder.custom.CustomSideContent"
+>                                     "template": "SalesOrder.ext.CustomSideContent"
 >                                  }
 >                               },
 >                               "<section-key>": {
 >                                  "subSections": {
 >                                     "<subSection-key>": {
 >                                        "sideContent": {
->                                           "template": "SalesOrder.custom.CustomSideContent",
+>                                           "template": "SalesOrder.ext.CustomSideContent",
 >                                           "equalSplit": true
 >                                        }
 >                                     }
@@ -278,7 +278,7 @@ If no value for the parameter is provided, the API toggles the display.
 >                            "_Item/@com.sap.vocabularies.UI.v1.LineItem": {
 >                               "actions": {
 >                                  "CustomActionToggleSideContent": {
->                                  "press": "Namespace.custom.CustomSectionSideContent.toggleSideContent",
+>                                  "press": "Namespace.ext.CustomSectionSideContent.toggleSideContent",
 >                                  "text": "Show/Hide Side Content",
 >                                  "enabled": true,
 >                                  "visible": true 
@@ -298,7 +298,7 @@ If no value for the parameter is provided, the API toggles the display.
 For more information about defining an action, see [Adding Custom Actions Using Extension Points](adding-custom-actions-using-extension-points-7619517.md).
 
 > ### Sample Code:  
-> webapp/custom/customSectionSideContent.js
+> webapp/ext/customSectionSideContent.js
 > 
 > ```
 > sap.ui.define([], function() {
diff --git a/docs/06_SAP_Fiori_Elements/creating-an-extension-to-modify-properties-in-the-navigation-context-199a496.md b/docs/06_SAP_Fiori_Elements/creating-an-extension-to-modify-properties-in-the-navigation-context-199a496.md
index c0c6a6d0..71ec9d50 100644
--- a/docs/06_SAP_Fiori_Elements/creating-an-extension-to-modify-properties-in-the-navigation-context-199a496.md
+++ b/docs/06_SAP_Fiori_Elements/creating-an-extension-to-modify-properties-in-the-navigation-context-199a496.md
@@ -110,10 +110,10 @@ The modification \(add/remove/change\) is achieved via the `adaptNavigationConte
     >         "extensions": {
     >             "sap.ui.controllerExtensions": {
     >                 "sap.fe.templates.ListReport.ListReportController": {
-    >                     "controllerName": "SalesOrder.custom.LRExtend"
+    >                     "controllerName": "SalesOrder.ext.LRExtend"
     >                 },
     >                 "sap.fe.templates.ObjectPage.ObjectPageController": {
-    >                     "controllerName": "SalesOrder.custom.OPExtend"
+    >                     "controllerName": "SalesOrder.ext.OPExtend"
     >                 }
     >             }
     >         }
diff --git a/docs/06_SAP_Fiori_Elements/enabling-actions-added-using-extension-points-dd78aca.md b/docs/06_SAP_Fiori_Elements/enabling-actions-added-using-extension-points-dd78aca.md
index b67c5242..1f947326 100644
--- a/docs/06_SAP_Fiori_Elements/enabling-actions-added-using-extension-points-dd78aca.md
+++ b/docs/06_SAP_Fiori_Elements/enabling-actions-added-using-extension-points-dd78aca.md
@@ -149,7 +149,7 @@ To enable an action in the list report only upon selection of one row in the tab
 
 > ### Sample Code:  
 > ```
-> "enabled": "SalesOrder.custom.CustomActions.enabledForCompletedOnly"
+> "enabled": "SalesOrder.ext.CustomActions.enabledForCompletedOnly"
 > ```
 
 > ### Sample Code:  
@@ -295,7 +295,7 @@ You can also control the visibility of actions via a custom handler \(this is si
 >                                     "actions": {
 >                                         "<ActionName>": {
 >                                             "DataFieldForAction::com.c_salesordermanage_sd.ArchiveSalesOrder": {
->                                             "visible": "SalesOrder.custom.CustomActions.visibleForCompletedOnly"
+>                                             "visible": "SalesOrder.ext.CustomActions.visibleForCompletedOnly"
 >                                             }
 >                                         }
 >                                     }
diff --git a/docs/06_SAP_Fiori_Elements/example-enable-internal-navigation-to-different-detail-page-75002b3.md b/docs/06_SAP_Fiori_Elements/example-enable-internal-navigation-to-different-detail-page-75002b3.md
index 78e197ce..5fd75e7e 100644
--- a/docs/06_SAP_Fiori_Elements/example-enable-internal-navigation-to-different-detail-page-75002b3.md
+++ b/docs/06_SAP_Fiori_Elements/example-enable-internal-navigation-to-different-detail-page-75002b3.md
@@ -140,7 +140,7 @@ Application developers can then add the extension code to call the route defined
 >     Log
 > ) {
 >     "use strict";
->     return ControllerExtension.extend("SalesOrder.custom.LRExtend", {
+>     return ControllerExtension.extend("SalesOrder.ext.LRExtend", {
 >         // this section allows to extend lifecycle hooks or override public methods of the base controller
 >         override: {
 >             ......
@@ -192,7 +192,7 @@ In addition, here's an example for the object page:
 >     ],
 >     function(ControllerExtension, Dialog, DialogType, Text, Button, ButtonType, MessageToast, Log) {
 >         "use strict";
->         return ControllerExtension.extend("SalesOrder.custom.OPExtend", {
+>         return ControllerExtension.extend("SalesOrder.ext.OPExtend", {
 >             // this section allows to extend lifecycle hooks or override public methods of the base controller
 >             override: {
 >                 ......
diff --git a/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-in-the-list-report-a12ad60.md b/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-in-the-list-report-a12ad60.md
index c5ccaa38..d584e92f 100644
--- a/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-in-the-list-report-a12ad60.md
+++ b/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-in-the-list-report-a12ad60.md
@@ -160,10 +160,10 @@ Application developers can selectively change the target when chevron navigation
     >         "extensions": {
     >             "sap.ui.controllerExtensions": {
     >                 "sap.fe.templates.ListReport.ListReportController": {
-    >                     "controllerName": "SalesOrder.custom.LRExtend"
+    >                     "controllerName": "SalesOrder.ext.LRExtend"
     >                 },
     >                 "sap.fe.templates.ObjectPage.ObjectPageController": {
-    >                     "controllerName": "SalesOrder.custom.OPExtend"
+    >                     "controllerName": "SalesOrder.ext.OPExtend"
     >                 }
     >             }
     >         }
diff --git a/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-on-the-object-page-b20dc7a.md b/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-on-the-object-page-b20dc7a.md
index cb97cd57..a5ff7b18 100644
--- a/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-on-the-object-page-b20dc7a.md
+++ b/docs/06_SAP_Fiori_Elements/example-replacing-standard-navigation-in-a-responsive-table-on-the-object-page-b20dc7a.md
@@ -154,10 +154,10 @@ Application developers can selectively change the target when chevron navigation
     >         "extensions": {
     >             "sap.ui.controllerExtensions": {
     >                 "sap.fe.templates.ListReport.ListReportController": {
-    >                     "controllerName": "SalesOrder.custom.LRExtend"
+    >                     "controllerName": "SalesOrder.ext.LRExtend"
     >                 },
     >                 "sap.fe.templates.ObjectPage.ObjectPageController": {
-    >                     "controllerName": "SalesOrder.custom.OPExtend"
+    >                     "controllerName": "SalesOrder.ext.OPExtend"
     >                 }
     >             }
     >         }
diff --git a/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md b/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md
index 7f5aa87e..17cf5a4d 100644
--- a/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md
+++ b/docs/06_SAP_Fiori_Elements/extending-sap-fiori-elements-based-apps-358cf25.md
@@ -28,10 +28,10 @@ The most specific one wins. In the sample code above, this means for the `SalesO
 > 
 > ```
 > "sap.fe.templates.ObjectPage.ObjectPageController": {
->     "controllerName": "SalesOrder.custom.OPExtend"
+>     "controllerName": "SalesOrder.ext.OPExtend"
 > },
 > "sap.fe.templates.ObjectPage.ObjectPageController#SalesOrder::SalesOrderManageObjectPage": {
->     "controllerName": "SalesOrder.custom.SalesOrderOPExtend"
+>     "controllerName": "SalesOrder.ext.SalesOrderOPExtend"
 > }
 > ```
 
diff --git a/docs/06_SAP_Fiori_Elements/extension-points-for-forms-on-the-object-page-4e49753.md b/docs/06_SAP_Fiori_Elements/extension-points-for-forms-on-the-object-page-4e49753.md
index 9e0ebaec..9ec41a88 100644
--- a/docs/06_SAP_Fiori_Elements/extension-points-for-forms-on-the-object-page-4e49753.md
+++ b/docs/06_SAP_Fiori_Elements/extension-points-for-forms-on-the-object-page-4e49753.md
@@ -91,7 +91,7 @@ The form containing additional custom fields can look like this:
     >                             "@com.sap.vocabularies.UI.v1.FieldGroup": {
     >                                 "fields": {
     >                                     "customFormElementAnchor": {
-    >                                         "template": "ObjectPageStructure.custom.CustomField",
+    >                                         "template": "ObjectPageStructure.ext.CustomField",
     >                                          "label": "{i18n>myFieldLabel1}",
     >                                          "position": {
     >                                              "placement": "After",
@@ -99,7 +99,7 @@ The form containing additional custom fields can look like this:
     >                                          }
     >                                      },
     >                                      "customFormElementAnchor2": {
-    >                                          "template": "ObjectPageStructure.custom.CustomField",
+    >                                          "template": "ObjectPageStructure.ext.CustomField",
     >                                          "label": "{i18n>myFieldLabel2}",
     >                                          "position": {
     >                                              "placement": "After",
diff --git a/docs/06_SAP_Fiori_Elements/extension-points-for-object-page-header-facets-61cf0ee.md b/docs/06_SAP_Fiori_Elements/extension-points-for-object-page-header-facets-61cf0ee.md
index 6c8ee9e7..1856758e 100644
--- a/docs/06_SAP_Fiori_Elements/extension-points-for-object-page-header-facets-61cf0ee.md
+++ b/docs/06_SAP_Fiori_Elements/extension-points-for-object-page-header-facets-61cf0ee.md
@@ -162,7 +162,7 @@ To define a header facet on UI level – you do this if you want to add a custom
 >                                 "header": {
 >                                     "facets": {
 >                                         "CustomHeaderFacet1": {
->                                             "template": "SalesOrder.custom.CustomHeaderFacetColumnChart",
+>                                             "template": "SalesOrder.ext.CustomHeaderFacetColumnChart",
 >                                             "stashed": false,
 >                                             "visible": "{= %{OverallSDProcessStatus} === 'C'}",
 >                                             "position": {
@@ -174,8 +174,8 @@ To define a header facet on UI level – you do this if you want to add a custom
 >                                             }
 >                                         },
 >                                         "CustomHeaderFacet2": {
->                                             "template": "SalesOrder.custom.CustomHeaderFacetDataPoint",
->                                             "templateEdit": "SalesOrder.custom.CustomHeaderFacetDataPointEdit",
+>                                             "template": "SalesOrder.ext.CustomHeaderFacetDataPoint",
+>                                             "templateEdit": "SalesOrder.ext.CustomHeaderFacetDataPointEdit",
 >                                             "title": "{i18n>customHeaderFacet2-CustomDataPoint}",
 >                                             "subTitle": "{i18n>customHeaderFacet2-CarRental}",
 >                                             "requestGroupId": "LongRunners",
@@ -221,7 +221,7 @@ To define a header facet on UI level – you do this if you want to add a custom
 >                                 "@com.sap.vocabularies.UI.v1.HeaderFacets": {
 >                                     "facets": {
 >                                         "CustomHeaderFacet2": {
->                                             "template": "SalesOrder.custom.CustomHeaderFacetOverwritten",
+>                                             "template": "SalesOrder.ext.CustomHeaderFacetOverwritten",
 >                                             "title": "Custom Error",
 >                                             "subTitle": "Should never appear!",
 >                                             "stashed": false,
@@ -231,8 +231,8 @@ To define a header facet on UI level – you do this if you want to add a custom
 >                                             }
 >                                         },
 >                                         "CustomHeaderFacet3": {
->                                             "template": "SalesOrder.custom.CustomHeaderFacetHarveyBall",
->                                             "templateEdit": "SalesOrder.custom.CustomHeaderFacetHarveyBallEdit",
+>                                             "template": "SalesOrder.ext.CustomHeaderFacetHarveyBall",
+>                                             "templateEdit": "SalesOrder.ext.CustomHeaderFacetHarveyBallEdit",
 >                                             "title": "{i18n>customHeaderFacet2-CustomProgress}",
 >                                             "stashed": false,
 >                                             "position": {
@@ -252,7 +252,7 @@ To define a header facet on UI level – you do this if you want to add a custom
 > }
 > ```
 
-In this example, the second header facet with the key `CustomHeaderFacet2` occurs twice: once in the content-based configuration and a second time in the annotation-based configuration. Since the 1st configuration has a higher priority, the second entry will be skipped at runtime and you won't see the fragment `SalesOrder.custom.CustomHeaderFacetOverwritten` as a header facet.
+In this example, the second header facet with the key `CustomHeaderFacet2` occurs twice: once in the content-based configuration and a second time in the annotation-based configuration. Since the 1st configuration has a higher priority, the second entry will be skipped at runtime and you won't see the fragment `SalesOrder.ext.CustomHeaderFacetOverwritten` as a header facet.
 
 **Settings for Custom Header Facets**
 
@@ -677,7 +677,7 @@ To define a field in a header field – you do this if you want to add a custom
 >                            "fields": {
 >                               "CustomField1": {
 >                                  "label": "{i18n>ObjectPageHeaderFacetFieldLabel1}",
->                                  "template": "ManageItems.custom.CustomHeaderFacetFieldGroupForm",
+>                                  "template": "ManageItems.ext.CustomHeaderFacetFieldGroupForm",
 >                                  "position": {
 >                                     "placement": "Before",
 >                                     "anchor": "DataField::headerDate"
diff --git a/docs/06_SAP_Fiori_Elements/extension-points-for-sections-on-the-object-page-92ad996.md b/docs/06_SAP_Fiori_Elements/extension-points-for-sections-on-the-object-page-92ad996.md
index 861c4cd0..f60d9bc8 100644
--- a/docs/06_SAP_Fiori_Elements/extension-points-for-sections-on-the-object-page-92ad996.md
+++ b/docs/06_SAP_Fiori_Elements/extension-points-for-sections-on-the-object-page-92ad996.md
@@ -125,7 +125,7 @@ To define a section on UI level - you do this if you want to add a custom look a
 >                         "body": {
 >                            "sections": {
 >                               "customSection": {
->                                  "template": "SalesOrder.custom.CustomSection",
+>                                  "template": "SalesOrder.ext.CustomSection",
 >                                  "title": "{i18n>customSection}",
 >                                  "position": {
 >                                     "placement": "Before",
@@ -137,11 +137,11 @@ To define a section on UI level - you do this if you want to add a custom look a
 >                                  "subSections": {
 >                                      "firstSubSectionKey": {
 >                                          "title": "First Subsection",
->                                          "template": "SalesOrder.custom.CustomFieldForm"
+>                                          "template": "SalesOrder.ext.CustomFieldForm"
 >                                      },
 >                                      "secondSubSectionKey": {
 >                                          "title": "Second Subsection",
->                                          "template": "SalesOrder.custom.CustomFieldForm2",
+>                                          "template": "SalesOrder.ext.CustomFieldForm2",
 >                                          "position": {
 >                                              "placement": "After",
 >                                              "anchor": "firstSubSectionKey"
diff --git a/docs/06_SAP_Fiori_Elements/extension-points-for-subsections-on-the-object-page-ce8d468.md b/docs/06_SAP_Fiori_Elements/extension-points-for-subsections-on-the-object-page-ce8d468.md
index 0d1164bf..1fe935e0 100644
--- a/docs/06_SAP_Fiori_Elements/extension-points-for-subsections-on-the-object-page-ce8d468.md
+++ b/docs/06_SAP_Fiori_Elements/extension-points-for-subsections-on-the-object-page-ce8d468.md
@@ -119,7 +119,7 @@ For more information, see [Extension Points for Sections on the Object Page](ext
 > 											"subSections": {
 > 												"customSubSection": {
 > 													"type": "XMLFragment",
-> 													"name": "SalesOrder.custom.CustomSubSection",
+> 													"name": "SalesOrder.ext.CustomSubSection",
 > 													"title": "{i18n>customSubSection}",
 > 													"position": {
 > 														"placement": "After",
diff --git a/docs/06_SAP_Fiori_Elements/extension-points-for-tables-d525522.md b/docs/06_SAP_Fiori_Elements/extension-points-for-tables-d525522.md
index 8250a390..76d7ea7d 100644
--- a/docs/06_SAP_Fiori_Elements/extension-points-for-tables-d525522.md
+++ b/docs/06_SAP_Fiori_Elements/extension-points-for-tables-d525522.md
@@ -322,7 +322,7 @@ The table containing additional custom columns can look like this:
     > 
     > ```
     > <core:FragmentDefinition xmlns:core="sap.ui.core" xmlns="sap.m" xmlns:l="sap.ui.layout">
-    > 	<l:VerticalLayout core:require="{handler: 'SalesOrder/custom/CustomColumn'}">
+    > 	<l:VerticalLayout core:require="{handler: 'SalesOrder/ext/CustomColumn'}">
     > 		<Button text="Custom Button" press="handler.buttonPressed" />
     > 	</l:VerticalLayout>
     > </core:FragmentDefinition>
@@ -353,7 +353,7 @@ The table containing additional custom columns can look like this:
     >                                                 "placement": "After",
     >                                                 "anchor": "DataFieldForAnnotation::FieldGroup::multipleActionFields"
     >                                             },
-    >                                             "template": "SalesOrder.custom.CustomColumnButton",
+    >                                             "template": "SalesOrder.ext.CustomColumnButton",
     >                                             "availability": "Default",
     >                                             "properties": [
     >                                                 "ID",
@@ -376,7 +376,7 @@ The table containing additional custom columns can look like this:
     >                                     "columns": {
     >                                         "CustomColumnOnObjectPage": {
     >                                             "header": "AnotherColumnLabel",
-    >                                             "template": "SalesOrder.custom.CustomColumnButton",
+    >                                             "template": "SalesOrder.ext.CustomColumnButton",
     >                                             "availability": "Adaption"
     >                                         }
     >                                     }
diff --git a/docs/06_SAP_Fiori_Elements/extension-points-for-views-in-the-list-report-eb37203.md b/docs/06_SAP_Fiori_Elements/extension-points-for-views-in-the-list-report-eb37203.md
index 8b52deda..edaa3a78 100644
--- a/docs/06_SAP_Fiori_Elements/extension-points-for-views-in-the-list-report-eb37203.md
+++ b/docs/06_SAP_Fiori_Elements/extension-points-for-views-in-the-list-report-eb37203.md
@@ -49,12 +49,12 @@ To define a custom view, the path configuration for the custom view in the manif
 >                     {
 >                         "key": "tab2",
 >                         "label": "Custom View with Table",
->                         "template": "BusinessPartners.custom.CustomViewTable"
+>                         "template": "BusinessPartners.ext.CustomViewTable"
 >                     },
 >                     {
 >                         "key": "tab3",
 >                         "label": "{i18n>LRCustomViewWithButton}",
->                         "template": "BusinessPartners.custom.CustomViewWithButton"
+>                         "template": "BusinessPartners.ext.CustomViewWithButton"
 >                     }
 >                 ],
 >                 "showCounts": true
@@ -247,7 +247,7 @@ In the following sample code, a simple button has been added inside a panel to a
 >         headerText="Business Partners"
 >         class="sapUiResponsiveMargin"
 >         width="auto"
->         core:require="{handler: 'BusinessPartners/custom/CustomButton'}"
+>         core:require="{handler: 'BusinessPartners/ext/CustomButton'}"
 >     >
 >         <content>
 >             <Button text="IBN" id="customButton1" class="sapUiSmallMarginEnd" press="handler.onPress" />
@@ -295,7 +295,7 @@ For app developers who want a standard filtering behavior along with other annot
 >         "extensions": {
 >             "sap.ui.controllerExtensions": {
 >                 "sap.fe.templates.ListReport.ListReportController": {
->                     "controllerName": "SalesOrder.custom.LRExtend"
+>                     "controllerName": "SalesOrder.ext.LRExtend"
 >                 }
 >             }
 >         }
@@ -316,7 +316,7 @@ In the following sample code, the binding information is updated with filter con
 > ```
 > sap.ui.define(["sap/ui/core/mvc/ControllerExtension", "sap/ui/model/Filter"], function(ControllerExtension, Filter) {
 >     "use strict";
->     return ControllerExtension.extend("BusinessPartners.custom.LRExtend", {
+>     return ControllerExtension.extend("BusinessPartners.ext.LRExtend", {
 >         override: {
 >             onViewNeedsRefresh: function(mParameters) {
 >                 var oFilterInfo = mParameters.filterConditions;
diff --git a/docs/06_SAP_Fiori_Elements/refresh-data-set-for-back-navigation-when-sap-keep-alive-is-set-to-true-f1c2704.md b/docs/06_SAP_Fiori_Elements/refresh-data-set-for-back-navigation-when-sap-keep-alive-is-set-to-true-f1c2704.md
index 8dda0689..9362d296 100644
--- a/docs/06_SAP_Fiori_Elements/refresh-data-set-for-back-navigation-when-sap-keep-alive-is-set-to-true-f1c2704.md
+++ b/docs/06_SAP_Fiori_Elements/refresh-data-set-for-back-navigation-when-sap-keep-alive-is-set-to-true-f1c2704.md
@@ -42,7 +42,7 @@ SAP Fiori elements provides two extension methods for applications that run in `
 > List report extension implementing `sap-keep-alive` extension APIs
 > 
 > ```
-> return ControllerExtension.extend("SalesOrder.custom.LRExtend", {
+> return ControllerExtension.extend("SalesOrder.ext.LRExtend", {
 >     // this section allows to extend lifecycle hooks or override public methods of the base controller
 >     override: {
 >         viewState: {
diff --git a/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md b/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md
index c95c4895..eaf90320 100644
--- a/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md
+++ b/docs/06_SAP_Fiori_Elements/share-functionality-022bf0d.md
@@ -65,7 +65,7 @@ Make the following changes in the `manifest.json` file:
 >             "extensions": {
 >                 "sap.ui.controllerExtensions": {
 >                     "sap.fe.templates.ObjectPage.ObjectPageController": {
->                         "controllerName": "SalesOrder.custom.OPExtend"
+>                         "controllerName": "SalesOrder.ext.OPExtend"
 >                     }
 >                 }
 >             }
@@ -78,7 +78,7 @@ Make the following changes in the `OPExtend.controller.js` file:
 > ```
 > sap.ui.define(["sap/ui/core/mvc/ControllerExtension"], function(ControllerExtension) {
 >         "use strict";
->         return ControllerExtension.extend("SalesOrder.custom.OPExtend", {
+>         return ControllerExtension.extend("SalesOrder.ext.OPExtend", {
 >             // this section allows to extend lifecycle hooks or override public methods of the base controller
 >             override: {
 >                onInit: function() {},

From f1c105ef4e8811b288be7ce8b0e5e4b8975d7420 Mon Sep 17 00:00:00 2001
From: Nicolas Lunet <nicolas.lunet@sap.com>
Date: Tue, 25 Oct 2022 10:28:04 +0200
Subject: [PATCH 2/2] fix lint issue

---
 .../adding-a-section-to-an-object-page-a357047.md             | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md b/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
index 8438d6c3..c4d3d860 100644
--- a/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
+++ b/docs/06_SAP_Fiori_Elements/adding-a-section-to-an-object-page-a357047.md
@@ -45,7 +45,7 @@ In the SAP Web IDE, open the folder structure of the Manage Products project and
 
 
 
-### Step 2: Add Section Title to the i18n File
+### Step 2: Add Section Title to the `i18n` File
 
 To make the section title translatable, add the text to the `i18n` file as follows:
 
@@ -181,7 +181,7 @@ In the editor of your choice, open the folder structure of the project where you
 
 
 
-### Step 2: Add Section Title to the i18n File
+### Step 2: Add Section Title to the `i18n` File
 
 To make the section title translatable, add the text to the `i18n` file as follows: