PatternFly 6 — Dashboard Guidelines¶
The Sardeenz dashboard uses PatternFly 6 (PF6) as its design system and component library.
Key Rules¶
- Do NOT use Context7 for PatternFly components — it may return outdated PF4/PF5 patterns
- Use PatternFly.org as the authoritative reference
- Use the built-in
/patternfly-6-developmentskill when working on dashboard components
CSS and Tokens¶
- All PF CSS classes use the
pf-v6-prefix (notpf-v5-or unprefixed) - Use only
--pf-t--semantic design tokens for custom styling - Never use
--pf-v6-component-level tokens directly — they are internal
/* Correct */
.my-component {
color: var(--pf-t--global--color--brand--default);
padding: var(--pf-t--global--spacer--md);
}
/* Wrong — uses internal component token */
.my-component {
color: var(--pf-v6--c-button--m-primary--Color);
}
Import Patterns¶
// Components
import { Button, Card, CardBody } from '@patternfly/react-core';
// Icons
import { PlusCircleIcon } from '@patternfly/react-icons';
// Charts
import { Chart, ChartBar } from '@patternfly/react-charts/victory';
// Table
import { Table, Thead, Tbody, Tr, Th, Td } from '@patternfly/react-table';
Layout Patterns¶
- Use
Page,PageSection, andPageSidebarfor top-level layout - Use
Grid/GridItemfor responsive multi-column layouts - Use
Stack/StackItemfor vertical stacking - Use
Split/SplitItemfor horizontal alignment
Accessibility¶
- All interactive elements must have accessible labels
- Use
aria-labeloraria-labelledbyon icon-only buttons - Follow PF6's built-in ARIA patterns — don't override them
- Test with keyboard navigation
Reference¶
- PatternFly.org Components
- PatternFly.org Layouts
- PatternFly.org Design Tokens
- Sardeenz v1 UI patterns — reference for cherry-picking