Apply new suggestions

Author: GitHub Actions

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

@@ -16,7 +16,7 @@ include::../modules/dynamic-plugins/con-understand-why-wiring-is-required.adoc[l
 include::../modules/dynamic-plugins/con-troubleshoot-why-a-dynamically-loaded-plugin-is-not-visible.adoc[leveloffset=+2]
 
 // When to perform frontend wiring
-include::../modules/dynamic-plugins/con-identify-and-register-plugin-features-for-application-use.adoc[leveloffset=+2]
+include::../modules/dynamic-plugins/con-dynamic-front-end-plugins-for-application-use.adoc[leveloffset=+2]
 
 // Extending the internal icon catalog
 include::../modules/dynamic-plugins/proc-extending-internal-icon-catalog.adoc[leveloffset=+1]

…plugin-features-for-application-use.adoc …ont-end-plugins-for-application-use.adocmodules/dynamic-plugins/con-identify-and-register-plugin-features-for-application-use.adoc renamed to modules/dynamic-plugins/con-dynamic-front-end-plugins-for-application-use.adoc modules/dynamic-plugins/con-identify-and-register-plugin-features-for-application-use.adoc renamed to modules/dynamic-plugins/con-dynamic-front-end-plugins-for-application-use.adoc

@@ -1,49 +1,49 @@
 :_mod-docs-content-type: CONCEPT
-[id="con-identify-and-register-plugin-features-for-application-use_{context}"]
+[id="con-dynamic-front-end-plugins-for-application-use_{context}"]
 
-= Identify and register plugin features for application use
+= Dynamic front-end plugins for application use
 
-Front-end wiring must be performed whenever a dynamic front-end plugin exports a feature that needs to be integrated into the main {product-custom-resource-type} application UI.
+Front-end wiring must be performed whenever a dynamic front-end plugin exports a feature for integration into the main {product-custom-resource-type} application UI.
 
 Wiring is specifically required for, but not limited to, the following scenarios:
 
 [cols="1,1,2"]
 |===
 |Scenario|Wiring configuration|Description
 
-|Enabling new pages/Routes
+|{installing-and-viewing-plugins-book-link}#proc-defining-dynamic-routes-for-new-plugin-pages.adoc_assembly-front-end-plugin-wiring[Enabling new pages/Routes]
 |`dynamicRoutes`
 |When adding a full new page and route to the application (for example, `/my-plugin`).
 
-|Extending existing pages/UI
+|{installing-and-viewing-plugins-book-link}#proc-using-mount-points.adoc_assembly-front-end-plugin-wiring[Extending existing pages/UI]
 |`mountPoints`
 |When injecting custom widgets, cards, listeners, or providers into existing pages (for example, the Catalog entity page).
 
-|Customizing sidebar navigation
+|{installing-and-viewing-plugins-book-link}#proc-defining-dynamic-routes-for-new-plugin-pages.adoc_assembly-front-end-plugin-wiring[Customizing sidebar navigation]
 |`dynamicRoutes.menuItem`, `menuItems`
 |When adding a new entry to the main sidebar or customizing its order/nesting.
 
-|Integrating custom APIs
+|{installing-and-viewing-plugins-book-link}#proc-provide-additional-utility-apis.adoc_assembly-front-end-plugin-wiring[Integrating custom APIs]
 |`apiFactories`
 |When a plugin provides a custom utility API implementation or overrides an existing one.
 
-|Extending entity tabs
+|{installing-and-viewing-plugins-book-link}#proc-customizing-and-extending-entity-tabs.adoc_assembly-front-end-plugin-wiring[Extending entity tabs]
 |`entityTabs`
 |When adding a new tab to the Catalog entity view or customizing an existing one.
 
-|Binding routes
+|{installing-and-viewing-plugins-book-link}#proc-binding-to-existing-plugins.adoc_assembly-front-end-plugin-wiring[Binding routes]
 |`routeBindings`
 |When linking a route in one plugin to an external route defined by another plugin.
 
-|Adding icons/Theming
+|{installing-and-viewing-plugins-book-link}#proc-extending-internal-icon-catalog.adoc_assembly-front-end-plugin-wiring[Adding icons/Theming]
 |`appIcons`, `themes`
 |When adding custom icons to the application catalog or defining a new {product-custom-resource-type} theme.
 
-|Scaffolder/TechDocs extensions
+|{installing-and-viewing-plugins-book-link}#con-providing-custom-scaffolder-field-extensions.adoc_assembly-front-end-plugin-wiring[Scaffolder/TechDocs extensions]
 |`scaffolderFieldExtensions`, `techdocsAddons`
 |When exposing custom field extensions for the Scaffolder or new Addons for TechDocs.
 
-|Translation resources
+|{installing-and-viewing-plugins-book-link}#proc-extensions-enabling-plugins-installation_rhdh-extensions-plugins[Translation resources]
 |`translationResources`
 |When providing new translation files or overriding default translations of a plugin.
 |===

modules/dynamic-plugins/con-troubleshoot-why-a-dynamically-loaded-plugin-is-not-visible.adoc

@@ -7,7 +7,12 @@ If you skip front-end wiring, the plugin is discovered but not loaded into the a
 
 You can expect the following behavior when you skip front-end wiring:
 
-Functionality is disabled:: The Backstage application does not know how to integrate the plugin exports.
-Invisible components:: New pages, sidebar links, or custom cards are not rendered.
-Unregistered APIs:: Custom utility APIs or API overrides provided by the plugin fail to register in the application API system, causing plugins or components to fail.
-Unused assets:: Icons, translations, and themes are not registered or made available for use.
+Disabled functionality:: The {product-custom-resource-type} application is unable to integrate or use the plugin exports.
+Invisible components:: New pages, sidebar links, or custom cards do not render in the application UI.
+Unregistered APIs:: Custom utility APIs or API overrides provided by the plugin are not registered in the application API system, potentially causing plugins or components to fail.
+Unused assets:: Icons, translations, and themes are not registered or made available for use.
+
+[TIP]
+====
+Sometimes a plugin might not be visible even if there is front-end wiring, which indicates it is misconfigured. To troubleshoot this, check the *Console* tab in the _Developer Tools_ of your browser for specific error messages or warnings.
+====