improvement(layout): a guideline for the page patterns (CUI-52)

[Cuervino]

Templates/Layout had nine stories and no guideline, so the page composition rules existed nowhere. The AppContainer slots were demonstrated in code, but nothing stated what goes in each slot, for which type of page, or when the overall summary applies. Two stories even labelled it "optional", which left the decision to whoever built the screen.

What the rules are based on

An inventory of the twelve ARTESCA listing pages: Truststore, Locations, Data Services, Identity Providers, Accounts, Virtual machines, Users, Groups, Nodes, Volumes and All Buckets. Every rule below classifies all twelve without exception.

What is added

stories/layout.guideline.mdx:

• the three slots, and what the context bar is for
• the two resource listing page forms, full page and list-detail, each with what it is, when to use it, and its composition rules
• browsable collections, which govern the breadcrumb, the presence of the overall summary, the level stated in the header, and the control that moves up one level
• dashboards, which have no canonical composition, with the condition under which one should be promoted to a pattern
• forms, marked as not yet defined

ResourceListPage in stories/layout.stories.tsx, embedded in the guideline. It composes the overall summary and a real Table with its search and create button. The existing stories demonstrate the plumbing with placeholder panels, which is not something anyone can start from. This one is meant to be copied.

Known follow-up

The guideline documents two page patterns. The list-detail form has no story of its own yet.

Generated with with a deep interaction with Claude Code.

[bert-e]

Hello cuervino,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/bypass_source_branch_lineage	Bypass the cross-branch contamination check	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request.
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @damiengillesscality

• @ChengYanJin

• @JeanMarcMilletScality

• @ZiyangLinScality

• @JBWatenbergScality

• @PierreAlexandreDelgado

• @hervedombya

• @sanassicisse

• @MonPote

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @MonPote

• @damiengillesscality

• @JBWatenbergScality

• @JeanMarcMilletScality

• @sanassicisse

• @PierreAlexandreDelgado

• @hervedombya

• @ZiyangLinScality

• @ChengYanJin