|
2 | 2 | section: extensions |
3 | 3 | subsection: Component groups |
4 | 4 | id: About component groups |
| 5 | +sortorder: 1 |
5 | 6 | --- |
6 | 7 |
|
7 | | -The [**@patternfly/react-component-groups**](https://www.npmjs.com/package/@patternfly/react-component-groups) extension contains a range of React components that are more complex than basic PatternFly components, often combining and adjusting multiple base components to address common use cases. |
| 8 | +Component groups lives in its own package [`@patternfly/react-component-groups`](https://www.npmjs.com/package/@patternfly/react-component-groups) |
8 | 9 |
|
9 | | -This extension replaces **RedHatInsights/frontend-components**. To migrate your product to this new implementation, you can refer to [this migration guide](https://github.com/patternfly/react-component-groups/migration.md). |
| 10 | +# Component groups |
10 | 11 |
|
11 | | -## Contributing to component groups |
| 12 | +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. |
12 | 13 |
|
13 | | -The code for component groups lives in the [patternfly/react-component-groups repository](https://github.com/patternfly/react-component-groups). Any issues related to additions or changes to this extension should be made within this repository. |
| 14 | +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 unit test coverage, and ensure that CSS overrides all correctly reference the PatternFly CSS API. |
14 | 15 |
|
15 | | -extension is an ongoing, collaborative effort to provide solutions for |
| 16 | +**Note:** This extension replaces [`RedHatInsights/frontend-components`](https://github.com/RedHatInsights/frontend-components). If you previoulsy used `frontend-components`, you can refer to [this migration guide](https://github.com/patternfly/react-component-groups/migration.md) to help you transition to `react-component-groups`. |
16 | 17 |
|
17 | | -For additional details, like contribution guidelines and instructions, refer to [the component groups GitHub README](https://github.com/patternfly/react-component-groups#readme). |
| 18 | +## Contribution guidelines |
| 19 | + |
| 20 | +The code for component groups lives in the [`patternfly/react-component-groups repository`](https://github.com/patternfly/react-component-groups). |
| 21 | + |
| 22 | +Specific contribution guidelines and instructions are outlined in [the component groups GitHub README](https://github.com/patternfly/react-component-groups#readme). |
| 23 | + |
| 24 | +### Reporting bugs and requesting new features |
| 25 | + |
| 26 | +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. |
| 27 | + |
| 28 | +If you notice a bug or have a suggestion for a new component group, feel free to file an issue in our [GitHub repository](https://github.com/patternfly/react-component-groups/issues)! Please make sure to check if there is already a pre-existing issue before creating a new issue. |
0 commit comments