I’m afraid the Qubes documentation is the only source to learn with and yes, you always can ask questions here.
- So first is to connect the qubes together in the Qubes manager, so you’re getting internet for every qube you want. Means: sys-net is the qube which handles the internet, followed by sys-firewall (which is getting internet through it’s netVM called sys-net), followed by personal [/work/sys-whonix/mostly all other qubes except anon-whonix, templates and vault] (which is getting internet through it’s netVM called sys-firewall).
- anon-whonix has sys-whonix as it’s netVM for Tor net & vault don’t have any netVM, like all the templateVMs
So the two main examples for this are:
INTERNET > sys-net > sys-firewall > [a vpn qube] > personal (/work /bank /standalone qubes like Windows10/11)
TOR NET > sys-net > sys-firewall > sys-whonix > anon-whonix
- updates always with the Qubes Updater tool under Start > Qubes > Qubes Updater
- installs of newly tools/apps and programs always via terminal commands (sudo apt-get install… for Debian based templates & sudo dnf install… for Fedora-based templates) in templateVMs
- in the default installation, you can use your qubes (personal/work/bank/anon-whonix) on basis of three underlying templates → one for Debian, another for Fedora and the third for whonix(-ws) - it depends on you which distros you’re more familiar with. Whonix is set for all tor-related. Debian is the distro for much tools with older date, but stable. Fedora is the distro for much newly created and updated stuff, which mostly just had a shorter testing time, which seems to be stable in most of the cases.