Welcome to the PatternFly content style guide: a place for UX professionals like you to learn about designing with words.
The words in a user interface, commonly referred to as "UX copy" or "microcopy," are just as important as the components or layouts. UX copy is another element of design, and it can drive better UX decisions and guide users to succeed.
I’ve come to believe that language is one of the most powerful design tools we have.
— n.k. feinberg, New York Times
Anyone involved in UX—researchers, designers, developers, content strategists, and more—can use this guide for building better product experiences with content design and strategy.
Style guide goal
As a PatternFly community, our goal with this style guide is to help UX professionals:
- Create clarity and consistency across products and applications.
- Make products sound more conversational and human.
- Use written content to create unified, on-brand experiences for all users.
With that said, we recognize that the PatternFly way is not the only way. This guide isn’t meant to:
- Overrule another style guide.
- Provide a complete list of all writing rules across all channels.
- Serve as hard requirements that everyone must follow.
In cases where advice differs, default to PatternFly if you’re writing for Red Hat interfaces.
- For component-specific microcopy guidance, see the component's design guidelines.
- For microcopy guidance that’s not included in this guide, see IBM Carbon’s UX content guidelines.
- For Red Hat product terminology and documentation standards, see Red Hat's supplementary style guide for Red Hat product documentation.
- For additional terminology guidance, use Merriam-Webster’s online dictionary.
In true Flyer fashion, we keep this style guide open. Contribute your ideas through GitHub.
View source on GitHub