Rough.js annotation in : Fit
Rough.js annotation decides what is being compared in under “Fit.” The figure that must stay on the axis is 2017. Drawing it larger does not create a unit. Look first for a cut axis and a missing key. Excel or Google Sheets or PowerPoint; export SVG/PDF.
When should I pick Rough.js annotation? When the story is: explainer highlights, ad concept frames, teaching callouts. When should I avoid Rough.js annotation? Skip it in cases like: dense quantitative comparison that needs precise lengths. Rough.js brought controllable sketch rendering to the open web
imperfect strokes and fills as attention cues Yes if one claim is visible at a glance in Meta, Google and retail print; otherwise link to a full figure. Yes for lab reports and poster boards if axes, units and a source line are present. Do not rely on hue alone. Label directly and check greyscale.
Rough.js annotation: honour imperfect strokes and fills as attention cues, and switch when dense quantitative comparison that needs precise lengths. The core mark of Rough.js annotation is imperfect strokes and fills as attention cues. explainer highlights, ad concept frames, teaching callouts
Read Rough.js annotation as , “Fit,” and 2017. A bar with no unit is not those three.2017
Figures to keep
- Year of the chart
- 2017
- Axis figure
- 2017
- Chart
- Rough.js annotation
- How to read it
- Fit