I feel like whoever did the web-ui for that article needs to (re)read this: http://bost.ocks.org/mike/scroll/ rather than mimicing it poorly (previous HN discussion: https://news.ycombinator.com/item?id=8551724)

For example here is another article that has much better scroll behaviour and provides a much better smoother user experience (at least on my machine):

http://www.nytimes.com/newsgraphics/2013/10/27/south-china-s...

Particularly when the images appear, on the nytimes article text keeps scrolling providing continuous feedback, in the wsj article opacity slowly changes, which is a lot harder to notice, and made me think for a second that the page got stuck, plus forced me to scroll a lot to move the page forward.

I guess the general rule of thumb is that text scrolls up the page as normally as any other website (albeit with perhaps more spacing between paragraphs on image / video dense pages), and images/videos will fade in and out in the background using a fixed position. Then when it's a dense text-only section the image will lock into the top/bottom of the text block and scroll with it.

Still a really good article! Good to see market solutions are developing in response to over-fishing problems.

There are ways of doing scroll-based storytelling right but this ain't it. This library does have the right idea that scrolling should be continuous, but if you over- or underscroll the content you get trapped in a weird middle ground of a tween between two states, and it's frustrating to exactly line up your viewport to the content so it's readable.

Mike Bostock wrote a pretty good post about scroll-based storytelling last year: http://bost.ocks.org/mike/scroll/ https://news.ycombinator.com/item?id=8551724