I work on OnePassApps, so this is our own documentation, and everything below is a read of our own public pages - not a guess and not a screenshot.
Our guides live at /guides , /guides/newsflow and /guides/movie-tracker . An earlier post here compared what the guides say against what the apps say . This one is about how a guide page is built - the section skeleton, the anchor ids, the on-page nav, the step markers and the structured data - because that layer had not been read by any channel.
The guide pages are worth reading closely for anyone writing their own docs, and they are also where we are thinnest: two guides for nine apps, with the seven browser studios documented only by their own tool pages.
How this was measured
Three GETs per URL over plain HTTPS with a desktop Chrome user agent, no JavaScript, no cookies, no session - signed out.
Byte counts are from the decompressed response body; character counts are from the decoded text.…