Apply new suggestions

Author: GitHub Actions

assemblies/dynamic-plugins/assembly-front-end-plugin-wiring.adoc

@@ -10,7 +10,7 @@ You can configure front-end plugins to customize icons, integrate components at
 include::../modules/dynamic-plugins/con-frontend-dynamic-plugin-wiring.adoc[leveloffset=+1]
 
 // Understand frontend wiring
-include::../modules/dynamic-plugins/con-understand-why-wiring-is-required-for-plugin-deployment.adoc[leveloffset=+2]
+include::../modules/dynamic-plugins/con-understand-why-wiring-is-required.adoc[leveloffset=+2]
 
 // When you skip frontend wiring
 include::../modules/dynamic-plugins/con-troubleshoot-why-a-dynamically-loaded-plugin-is-not-visible.adoc[leveloffset=+2]

modules/dynamic-plugins/con-identify-and-register-plugin-features-for-application-use.adoc

@@ -79,7 +79,7 @@ The application follows these steps when it loads:
 
 . It parses the `dynamic-plugins-config.yaml`.
 . It uses the `<plugin_path_or_url>` to download the plugin bundle using the dynamic loading mechanism.
-. If the plugin exports the plugin object, the application adds this to the list of plugins provided to the Backstage `createApp` API, registering the plugin properly with the Backstage front-end application.
+. If the package exports the plugin object, the application adds it to the list provided to the {product-custom-resource-type} `createApp` API, registering the plugin properly with the front-end application.
 . It uses the configuration block (`dynamicRoutes`, `menuItem`) to:
 * Add an entry to the internal router mapping `/my-new-page` to the `FooPluginPage` component.
 * Construct and render a new sidebar item labeled _My Custom Page_, pointing to the `/my-new-page` route.

modules/dynamic-plugins/con-understand-why-wiring-is-required-for-plugin-deployment.adoc

@@ -0,0 +1,16 @@
+:_mod-docs-content-type: CONCEPT
+[id="con-understand-why-wiring-is-required_{context}"]
+
+= Understand why wiring is required
+
+Dynamic front-end plugins load their code at runtime, but the {product-short} application does not automatically know where the components of a plugin must appear in the user interface (UI).
+
+Front-end wiring provides the metadata and instructions that bridge this gap by telling the application the following:
+
+* {installing-and-viewing-plugins-book-link}#proc-defining-dynamic-routes-for-new-plugin-pages.adoc_assembly-front-end-plugin-wiring[Add new pages and routes to the main application]. (using `dynamicRoutes`)
+* {installing-and-viewing-plugins-book-link}#proc-using-mount-points.adoc_assembly-front-end-plugin-wiring[Inject custom components into existing UI pages]. (using `mountPoints`)
+* {installing-and-viewing-plugins-book-link}#proc-extending-internal-icon-catalog.adoc_assembly-front-end-plugin-wiring[Configure application-wide customizations, such as new icons or themes]. (using `appIcons`)
+* {installing-and-viewing-plugins-book-link}#proc-customizing-sidebar-menu-items.adoc_assembly-front-end-plugin-wiring[Add new menu items]. (using `menuItems`)
+* {installing-and-viewing-plugins-book-link}#proc-binding-to-existing-plugins.adoc_assembly-front-end-plugin-wiring[Bind to existing plugins]. (using `routeBindings`)
+
+Wiring configuration, typically located in `{my-app-config-file}` or `dynamic-plugins-config.yaml`, provides the application with the metadata (including the component names, paths, and integration points) needed to render and use the plugin features.

modules/dynamic-plugins/con-understand-why-wiring-is-required.adoc

@@ -7,6 +7,3 @@ include::artifacts/attributes.adoc[]
 :abstract: As a platform engineer, you can configure dynamic plugins in {product} ({product-very-short}) to access your development infrastructure or software development tools.
 
 include::assemblies/dynamic-plugins/assembly-configuring-rhdh-plugins.adoc[]
-
-// frontend plugin wiring
-include::assemblies/dynamic-plugins/assembly-front-end-plugin-wiring.adoc[leveloffset=+1]

titles/plugins-rhdh-configure/master.adoc

@@ -32,5 +32,8 @@ include::assemblies/dynamic-plugins/assembly-extensions-plugins.adoc[leveloffset
 // Troubleshooting plugins
 include::modules/dynamic-plugins/proc-plugins-troubleshooting.adoc[leveloffset=+1]
 
+// frontend plugin wiring
+include::assemblies/dynamic-plugins/assembly-front-end-plugin-wiring.adoc[leveloffset=+1]
+
 // Plugin indicators and support types
 include::assemblies/dynamic-plugins/assembly-plugin-indicators-and-support-types.adoc[leveloffset=+1]