The windows documentation is probably not “harmful” but it doesn’t seem really helfpul either.
We strive to follow the principle of merging PRs that are net improvements, even if they fail to comply with some policies, because the docs are still better off. (This is an instance of not allowing the perfect to be the enemy of the good.) PR #1190 is an example where an exception to the usual release-specific doc policy was made.
I’ll add that “suboptimal” is better than nothing: well-formatted, typo-free, detailed instructions like most of the official/qubes-community docs take a very large amount of time to write (been there); in comparison the forum makes it easy to contribute quick-and-dirty instructions, which could potentially make their way into a qubes-comunnity or official doc after a few rounds of refining. But an issue with forum posts/guides is visibility - ie. how to search/find them (for instance in hindsight the title I’ve picked for this windows post could be improved). IMHO that’s where it would make sense to link forum posts that are deemed helfpul in the official/qubes-community docs (obviously with a “work in progress / use at your own risks” header); for seemingly such popular tasks as creating a windows qube this will definitely save people some time, rather than loosing time following outdated instructions.
[offtopic - here’s an illustration: the current rpc policy doc isn’t relevant to 4.1; this article describes the new format but it’s not easily found (at least it wasn’t for me) and being almost 2 years old it isn’t clear if something changed while coding 4.1’s policies. A “suboptimal rather than nothing” approach would be to add a quick-and-dirty note at the top of the current doc with a link to the article, until somebody spends much more time reformatting the whole document and dealing with PRs back-and-forth (the “good”/“perfect” but time-consuming approach). I considered sending a short PR but there’s always this idea that official qubes docs are too well written to allow that kind of “kludge” ; what’s your position ?]
We don’t expect to have a new documentation system with support for release-specific docs for a while. (It’s being worked on.)
Ah, nice - I’ve just read related posts/issues, good to see there’s some progress in that area !
(and thanks for your detailed reply btw).