RHIDP-12605: Phase 2 Homepage - persona support and related RBAC#2153
RHIDP-12605: Phase 2 Homepage - persona support and related RBAC#2153jmagak wants to merge 9 commits into
Conversation
PR Build ResultsBuild passed -- 34/34 titles | 86s Content Quality AssessmentCQA Report
SummaryChecks: 19 total, 19 pass, 0 fail 19 checks: 19 pass, 0 fail Run Updated 2026-05-18 14:21:59 UTC |
f96146a to
9e18a23
Compare
9e18a23 to
42dfe9f
Compare
42dfe9f to
7c1b1aa
Compare
7c1b1aa to
1c8d7c1
Compare
1c8d7c1 to
482ac9e
Compare
482ac9e to
77f15e4
Compare
77f15e4 to
7f67714
Compare
7f67714 to
40f099b
Compare
606ac5f to
186ac2b
Compare
186ac2b to
5774212
Compare
18e85d4 to
94284d3
Compare
94284d3 to
77849eb
Compare
christoph-jerolimov
left a comment
There was a problem hiding this comment.
Hi @jmagak, thanks a lot. This all looks good to me.
There are just two concerns I have at the moment:
- The term "RBAC groups" is a bit misleading to me because groups are not necessary related to RBAC. I would use just groups or group memberships.
- The
permissionscondition doesn't work as I / we expected. I opened issue https://redhat.atlassian.net/browse/RHDHBUGS-3132 for this and it would be nice to remove that sections until the issue is resolved.
Is that okay for you?
b240d5c to
5d8ed57
Compare
5d8ed57 to
2a94bcb
Compare
2a94bcb to
c508617
Compare
c508617 to
20178dc
Compare
20178dc to
5d4d0e7
Compare
5d4d0e7 to
8bda1c1
Compare
|
rh-tokeefe
left a comment
There was a problem hiding this comment.
@jmagak I noted a few things for you to consider. LGTM!
| :context: deploy-persona-specific-homepages-to-provide-targeted-content-to-distinct-teams | ||
|
|
||
| [role="_abstract"] | ||
| Deploy persona-specific homepage layouts in {product} to deliver targeted content to distinct user groups by configuring visibility rules that automatically show role-appropriate cards, templates, and quick access links to each team. |
There was a problem hiding this comment.
| Deploy persona-specific homepage layouts in {product} to deliver targeted content to distinct user groups by configuring visibility rules that automatically show role-appropriate cards, templates, and quick access links to each team. | |
| Persona-specific homepage layouts allow you to deliver targeted content, such as role-appropriate templates and links, to distinct user groups in {product}. |
|
|
||
| [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 homepage card layouts and integrate specialized cards by using the 12-column grid system to optimize visual organization and create effective user experiences across different screen sizes. |
There was a problem hiding this comment.
| Arrange homepage card layouts and integrate specialized cards by using the 12-column grid system to optimize visual organization and create effective user experiences across different screen sizes. | |
| Arrange and customize homepage card layouts to ensure your content scales correctly across different screen sizes. |
| = Attach homepages to groups to control access and automate layout assignment | ||
|
|
||
| [role="_abstract"] | ||
| Attach persona-specific homepage layouts to groups to control access and automate layout assignment, ensuring users automatically see only the homepage content relevant to their role based on group membership. |
There was a problem hiding this comment.
| Attach persona-specific homepage layouts to groups to control access and automate layout assignment, ensuring users automatically see only the homepage content relevant to their role based on group membership. | |
| Assign persona-specific homepage layouts to user groups to automate role-based content access |
|
|
||
| [role="_abstract"] | ||
| As an administrative user, you can easily integrate custom features or content from any installed plugin into your Home page layout. You can use the additional cards available for configuration based on the front-end plugins you enable. | ||
| Integrate custom features from installed plugins into your Home page by using available cards. |
There was a problem hiding this comment.
Should Home be bold here? I'm not sure if it's a specific UI element in this context.
| = Homepage backend configuration reference | ||
|
|
||
| [role="_abstract"] | ||
| Reference information about the homepage backend plugin configuration options, card structure, and API endpoints. |
There was a problem hiding this comment.
| Reference information about the homepage backend plugin configuration options, card structure, and API endpoints. | |
| Use these backend plugin configuration options, card structures, and API endpoints to customize and manage your homepage data. |
| = Homepage visibility rule syntax | ||
|
|
||
| [role="_abstract"] | ||
| Reference information about controlling who can see homepage cards. |
There was a problem hiding this comment.
| Reference information about controlling who can see homepage cards. | |
| Review the visibility properties, access control parameters, and user group settings used to restrict or grant access to homepage cards. |



IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s): 1.10, main
Issue: RHIDP-12605
Preview:
15. Deploy persona-specific homepages to provide targeted content to distinct teams
15.1. Author default persona-based layouts to curate distinct starting experiences
15.2. Attach homepages to RBAC groups to control access and automate layout assignment
15.3. Homepage backend configuration reference
15.4. Homepage visibility rule syntax