Started on improving existing Qubes documentation, or started on putting together a “Simple User Guide” discussed in this post?
I somewhat dropped the ball 9 weeks ago, offering to put together an asynchronous workshop and then just being perpetually too overworked to dedicate time to that. I still want to do that, but also don’t want to roadblock others excited to contribute to something, now.
I feel there are a few main points around which to orient this work, that should be defined up-front:
- Who is this for (needs, motivations, existing skills)?
- Who is this not for (needs, motivations, existing skills)?
- What principles do we desire for content to align against?
After or in parallel to that, I’d suggest drafting an outline of topics to then write documentation against.
After or in parallel to that, if there’s a topic you feel excited to just dive on into, go for it!