Please go ahead and summarize some ideas in this thread!
I honestly think the best possible starting-point output, would come from an asynchronous workshop… in a tool that allows for post-it-note fidelity-level rearranging of information in small bits. Bits that are visual and prevent participants from writing sentences upon sentences, or getting too granular into detail—and allow for easy moving-around of parts and creation of more parts. All of which can be visible at once. Which is why post-its on big blank walls are so delicious.
Most of my participation I think, should just be in moderation—as I am not a power user of Qubes, but am very aware of where non-Linux-native users have struggled in their adoption and learning curves. I’m also a UX practitioner by trade, and can setup some guiding principles and guardrails to guide others in actually “Creating” the goods. If that makes sense.
Once that workshop is completed and there’s a solid group consenssus around what a 10,000ft view should look like, drafting in a wiki can begin.
I posted this in the other thread, but will share again here as a reference point. In regards to how information is “bucketed” hierarchically, and nicely segmented into cognitively accessible bites—UXPin’s documentation is a good example I’ve been using a lot lately for the App Menu redesign project: https://www.uxpin.com/docs/getting-started/downloading-and-using-uxpin/