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
2016-01-13 15:41:39 -05:00
basics Fix a few typos 2016-01-10 18:41:30 -05:00
common-tasks Fix a few (of my own) typos 2016-01-13 15:41:39 -05:00
configuration Fix a few typos 2016-01-10 18:41:30 -05:00
customization Fix a few typos 2016-01-10 18:41:30 -05:00
developers Fix a few (of my own) typos 2016-01-13 15:41:39 -05:00
hardware fixed typo 2015-12-17 18:16:38 -05:00
installing Rewrite R3.1 in-place upgrade page for accuracy and clarity 2016-01-13 01:04:51 +00:00
managing-os Fix a few typos 2016-01-10 18:41:30 -05:00
privacy Fix a few typos 2016-01-10 18:41:30 -05:00
reference Fix a few typos 2016-01-10 18:41:30 -05:00
releases Remove issues already fixed in 3.1-rc2 2016-01-12 23:26:29 +01:00
security Fix a few typos 2016-01-10 18:41:30 -05:00
troubleshooting fixed broken /en/ links 2015-12-09 16:29:45 +00:00
unsorted Remove en/ from URLs (QubesOS/qubes-issues#1333) 2015-10-28 22:14:40 +00:00
doc.md Remove duplicate TorVM entry 2015-12-29 05:32:23 +00:00
README.md Update README 2015-11-08 01:05:45 +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. Contributions to the documentation (both new content and edits of existing content) are welcome. To contribute, please fork and clone this repo, make your changes, then either submit a pull request or send a patch to the qubes-devel mailing list. If you have a GitHub account (free), you can simply browse this repository and edit the files here. The GitHub interface will automatically guide you through the fork and pull request process.

Markdown Conventions

All the documentation is written in Markdown for maximum accessibility. When making contributions, please observe the following style conventions:

  • Use spaces instead of tabs.
  • Hard wrap Markdown lines at 80 characters.
  • Hard wrap Git commit message lines at 72 characters.
    • This leaves exactly four spaces on each side of the commit message when viewed in the default git log format.)
  • If appropriate, make numerals in numbered lists match between Markdown source and HTML output.
    • In the event that a user is required to read the Markdown source directly, this will make it easier to follow, e.g., numbered steps in a set of instructions.
  • Use hanging indentations
    where appropriate.
  • Use underline headings (===== and -----) if possible. If this is not possible, use Atx-style headings on both the left and right sides (### H3 ###).
  • Use [reference-style][ref] links.

[ref]: http://daringfireball.net/projects/markdown/syntax#link