Skip to content

Instantly share code, notes, and snippets.

@JoeArauzo

JoeArauzo/diagrams-best-practice.adoc

Last active January 19, 2021 16:42
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save JoeArauzo/96f2cccaf9d19a502f9965263e7f5fe4 to your computer and use it in GitHub Desktop.
Save JoeArauzo/96f2cccaf9d19a502f9965263e7f5fe4 to your computer and use it in GitHub Desktop.
Download ZIP
Best practice for diagram size.
Raw
diagrams-best-practice.adoc

Overview

I’m sure you can agree, if you’re writing technical documentation, you’re also using diagrams to get your point across. But how should you size your diagrams while also accomplishing the following?

  1. Diagram shows equally well regardless if printed, displayed online, or included in a slide deck.

  2. Clearly legible text within the diagram.

  3. Retain a high level of quality when resized.

The following are some best practices to help.

Exporting Assets from Microsoft Visio

Chances are you’re already using Microsoft Visio for all, or maybe just a part, of your workflow for creating diagrams. It’s impossible to deny, a lot of great shapes already exist in the Visio Stencil format. Just take a look at Visio Cafe.
The purpose of this gist is to share best practices I have discovered for sizing diagrams and their assets so they display legibly in both printed and web/presentation mediums.

This assumes a standard printed page size of

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment