All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
Go to file
stubbybubby 3db69ad702 Rewrite parts of usability-ux.md
This proposed file changes probably includes some content changes, but ones I hope you'll immediately agree with because the result is a more accurate article.

Among other things,
* Removed unnecessarily prudent logical connection phrases like "thus," and just replaced them with "because" and "as a result" where I could.
* Moved some sentences or clarifications to their proper sections, e.g. moved the "Despite this rule, some acronyms..." line to the Avoid Acronyms section.
* Removed some sentences (like "Additionally, security focused software has the responsibility of providing safety to the user and their data") that, while true, without proper context did not seem relevant to the article.
* Removed some phrases that repeated known contextual information like "of usability and experience" in "if you are interested in furthering your understanding of usability and experience" or "which are shown to a user" in "notifications which are shown to a user".
* Introduced some clauses or phrases that clarified information, like adding "of those mentioned" to "All three desktop environments have their own human interface guidelines,"
* Merged the Avoid Repetitive Tasks and Minimize Repetitive Steps sections.
* Rewrote some sentences that were incomplete or didn't make sense into what I assumed the writer intended to say.
* Inserted possessive's' when they were necessary, and turned bigger sentences into smaller ones using possessives when I could ("notification messages presented to user" --> "user's notification messages")
* Grammar edits
* Compartmentalized run-on sentences.

This was a pretty big edit, so you'll probably disagree with some of the changes. Just explain what you want to be re-done or where my edits changes an important meaning/formed an inaccuracy and I will make another commit.
2017-04-02 11:57:54 -07:00
basics_dev Rewrite parts of usability-ux.md 2017-04-02 11:57:54 -07:00
basics_user Edit doc-guidelines.md 2017-04-01 08:53:06 -07:00
building Remove outdated instructions for building PVUSB 2017-03-16 09:05:17 -04:00
common-tasks Fix headers 2017-03-21 19:05:09 -07:00
configuration Quality over quantity 2017-03-16 04:34:47 -04:00
customization bind-dirs: Missing ro path limitation is being fixed 2017-03-27 12:21:33 +02:00
debugging Adjust headings for auto-ToC and uniformity 2016-11-22 03:03:51 -08:00
hardware Drop obsolete hint (no more multiple kernels) 2016-09-25 01:25:57 +02:00
installing Fix link to Reflections on Trusting Trust paper 2017-03-31 12:00:33 -04:00
managing-os Update information on Ubuntu builds 2017-03-18 03:44:01 +00:00
privacy Delete Onion Service Repos page 2017-02-15 05:46:19 -08:00
reference Fix typo 2017-03-28 17:48:01 -07:00
releases Add Fedora 23 EOL and 24 upgrade instructions to 3.2 release notes 2017-03-05 21:01:15 +00:00
security Directly link to HCL 2017-03-21 15:54:32 -04:00
security-info Add notes regarding embargoed XSAs and unused XSA numbers 2017-03-21 18:02:03 -07:00
services mgmt1: fix table syntax, adjust mgmt.pool.add argument 2017-03-10 01:08:34 +01:00
system Reorganize security info pages 2017-03-18 19:31:12 -07:00
troubleshooting Remove redundant string (closes #309) 2017-03-09 08:41:55 -08:00
CONTRIBUTING.md Update CONTRIBUTING.md 2016-10-19 16:26:57 -07:00
doc.md Add new testing page to doc index 2017-03-20 18:38:48 -07:00
README.md Fix typo 2016-03-22 22:52:54 +00:00

Qubes OS Documentation

Canonical URL: https://www.qubes-os.org/doc/

All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.

For more information about the documentation, including how to contribute, please see the Documentation Guidelines.