Component groups lives in its own package @patternfly/react-component-groups
Note: This extension replaces RedHatInsights/frontend-components
. If you previously used frontend-components
, you can refer to this migration guide to help you transition to react-component-groups
.
Component groups
The component groups extension contains a range of React components that are more complex than basic PatternFly components. These component groups combine and adjust multiple base components to provide opinionated solutions for recurring use cases across products using PatternFly.
The creation and maintenance of this extension is a collaborative effort between the PatternFly and Red Hat Hybrid Cloud Console teams. All component groups receive accessibility and design reviews, and we are working to improve internationalization, add test coverage, and ensure that CSS overrides all correctly reference the PatternFly CSS API.
There are a few different functional categories of component groups:
Organize and display information in structured or flexible containers.
Enable more effective navigation and selection by providing users with options for interaction and input.
Communicate issues or restrictions through error and alert states.
Provide users with utilities that enhance usability and provide additional guidance or information within the UI.
Inform users of system conditions or processes through visualizations of entity states, statuses, and loading indicators.
Contribution guidelines
The code for component groups lives in the patternfly/react-component-groups repository
.
Specific contribution guidelines and instructions are outlined in the component groups GitHub README.
Reporting bugs and requesting new features
We aim to align the standards of component groups as closely as possible with existing PatternFly standards. Given that this is a multi-team collaboration, we will continue to work towards this goal together.
If you notice a bug or have a suggestion for a new component group, open an issue in our GitHub repository! Please make sure to check if there is already a pre-existing issue before creating a new one.