Whonix vs Qubes Docs

[Patrick]

@entr0py

Don’t understand how that argument supports movement of any docs. Given that Whonix software is bundled with Qubes (and not required to be integrated completely), can’t they likewise simply bundle Whonix’s offline docs with Qubes offline docs? Formatting issues? Quality issues? Licensing?

There is no Whonix offline documentation. It is an unsolved issue.

https://forums.whonix.org/t/offline-documentation-discussion

That is the problem.

Also, “move” for bridges would mean “duplicate”. Since Non-Qubes-Whonix users still need these docs. And duplication is awful. Changes will be made in one but not the other, so merging gets difficult.

Rather than making all of Whonix’s documentation accessible in offline documentation, it would be simpler to do that just with a single page. (That will need manual fixes to make ti readable, but much more doable for 1 page than the whole wiki.)

@Ego

As when the Whonix documentation is more readable it could simply be combined with what the Qubes team plans and coexist, at least from my point of view.

Yes, if the Whonix mediawiki offline documentation can be sorted out.

Or, I was also wondering… In case we port (might be considered in future, but really no strong plan for now) Whonix documentation from mediawiki to jekyll, then it would be simple to add more, most or even all of Whonix documentation to Qubes jekyll based website. The Whonix documentation would be just have a few unique pages such as Whonix homepage, Whonix documentation, Whonix help and such. Probably not so simple to due links. And non-perfect.

The Qubes documentation would, I am sure, demand to leave aside “if you are using Qubes-Whonix” and “if you are using Non-Qubes-Whonix”.

Short discussion on jekyll:
splitting Whonix documentation into a short and long edition for better usability - #11 by Ego