miniblog.

rust-analyzer has a really cute feature "highlight related". It will highlight the enclosing loop when cursor is on `break`, or the enclosing `async` when cursor is on `await`:

Online videos are often a great historical reference for obsolete computer games, because they show the game in context of an active community: https://www.rockpapershotgun.com/2019/05/06/how-youtube-lets-plays-are-preserving-video-game-history/ (I suppose this also applies to MUDs and online communities that aren't gaming related.)

I'm coming round to the view that optimum documentation is one web page per function. This gives you space for prose, examples, related functions, version history and even user comments! It's not the norm though, and requires substantial content writing.