Our Code Of Conduct

PatternFly adheres to the Contributor Covenant Code of Conduct. As a PatternFly community member, you are expected to uphold this code of conduct.

Keep in touch

  • Find us on Slack
  • Follow us on Twitter
  • Read our blog
  • Subscribe to our mailing list to participate in or follow a variety of discussions on both technical and design topics. This is also a good place to ask questions, gather requirements, or join forces with other community members. Older threads can be found in the archive.
  • Check out the PatternFly YouTube channel to view live meetings or prior meeting recordings. Announcements about upcoming meetings are sent to the mailing list. You can also reach out to us on our mailing list to be added directly to our community invite.


File an Issue

Before filing an issue, check the list of open issues against our GitHub repositories. When you create an issue, include as many details as possible, use a clear and descriptive title, and remember that an image is worth a thousand words, so try to add images and links when possible.

Proposing or Modifying a Design

Propose a new pattern, add an enhancement to an existing pattern, or help us fix existing documentation issues. All design and documentation changes are submitted and managed through our Design Repo. Visit How to Contribute to PatternFly Design for more information.

Contributing code

Both developers and designers review PRs, so if you are committing a new design or modifying an existing design, be sure to add a link to a graphic or a working version on rawgit so that designers can preview the request.

Whenever possible, provide a link to the design documentation or specification that supported the development of the code. The PR will be reviewed by the community, and once it’s approved by two people from the team it can be merged.