Rough.js annotation in 2017: Shared baseline
Keep the grid faint. Data should own the ink. Keep Rough.js annotation with “Shared baseline” and 2017 from 2017. One annotation sentence. Date the source. Variant 1 of Rough.js annotation (Hand-drawn marks). Same encoding, different layout.
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. 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 The eye compares length and position more accurately than area. PowerPoint, Excel or Google Sheets and Meta, Google and retail print share the same geometry.
Keep axis, unit, and year. If “Shared baseline” is the axis, the figure is 2017 and the year is 2017. Keep Rough.js annotation with “Shared baseline” and 2017 from 2017. 20172017
Figures to keep
- Year of the chart
- 2017
- Axis figure
- 2017
- Chart
- Rough.js annotation
- How to read it
- Shared baseline
Sankey flow stories in 1898: Shared baseline · 157-1Next essayAll 1100 essays1100