I think that would be unworkable tbh, exactly because the line is
There are some things that are straightforward, and the Qubes element small:
How do I install libreoffice? The Qubes part here is
do it in the template
There are some things that are all Qubes:
How do I move files between qubes?
How do I get rid of the prompt when copying files between qubes?
How do I install programs in dom0?
Then there’s the rest, where the Qubes element may (or may not) be large.
Lets’ take an example:
How do I get WiFi working with a Realtek 8852AE?
Here, you have to build and install drivers from source: complicated
enough, and needs kernel headers. The Qubes part here is quite large
because you will have to understand templates, load (and use) a native
kernel, or consider using a standalone.
See? In that last case you can find instructions for the build, but you
need Qubes knowledge to understand where to best build the modules,
how to use a native kernel, and so on.
The complexity of that is determined by the specific WiFi card. If it
were an AR5BHB116, it would be category 1.
In many cases I see people posting questions where the answer is
either RTFM or STFW. In many cases, the Qubes element is small.
Why is this? I think at least part of the answer is that there is a
perception that Qubes is complicated, and difficult, and so users (even
“Linux savvy IT_sec professionals”) start with that expectation, and
think finding a solution will be beyond them. (That, and laziness.)
In my experience, if users are trained not to think that Qubes is
hard, they don’t find it hard. It helps if they know their limits, and
have support they can call on.
Need I say, that this is my opinion, and I don’t speak for Qubes?
(And @fiftyfourthparallel, nothing here is aimed at you.)