Rough.js annotation in : History
Rough.js annotation decides what is being compared in under “History.” 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. When the story is: explainer highlights, ad concept frames, teaching callouts.
Use Rough.js strokes to annotate and emphasize - persuasion through human-looking marks, not chrome. Rough.js annotation encodes values as imperfect strokes and fills as attention cues. Rough.js brought controllable sketch rendering to the open web. In reports, ads and assignments it fits explainer highlights, ad concept frames, teaching callouts. Skip it when dense quantitative comparison that needs precise lengths.
This page gathers anatomy, fit, craft, failure modes and work / ads / school recipes for Rough.js annotation. When should I pick Rough.js annotation? 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. Excel or Google Sheets or PowerPoint; export SVG/PDF.
Read Rough.js annotation as , “History,” 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
- History
Sankey flow stories in 1898: HistoryNext essayAll 1100 essays1100