- Cleared misunderstandings of disposable templates, this word was
sometimes used interchangeably with disposables;
- Deduplicate content as much as possible;
- Reference other pages or previous sections;
- Assume the user has read the previous sections up until the
current section they are reading;
- All this deduplication enables easier reading, less clutter, but
each section doesn't stand by itself, each page does. Some things
were reinforced on multiple sections, but limited to when
extremely necessary to learn by reinforcement;
- Structure the files to their distinct use cases:
- how-to-use-disposables is just the basics to learn what are
disposables and how to use them, using GUI and CLI alternatives;
- disposable-customization has everything advanced related to
disposables, such as advanced usage, creation of disposables
templates, their customization;
- disposable-implementation assumes the user understand the previous
pages and contains a more technical description of disposables and
preloaded disposables as well as their implementation;
- Prepared usage for a GUIVM setup, avoiding mentions to dom0;
- Usage modes has been organized in GUI first and CLI second, grouped by
origin such as GUIVM and app qube;
- Usage page restricts itself to "default-dvm", it's name is not
variable like the Whonix disposable template variant and it is the
most used disposable template, thus we avoid variables replacement
that the user should think of the value to a definitive value to use
when learning. Customization page could not benefit much from this
though, as it is intended to create alternative disposable templates;
- Usage page links to Tails documentation of why using it on a VM is not
amensiac, so it can be referenced for users that ask to have Tails in
a VM for anti-forensics purposes;
- Updated the images to R4.3, nobody deserves to see the Qubes version
of the Xfce application menu anymore when the new app menu rocks. The
images also had to be updated because it was fullscreen screenshot
on a large resolution, making it very difficult to read unless
opening the image in a new tab and zooming in;
- Implementation page shows preloaded disposables alternatives that were
once used or considered as a comparative for future studies, to answer
why a different option is not being used and what requirements a
replacement must meet;
- Content from previous releases have been deleted;
- Updates to Qrexec policy v4;
- Use rST roles;
- Change non-ASCII quotes and em-dashes to ASCII;
- Standardized text writing style, many people have contributed to these
pages over the years, there is a lot of different writings styles
which make the text difficult to map. I rewrote a lot of the
paragraphs to my liking and understanding of the different stages that
a user may go through when using disposables, and even on paragraphs
that I didn't completely write, it was modified to follow the same
standard with the rest of the pages. The usage must be very simple
with just the basics, we don't want to scare the user's off of using
disposables, we want to convince them. The customization is a bit more
advanced, it assumes a lot more knowledge from the user to make
decisions by themselves such as customizing applications and qube
settings, which can affect system security. The implementation details
do not require reading the code, it just exist to explain what is
being used and why it was chosen.
Fixes: https://github.com/QubesOS/qubes-issues/issues/10282
For: https://github.com/QubesOS/qubes-issues/issues/1512
Previous link expected a label called "T: bug" and "release-notes, which
no longer seem to exist. They were respectively converted to "type:
task" and "release notes" (without dash)
The incidental urlencoding (removal of some '+' should not make a
difference as far as links are concerned).
With duplication, inconsistencies appears, such as:
- Poetry did not have a version check of sphinx-build;
- Poetry did not discern between git clone and fetching other
dependencies;
- Virtual environment and poetry documentation were different already;
- Build instructions sometimes used "qubes-doc" or "../qubes-doc".
New structure introduces sections to separate installation, lint and
build process.
1. Add CLI tools usage examples and references to documentation
2. Minor styling in Command-line interface section: make writing a bit more concise, use numbered nested list
The new header in `resize-disk-image` is far from perfect but it allows
us to enable nitpicky mode by default, so that any contributor is warned
about missing references when building the docs.
* as [mentioned on the
forum](https://forum.qubes-os.org/t/version-4-3-0-rc3-not-available-incoherent-with-documentation/36843/6),
the 4.3 schedule was wrong, so I removed the rc3 date.
* more links to the website news page should help users to figure out
what the latest release candidate available is.
* I created a direct reference to a useful header on version-scheme.rst
and updated the text and the references
* There is a minor formatting improvement on the version-scheme.rst and
a link to the schedule of R4.1 to provide a concrete example.
Btrfs mount options are per whole filesystem, not per mountpoint. If a
filesystem (or a subvolume inside of it) is mounted a second time, the
second set of mount options such as compress= will not be applied.
https://btrfs.readthedocs.io/en/latest/ch-mount-options.html
