Merge branch 'main' into RHDHBUGS-2557

Author: themr0c

.gitignore

@@ -14,4 +14,4 @@ catalog-info.yaml
 .claude/settings.json.backup
 build-report.json
 .lycheecache
-build/.cache/
+build/.cache/

artifacts/attributes.adoc

@@ -15,9 +15,7 @@
 :product-cli: rhdh-cli
 :product-local: Red Hat Developer Hub Local
 :product-local-very-short: RHDH Local
-:product-version: 1.9
-// TODO change to 1.10 after creating the release-1.10 branch
-// :product-version: 1.10
+:product-version: 1.10
 :product-bundle-version: 1.10.0
 :product-chart-version: 1.10.0
 :product-backstage-version: 1.45.3

assemblies/configure_customizing-rhdh/assembly-customize-the-home-page.adoc

@@ -0,0 +1,39 @@
+:_mod-docs-content-type: ASSEMBLY
+ifdef::context[:parent-context: {context}]
+
+[id="deploy-persona-specific-homepages-to-provide-targeted-content-to-distinct-teams_{context}"]
+= Deploy persona-specific homepages to provide targeted content to distinct teams
+
+:previouscontext: {context}
+:context: deploy-persona-specific-homepages-to-provide-targeted-content-to-distinct-teams
+
+[role="_abstract"]
+Persona-specific homepage layouts allow you to deliver targeted content, such as role-appropriate templates and links, to distinct user groups in {product}.
+
+// Configuring persona-based homepages
+
+include::../modules/shared/proc-author-default-persona-based-layouts-to-curate-distinct-starting-experiences.adoc[leveloffset=+1]
+
+include::../modules/shared/proc-attach-homepages-to-groups-to-control-access-and-automate-layout-assignment.adoc[leveloffset=+1]
+
+include::../modules/shared/ref-homepage-backend-configuration-reference.adoc[leveloffset=+1]
+
+include::../modules/shared/ref-homepage-visibility-rule-syntax.adoc[leveloffset=+1]
+
+// Customizing homepage cards
+
+include::../modules/shared/ref-available-homepage-cards.adoc[leveloffset=+1]
+
+include::../modules/shared/proc-arrange-homepage-card-layouts-to-optimize-visual-organization.adoc[leveloffset=+1]
+
+include::../modules/shared/proc-define-the-layout-of-the-rhdh-home-page.adoc[leveloffset=+1]
+
+include::../modules/shared/proc-customize-your-dynamic-homepage.adoc[leveloffset=+1]
+
+include::../modules/shared/proc-customize-quickaccesscard-card-icons-on-the-rhdh-homepage.adoc[leveloffset=+1]
+
+:context: {previouscontext}
+:!previouscontext:
+
+ifdef::parent-context[:context: {parent-context}]
+ifndef::parent-context[:!context:]

assemblies/configure_customizing-rhdh/assembly-deploy-persona-specific-homepages-to-provide-targeted-content-to-distinct-teams.adoc

@@ -27,6 +27,8 @@ By delegating RBAC access through either method, you can expect the following ou
 * Visibility of other users' or teams' permissions is restricted.
 * Administrators retain overarching control while delegating team-specific access.
 
+Use groups to configure persona-specific homepage layouts, ensuring users see homepage content appropriate to their role.
+
 include::../modules/shared/proc-delegate-rbac-access-in-rhdh-by-using-the-web-ui.adoc[leveloffset=+1]
 
 

assemblies/shared/assembly-delegate-role-based-access-controls-rbac-access-in-rhdh.adoc

@@ -73,7 +73,7 @@
 `GITLAB_HOST`
 
 
-|Global Floating Action Button |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-global-floating-action-button/v/1.9.1[@red-hat-developer-hub/backstage-plugin-global-floating-action-button]` |1.9.1 
+|Global Floating Action Button |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-global-floating-action-button/v/1.9.2[@red-hat-developer-hub/backstage-plugin-global-floating-action-button]` |1.9.2 
 |`./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-global-floating-action-button`
 
 
@@ -161,7 +161,7 @@
 |`oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator@sha256:5b52adc153afcf79fb134262aa01b1e117085bf59c1a1997ff2e3a6f31c7647a`
 
 
-|Quickstart |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-quickstart/v/1.9.3[@red-hat-developer-hub/backstage-plugin-quickstart]` |1.9.3 
+|Quickstart |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-quickstart/v/1.9.4[@red-hat-developer-hub/backstage-plugin-quickstart]` |1.9.4 
 |`./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-quickstart`
 
 

modules/extend_dynamic-plugins-reference/ref-supported-plugins.adoc

@@ -17,11 +17,11 @@ include::../../artifacts/snip-technology-preview.adoc[]
 |`./dynamic-plugins/dist/backstage-community-plugin-acr`
 
 
-|Bulk Import |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-bulk-import/v/7.3.2[@red-hat-developer-hub/backstage-plugin-bulk-import]` |7.3.2 
+|Bulk Import |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-bulk-import/v/7.3.4[@red-hat-developer-hub/backstage-plugin-bulk-import]` |7.3.4 
 |`./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-bulk-import`
 
 
-|Bulk Import |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-bulk-import-backend/v/7.3.2[@red-hat-developer-hub/backstage-plugin-bulk-import-backend]` |7.3.2 
+|Bulk Import |`https://npmjs.com/package/@red-hat-developer-hub/backstage-plugin-bulk-import-backend/v/7.3.4[@red-hat-developer-hub/backstage-plugin-bulk-import-backend]` |7.3.4 
 |`./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-bulk-import-backend-dynamic`
 
 

modules/extend_dynamic-plugins-reference/ref-technology-preview-plugins.adoc

@@ -9,7 +9,7 @@
 "GitHub","@backstage/plugin-scaffolder-backend-module-github","Backend","0.9.7","Production","active","./dynamic-plugins/dist/backstage-plugin-scaffolder-backend-module-github-dynamic",";","Disabled"
 "GitLab Org","@backstage/plugin-catalog-backend-module-gitlab-org","Backend","0.2.19","Production","active","./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-gitlab-org-dynamic","`GITLAB_HOST`;`GITLAB_ORG_GROUP`;","Disabled"
 "GitLab","@backstage/plugin-catalog-backend-module-gitlab","Backend","0.8.1","Production","active","./dynamic-plugins/dist/backstage-plugin-catalog-backend-module-gitlab-dynamic","`GITLAB_DISCOVERY_GROUP`;`GITLAB_HOST`;","Disabled"
-"Global Floating Action Button","@red-hat-developer-hub/backstage-plugin-global-floating-action-button","Frontend","1.9.1","Production","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-global-floating-action-button",";","Enabled"
+"Global Floating Action Button","@red-hat-developer-hub/backstage-plugin-global-floating-action-button","Frontend","1.9.2","Production","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-global-floating-action-button",";","Enabled"
 "Global Header","@red-hat-developer-hub/backstage-plugin-global-header","Frontend","1.21.4","Production","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-global-header",";","Enabled"
 "Http Request","@roadiehq/scaffolder-backend-module-http-request","Backend","5.6.0","Production","active","oci://registry.access.redhat.com/rhdh/roadiehq-scaffolder-backend-module-http-request@sha256:2e498033306df2711ec2a548db0a9db921f911eb9b99af2b9e44162b4851bbe8",";","Disabled"
 "Keycloak","@backstage-community/plugin-catalog-backend-module-keycloak","Backend","3.19.2","Production","active","./dynamic-plugins/dist/backstage-community-plugin-catalog-backend-module-keycloak-dynamic","`KEYCLOAK_BASE_URL`;`KEYCLOAK_CLIENT_ID`;`KEYCLOAK_CLIENT_SECRET`;`KEYCLOAK_LOGIN_REALM`;`KEYCLOAK_REALM`;","Disabled"
@@ -22,16 +22,16 @@
 "Orchestrator","@red-hat-developer-hub/backstage-plugin-orchestrator","Frontend","5.7.10","Production","active","oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator@sha256:062a536d266bcd76d454fc9fdc0157b99e62074f6d3304578a68f515ced83e64",";","Disabled"
 "Orchestrator","@red-hat-developer-hub/backstage-plugin-orchestrator-backend","Backend","8.9.4","Production","active","oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend@sha256:365d67fddeeaa2cf0b0266b012eb3e74fb5d5071b848059662353e62e7f9ceab",";","Disabled"
 "Orchestrator","@red-hat-developer-hub/backstage-plugin-scaffolder-backend-module-orchestrator","Backend","1.5.4","Production","active","oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator@sha256:5b52adc153afcf79fb134262aa01b1e117085bf59c1a1997ff2e3a6f31c7647a",";","Disabled"
-"Quickstart","@red-hat-developer-hub/backstage-plugin-quickstart","Frontend","1.9.3","Production","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-quickstart",";","Enabled"
+"Quickstart","@red-hat-developer-hub/backstage-plugin-quickstart","Frontend","1.9.4","Production","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-quickstart",";","Enabled"
 "RBAC","@backstage-community/plugin-rbac","Frontend","1.52.4","Production","active","./dynamic-plugins/dist/backstage-community-plugin-rbac",";","Disabled"
 "Regex","@backstage-community/plugin-scaffolder-backend-module-regex","Backend","2.15.1","Production","active","./dynamic-plugins/dist/backstage-community-plugin-scaffolder-backend-module-regex-dynamic",";","Enabled"
 "Signals","@backstage/plugin-signals-backend","Backend","0.3.13","Production","active","./dynamic-plugins/dist/backstage-plugin-signals-backend-dynamic",";","Disabled"
 "Tech Radar","@backstage-community/plugin-tech-radar","Frontend","1.17.0","Production","active","./dynamic-plugins/dist/backstage-community-plugin-tech-radar",";","Disabled"
 "Tech Radar","@backstage-community/plugin-tech-radar-backend","Backend","1.16.0","Production","active","./dynamic-plugins/dist/backstage-community-plugin-tech-radar-backend-dynamic","`TECH_RADAR_DATA_URL`;","Disabled"
 "Topology","@backstage-community/plugin-topology","Frontend","2.12.2","Production","active","./dynamic-plugins/dist/backstage-community-plugin-topology",";","Disabled"
 "ACR","@backstage-community/plugin-acr","Frontend","1.24.1","Red Hat Tech Preview","active","./dynamic-plugins/dist/backstage-community-plugin-acr",";","Disabled"
-"Bulk Import","@red-hat-developer-hub/backstage-plugin-bulk-import","Frontend","7.3.2","Red Hat Tech Preview","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-bulk-import",";","Disabled"
-"Bulk Import","@red-hat-developer-hub/backstage-plugin-bulk-import-backend","Backend","7.3.2","Red Hat Tech Preview","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-bulk-import-backend-dynamic",";","Disabled"
+"Bulk Import","@red-hat-developer-hub/backstage-plugin-bulk-import","Frontend","7.3.4","Red Hat Tech Preview","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-bulk-import",";","Disabled"
+"Bulk Import","@red-hat-developer-hub/backstage-plugin-bulk-import-backend","Backend","7.3.4","Red Hat Tech Preview","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-bulk-import-backend-dynamic",";","Disabled"
 "Events Backend Module GitHub","@backstage/plugin-events-backend-module-github","Backend","0.4.10","Red Hat Tech Preview","active","oci://registry.access.redhat.com/rhdh/backstage-plugin-events-backend-module-github@sha256:c1d17d47aaac41eaeb3ad15c64d904cbad7d93f351cdd69d7aee13b2097329ed","`GITHUB_WEBHOOK_SECRET`;","Disabled"
 "Extensions","@red-hat-developer-hub/backstage-plugin-extensions","Frontend","0.17.1","Red Hat Tech Preview","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-extensions",";","Enabled"
 "Extensions","@red-hat-developer-hub/backstage-plugin-catalog-backend-module-extensions","Backend","0.17.1","Red Hat Tech Preview","active","./dynamic-plugins/dist/red-hat-developer-hub-backstage-plugin-catalog-backend-module-extensions-dynamic","`RHDH_EXTENSIONS_DIRECTORY`;","Enabled"

modules/extend_dynamic-plugins-reference/rhdh-supported-plugins.csv

@@ -1,12 +1,20 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="customize-the-home-page-cards_{context}"]
-= Customize the Home page cards
+[id="arrange-homepage-card-layouts-to-optimize-visual-organization_{context}"]
+= Arrange homepage card layouts to optimize visual organization
 
 [role="_abstract"]
-As an administrator, you can customize the layout and content of the Home page to create a tailored user experience. This includes integrating various specialized cards into the primary view.
+Arrange and customize homepage card layouts to ensure your content scales correctly across different screen sizes.
 
-The Home page layout uses a 12-column grid system. You can precisely define the position (x), width (w), and height (h) for each card across multiple screen breakpoints:
+The Home page layout uses a 12-column grid system.
+The grid uses the following layout properties:
+
+* `w` (width): Number of columns (1-12)
+* `h` (height): Number of grid rows (arbitrary units)
+* `x` (x-position): Column offset (0-11)
+* `y` (y-position): Row offset (optional, defaults to auto-placement)
+
+You can define these layout properties for each card across multiple screen breakpoints:
 
 * Extra-large (xl)
 * Large (lg)
@@ -59,7 +67,9 @@ dynamicPlugins:
 ----
 
 .Prerequisites
+
 * You have administrative access and can modify the `{my-app-config-file}` file for dynamic plugin configurations.
+* Optional: For persona-based homepage configuration, you have installed and configured the homepage backend plugin.
 
 .Procedure
 * Configure different cards for your Home page in {product} as shown in the following code:

…/proc-customize-the-home-page-cards.adoc …uts-to-optimize-visual-organization.adocmodules/shared/proc-customize-the-home-page-cards.adoc renamed to modules/shared/proc-arrange-homepage-card-layouts-to-optimize-visual-organization.adoc modules/shared/proc-customize-the-home-page-cards.adoc renamed to modules/shared/proc-arrange-homepage-card-layouts-to-optimize-visual-organization.adoc

@@ -0,0 +1,122 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="attach-homepages-to-groups-to-control-access-and-automate-layout-assignment_{context}"]
+= Attach homepages to groups to control access and automate layout assignment
+
+[role="_abstract"]
+Assign persona-specific homepage layouts to user groups to automate role-based content access.
+
+.Prerequisites
+
+* You have {product} {product-version} or later running with the homepage backend plugin enabled.
+* You defined groups for each user persona (for example, `group:default/developers`, `group:default/data-scientists`, `group:default/managers`).
+* You authored persona-based homepage layouts in your `{my-app-config-file}` configuration file.
+* You have administrative access to modify the `{my-app-config-file}` configuration file.
+
+.Procedure
+
+. Identify your user personas and their corresponding groups.
++
+--
+[IMPORTANT]
+====
+Replace the example group names below with your organization's actual group names.
+====
+
+[options="header"]
+|===
+|Persona |Group
+|Developer |`group:default/developers`
+|Manager |`group:default/managers`
+|Data Scientist |`group:default/data-scientists`
+|===
+--
+
+. Verify that you created the groups in your {product-very-short} configuration.
++
+Check that the groups exist by using the RBAC web UI or by reviewing your RBAC configuration file.
+You must create all groups referenced in your persona mapping before configuring homepage visibility.
+
+. Open your `{my-app-config-file}` configuration file.
+
+. Attach persona-specific layouts to groups by adding the `if.groups` field to group cards under a shared visibility condition.
++
+For example, attach the developer persona layout to the developers group:
++
+[source,yaml]
+----
+homepage:
+  defaultWidgets:
+    # Attach developer layout to developers group
+    - if:
+        groups: [group:default/developers]
+      children:
+        - id: developer-onboarding
+          ref: 'rhdh-onboarding-section'
+          layout:
+            xl: { w: 12, h: 6 }
+            lg: { w: 12, h: 6 }
+
+        - id: developer-quickaccess
+          ref: quickaccess-card
+          props:
+            title: Developer Quick Access
+          layout:
+            xl: { w: 7, h: 8 }
+            lg: { w: 7, h: 8 }
+
+        - id: templates
+          ref: TemplateSection
+          layout:
+            xl: { w: 12, h: 5 }
+            lg: { w: 12, h: 5 }
+
+        - id: starred-entities
+          ref: CatalogStarredEntitiesCard
+          layout:
+            xl: { w: 5, h: 4, x: 7 }
+            lg: { w: 5, h: 4, x: 7 }
+----
++
+The `groups` field accepts an array of group entity references.
+Users who belong to any of the listed groups see all child cards.
+
+. Control visibility for multiple groups by adding additional `if.groups` configurations.
++
+Individual child cards can include their own `if` conditions to further restrict visibility beyond the parent group's rules.
++
+[NOTE]
+====
+The front-end positions cards according to layout coordinates (`x`, `y`, `w`, `h`), not array order.
+The configuration array order does not affect rendering position.
+====
+
+. Save the configuration file and restart {product}:
++
+[source,terminal,subs="+quotes"]
+----
+$ kubectl rollout restart deployment/_<rhdh-deployment-name>_
+----
++
+Replace _<rhdh-deployment-name>_ with the name of your {product-very-short} deployment.
++
+[IMPORTANT]
+====
+{product-very-short} validates the homepage configuration at startup.
+If the configuration contains errors, {product-very-short} will fail to start.
+Check the pod logs for configuration validation errors if the deployment does not become ready.
+====
+
+.Verification
+
+. Log in to {product} as a test user who belongs to one of the configured groups.
++
+The homepage displays only the cards configured for that user's persona.
+
+. Log in as a test user from a different group.
++
+The homepage displays a different set of cards based on the second user's group membership.
+
+. Log in as a test user who does not belong to any persona-specific group.
++
+The homepage displays only the default cards that have no `if` conditions.