- Revamp intro to make it (hopefully) more user-friendly
- Generalize last section into "Unofficial venues"
- Warn that we do not monitor or moderate unofficial venues
- Warn more explicitly about possible Qubes team impostors
- Miscellaneous updates and improvements
- Improve section organization
- Improve new issue instructions
- Add section on "projects"
- Convert final section into "How issues get closed"
- Add section on backports (closesQubesOS/qubes-issues#6655)
- Rename to "Issue Tracking" (file rename in separate commit to preserve
history)
- Break the "Important" section up into multiple shorter sections in an
attempt to discourage people from skipping over it
- Add "How to open a new issue" section
- Add "Labels and milestones" section
- Update heading syntax
- Create new "Command-line interface" section
- Move warning about direct commands to new section
- Move info about qubesctl commands and testing repos to new section
- Revise "Upgrading" section
- Improve intro
- Make key instruction steps harder to miss
- Add "Troubleshooting" section
- Move text on updating standalones to "Standalones and HVMs"
Based on examining the AwesomeWM project's web presences and Wikipedia
entry, there does not appear to be a single consistent name by which the
project refers to its window manager. All three of these variations are
used: "awesome", "Awesome", and "AwesomeWM". In order to avoid ambiguity
with the regular English word, we're opting for "AwesomeWM" in our own
documentation.
This commit also reverts the change to the widget image, since that
change was not necessary (see #1161).
Finally, this commit adds links to the KDE, i3, and AwesomeWM pages.
- Updated image to match wording to names shown above
- Edited "custom" to "unique" wrt "unique to qubes," as sdwdate is not custom _to_ qubes, but is unique(ish) to Qubes.
- Included bullet for Whonix widget, w/ link-out
- Capitalized "A" on Awesome in desktop environments
This eases the doc maintenance burden by allowing bulk operations on
*.md files without missing intended files (whereas attempting to perform
such operations on *all* files can be dangerous due to hidden git files,
for example). Since HTMl can validly be embedded in Markdown files, this
doesn't affect the way the pages are rendered.
