Skip to main content

Diagrams

Our diagrams and graphs are accurate and informative. We prove we're trustworthy and reliable by sweating the small stuff. Every line and color choice in our technical illustrations should feel considered.

Charts and graphs

Our charts and graphs should build trust. Attention to detail, legibility of text, and accessibility are the main priority. This is not the place for illustrations, gradients or adjacent color.

Two examples of charts showing Human/Deskilling Developers bar chart and Test Cases Solved comparison.

When absolutely essential, color can be used to group complex data.

A line graph showing tool use in GitHub Copilot with multiple data points and connections.

Diagrams

Like charts and graphs, diagrams should feel clear, technical and instructional. Occasionally color blocking can be used for key pillars (Copilot, Security) or for clarity of information.

A flow diagram showing memory generation process with Agent 1, Memory DB, and Memory API components.

Infographics

Some claims aren’t as comparative. In these moments we use icons, type, and simple layout to show the emotions that back up why the numbers matter.

An infographic showing GitHub Copilot stats: 20% higher accepted characters, 52% higher acceptance rate, and 3x throughput with 35% lower latency.

But don’t feel stuck to what’s been done before. In some settings, it’s appropriate to break out of the box to make a bold or striking claim.

Copilot Remediation rate infographic showing 47% Without Autofix, 52% With Autofix suggestion, and 98% When suggestion is used.