About a year ago, we started grappling with the problem of long articles. Sometimes, a short article just wouldn't cut it--you need a lengthy onboarding guide or a long procedure that has a lot of content. The question became, "how can one best present lengthy content to the end user?"
Because if articles are too long, they force the reader to endlessly scroll down the page. All of that scrolling can be confusing, and readers can quickly lose track of what they are even looking at. So we wanted to fix that.
One option was to split the article up into multiple articles in a manual. This approach would let a reader finish an article, and then hit next. The problem we saw was that, often times, readers would either land in the middle of a lengthy process (from searching a keyword the knowledge base and clicking on an article), or they would get lost somewhere in the process and lose track of where they were.