Most data tools start with the chart. You pick a visualization, pour data into it, and hope the reader works out what it means. Scrolld starts from the opposite end: the story.
Scroll is the narrative axis
A story has an order. First this happened, then that, and here is why it matters. A dashboard has no order — every panel shouts at once, and the reader is left to assemble the plot themselves.
Scrolld treats scroll position as the timeline of the story. As you scroll, charts build themselves: axes draw in, series animate, annotations appear exactly when the text refers to them. The reader never has to choose between reading the words and reading the chart, because the two are synchronized by design.
One dataset, one argument
A Scrolld story makes one argument. That constraint is deliberate. When a page tries to say everything, it says nothing — so each section gets one chart, one claim, and the data that backs it.
This is also why stories are built from the data up. You bring a dataset, and the story engine works out what is actually in it: the shape of the series, the outliers, the turning points. The narrative is grounded in what the data shows, not in what a template assumed it would show.
Honesty as a design constraint
A chart that animates beautifully but exaggerates a trend is worse than a boring one that tells the truth. The engine defaults are chosen to avoid the classic distortions: baselines are not silently truncated, dual axes are not used to fake correlation, and missing data is shown as missing rather than interpolated away.
Data storytelling is still storytelling — but the data gets the final word.