Skip to content

OSDOCS-13110: Update PatternFly guidelines for PF6 in OCP content #99660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2025
Merged

OSDOCS-13110: Update PatternFly guidelines for PF6 in OCP content #99660

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions web_console/dynamic-plugin/overview-dynamic-plugin.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,14 +55,16 @@ When creating your plugin, follow these guidelines for using PatternFly:

* Use link:https://www.patternfly.org/components/all-components/[PatternFly] components and PatternFly CSS variables. Core PatternFly components are available through the SDK. Using PatternFly components and variables help your plugin look consistent in future console versions.
ifndef::openshift-rosa-hcp[]
** Use Patternfly 4.x if you are using {product-title} versions 4.14 and earlier.
** Use Patternfly 5.x if you are using {product-title} 4.15 or later.
** Use PatternFly 4.x if you are using {product-title} versions 4.14 and earlier.
** Use PatternFly 5.x if you are using {product-title} versions 4.15 through 4.18.
** Use PatternFly 6.x if you are using {product-title} versions 4.19 and later.

endif::openshift-rosa-hcp[]
ifdef::openshift-rosa-hcp[]
** Use Patternfly 5.x.
endif::openshift-rosa-hcp[]
* Make your plugin accessible by following link:https://www.patternfly.org/accessibility/accessibility-fundamentals/[PatternFly's accessibility fundamentals].
* Avoid using other CSS libraries such as Bootstrap or Tailwind. They might conflict with PatternFly and not match the rest of the console. Plugins should only include styles that are specific to their user interfaces to be evaluated on top of base PatternFly styles. Avoid importing styles such as `@patternfly/react-styles/**/*.css` or any styles from the `@patternfly/patternfly` package in your plugin.
* The console application is responsible for loading base styles for all supported PatternFly version(s).
* Avoid using other CSS libraries such as Bootstrap or Tailwind. They might conflict with PatternFly and not match the rest of the console. Plugins should only include styles that are specific to their user interfaces to be evaluated on top of base PatternFly styles. Do not import styles directly from `@patternfly/react-styles/**/*.css` or `@patternfly/patternfly`. Instead, use components and CSS variables provided by the console SDK.
* The console application is responsible for loading base styles for all supported PatternFly versions.

include::modules/dynamic-plugin-localization.adoc[leveloffset=+2]