Technical diagrams explain what our products do and how they work together. They can also illustrate concepts, technological approaches, or processes. They support specific documentation and have intended context, purpose, and audience.
The primary focus should be on the components (like hardware, users, and concepts), their proximity to each other, and their common fate. Use simple shapes and icons to represent each component so that the resulting diagrams are simple, clean, and easy to understand. Using the same elements in each diagram means they work well together as a set, no matter which product they’re for. Also, it creates consistency that helps readers understand what we mean quickly.
Always use flat rectangular shapes with no drop shadows, bevels, or gradients.
Group similar (or equal) components to simplify the diagram and make the content easier to understand. Use the grouping style that best fits your content and the concept you need to illustrate.
Use icons only for easily recognized concepts, like people, servers, or clouds. This helps the viewer focus on the main message, instead of what individual icons mean.
LINES & ARROWS
Lines and arrows guide the viewer through the diagram. Lines show how components relate and connect to each other. They indicate action, direction, and network connections.
Proper labeling is crucial. Labels identify each element and connect them to the supporting documentation.
Group 1: Storage and big data
The diagram illustrates an overview of Red Hat Gluster Storage architecture and Storage concepts — showing the product can be installed and managed on-premise, or in a public cloud, such as Google’s Cloud Platform.
Group 2: IT infrastructure (2A and 2B)
This diagram provides an example of the Red Hat Enterprise Virtualization environment workflow for backing up a self-hosted engine using a failover host.
Group 2: IT infrastructure (2C)
This diagram depicts the Red Hat Satellite subscription process of registering a virtual machine.
Group 3: Application development
This diagram illustrates an example of OpenShift routing — showing how data flows from the master through the plug-in and finally into an HAProxy configuration.
Color is used to color-code products or create hierarchy. Use color sparingly to emphasize important pieces of information or visually connect concepts.