Add frontend plugn wiring section

Author: GitHub Actions

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

@@ -36,6 +36,12 @@ include::../modules/dynamic-plugins/proc-adding-application-providers.adoc[level
 // Customizing and extending entity tabs
 include::../modules/dynamic-plugins/proc-customizing-and-extending-entity-tabs.adoc[leveloffset=+1]
 
+// SignIn page
+include::../modules/dynamic-plugins/con-using-custom-signinpage-component.adoc[leveloffset=+1]
+
+// custom scaffolder extension
+include::../modules/dynamic-plugins/con-providing-custom-scaffolder-field-extensions.adoc[leveloffset=+1]
+
 // Provide additional Utility APIs
 include::../modules/dynamic-plugins/proc-provide-additional-utility-apis.adoc[leveloffset=+1]
 

modules/dynamic-plugins/con-providing-custom-scaffolder-field-extensions.adoc

@@ -0,0 +1,29 @@
+[id="con-providing-custom-scaffolder-field-extensions"]
+
+= Providing custom Scaffolder field extensions
+
+The Scaffolder component in {product} ({product-very-short}) enables users to create software components using templates through a guided wizard. You can extend the functionality of the Scaffolder by providing custom form fields as dynamic plugins using the `scaffolderFieldExtensions` configuration.
+
+Custom field extensions allow you to add specialized form fields that capture domain-specific data during the scaffolding process, such as environment selectors, input validations, or repository checks.
+
+When you configure custom scaffolder field extensions:
+
+* The dynamic plugin exposes the field extension component using `createScaffolderFieldExtension`.
+* Each field extension requires a unique `importName` for registration.
+* Multiple field extensions can be registered by listing each in the configuration.
+
+[source,yaml]
+----
+dynamicPlugins:
+  frontend:
+    my-plugin: # <1>
+      scaffolderFieldExtensions:
+        - importName: MyNewFieldExtension # <2>
+----
+<1> Specify the plugin package name.
+<2> The `importName` references the exported scaffolder field extension component from your plugin.
+
+[NOTE]
+====
+The `module` field is optional and specifies which set of assets to access within the plugin. By default, the system uses the `PluginRoot` module, consistent with the `scalprum.exposedModules` key in your plugin's `package.json`.
+====

modules/dynamic-plugins/con-using-custom-signinpage-component.adoc

@@ -0,0 +1,27 @@
+[id="con-using-custom-signinpage-component"]
+= Using a custom SignInPage component
+
+In {product} ({product-very-short}), the `SignInPage` component manages the application's authentication flow. The `SignInPage` connects one or more authentication providers to the sign-in process. By default, {product-short} uses a static `SignInPage` that supports all built-in authentication providers.
+
+When you configure a custom `SignInPage`:
+
+* The system loads the specified `importName` component from your dynamic plugin.
+* The component returns a configured `SignInPage` that connects the desired authentication provider factories.
+* Only one `signInPage` can be specified for the application at a time.
+
+[source,yaml]
+----
+dynamicPlugins:
+  frontend:
+    my-plugin: # <1>
+      signInPage:
+        importName: CustomSignInPage
+----
+<1> Specify the plugin package name.
+
+[NOTE]
+====
+The `package_name` under `dynamicPlugins.frontend` must match the `scalprum.name` value in your plugin's `package.json` to ensure the dynamic plugin loads correctly during runtime.
+
+The `module` field is optional and allows specifying which set of assets should be accessed within the dynamic plugin. By default, the system uses the `PluginRoot` module.
+====