Just a thought.. And timely given @peter it currently working on ST4 documentation.
I think when it comes to product documentation, there are always topics that need more than just documentation. They need a broader article or blog post that explains a collection of features that make up a 'topic' and then discuss strategies of how to use it depending on the desired outcome and in alignment with product design decisions (i.e. the product works this way because of X, Y, Z design decisions). This last part is important as many people won't under the 'why' of a product design decision until it is laid out, and helps people understand the constraints, risks, benefits, trade-offs, etc. they they can't see due to their narrower focus on solving their problem.
This topic (i.e. Queue management, how to navigate 'lists' with MIDI/Assigned buttons/Footswitches, etc.) comes up a lot, and I don't doubt it will continue to come up with new users (or current users expanding into MIDI/foot switches). I really think it is worthy of one of these broader topic explanations. By doing this, people get a better understanding of the product, how to use it more effectively, and (hopefully) reduces support emails/posts.