When our customers are searching for new software, they often turn to marketplaces and catalogs from Red Hat and our partners. With so many offerings available, it’s important for our listings to be clearly and accurately identified as Red Hat offerings so that customers can find them quickly and easily.

When listings have an image, use the offering’s full color technology icon so that customers can distinguish between multiple Red Hat offerings on the same page.

Use the full, approved name for offerings. For products and platforms, that means including “Red Hat” and typing in title case. For components, pay attention to the official spelling and capitalization of the name.

Listing descriptions should put the information that’s most useful to the customer first. Refer to the product’s messaging guide and keep the description clear and concise.

In Red Hat-owned marketplaces, you can use technology icons to indicate that listings are compatible with specific Red Hat offerings.

First-party listings of Red Hat offerings in marketplaces should use Red Hat technology icons for the image, even though Red Hat is not listed as the provider or source of the software.

Partners or resellers who are listing Red Hat offerings with permission should use their own logo for the listing image. Learn more on the partner handbook.

Do not use the Red Hat logo, product logos, or the hat for listings. This makes it difficult to distinguish between multiple Red Hat listings.

Do not abbreviate names or use a name other than the full, approved name of an offering.

Do not use the logo or icon of an open source community project or an outdated product icon.

The interface is the actual product itself, where our customers do their work. For many customers, this is the most common way they interact with our brand. Product branding in the interface should improve the user experience (not get in the way), and should clearly communicate which Red Hat offerings they are using.

Use the one- or two-line, full color product or platform logo in the masthead of the interface, with appropriate clear space (at least the height of the “e” in the word “Red”). Always use the approved logo image file rather than recreating the logo.

Use platform artwork or general Red Hat imagery—like an illustration or icon pattern—for decoration on hero graphics and empty states.

Use technology icons to help users navigate the interface and differentiate between Red Hat offerings.

In interfaces that are built with other design systems (like Material or Carbon), you should still use Red Hat technology icons as they exist to represent our offerings. Use the one-color version of icons when necessary.

In PatternFly, component interfaces that aren’t tied to a specific product or platform should use the Red Hat logo in the masthead and type the name of the component in the sidebar.

In component interfaces without a sidebar, type the name of the component in Red Hat Display Medium in the masthead. Place the Red Hat logo in a separate but prominent spot in the interface, like the opposite side of the masthead.

Avoid using one-color logos. In digital applications, we should use full color logos.

Don’t use a three-line product logo in a masthead; there’s not enough room. Opt for a one- or two-line logo instead, which you can request from the Brand team if needed.

Don’t create logos for components. Don’t combine text with the hat or a technology icon.

Don’t modify technology icons by changing their color or removing them from the rounded rectangle bounding shape.

Don’t redraw Red Hat icons in the style of another design system. Don’t represent a Red Hat offering with an icon from another design system, either.

Avoid using artwork or graphics for heroes and empty states that don’t match the Red Hat design language.

Presentations at Red Hat events, webinars, and sales meetings are often the first place prospective customers and partners see our product branding. It’s important to make the most of those first impressions. And remember—nothing is internal only: Design your slides with the expectation that they might be seen by customers and partners in the future.

Use the full name of an offering on the first use. Approved acronyms and abbreviations come in handy, but they can be confusing without context.

Build recognition for our icons and simplify graphics by using technology icons. You can type the name of the offering near the icon for added context.

Set viewer expectations by using the correct type of icons. Represent Red Hat offerings with technology icons. Represent general concepts with icons from the standard icon library. It’s okay to mix types of icons on the same slide.

When listing multiple Red Hat products on the same slide, type out the names in plain text or use technology icons rather than using multiple product logos.

For presentations related to a platform, use one of our platform presentation templates. They have platform artwork built in.

When referring to a component, use either the general Red Hat presentation template or the template for the platform that the component falls under.

Avoid a “sea of red hats.” Don’t fill a slide with multiple product logos. Use technology icons or type out the names in our font instead.

Don’t use outdated product logos or icons. Check to make sure that you’re using the most recent version of our brand assets.

Don’t create logos for components or pair them with the Red Hat logo in a way that looks like an official logo. Use the component’s technology icon instead.

Don’t use abbreviations on the first reference to an offering. Use approved acronyms or abbreviations only after introducing the full name.

Don’t modify icons or imply that a general concept is an official Red Hat offering. It’s okay to mix multiple icon types on the same slide.

Don’t use technology icons to create custom artwork for a component or product. Only our 3 platforms use custom artwork.

Marketing spans a huge variety of mediums—from our website to advertising, from swag to giant event booths. Using product branding across these applications creates a consistent journey for our customers as they learn more about Red Hat and our offerings, which makes it easier for them to trust what they see when they’re buying and making purchasing decisions. We want to make every brand impression count.

Use product logos on collateral when it’s relevant to the content.

In web graphics, use technology icons and platform artwork to visually tie the web experience back to other parts of the customer journey.

When marketing a component, use branding and artwork for the product that the component is a part of. This makes it clear which of our products the customer should purchase to use the component.

When you need additional visuals, choose general illustrations, icon patterns, or photography related to the concept.

Always include either a product logo or the Red Hat logo on swag. Place the logo in a separate imprint area from the main artwork if needed.

In videos, use approved intros and outros. For our 3 platforms, these include animated technology icons in combination with the platform’s logo.

Avoid using multiple product logos on one piece of swag. Instead, use the Red Hat logo and then type out the names of the products.

Don’t abbreviate or simplify names in marketing materials. It might be the first time the customer is hearing about the offering.

Don’t create marketing materials without a Red Hat logo or product logo. Icons and artwork might not be recognizable on their own.

Don’t modify technology icons to create custom artwork for products or components. Use existing illustrations, icons, and photography.

Don’t co-brand a product logo with a partner logo. For co-branded product marketing, use a standard co-brand logo.