Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-26 07:49:34 -05:00
Code Issues Packages Projects Releases Wiki Activity
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.
6,337 Commits 5 Branches 2,526 Tags 87 MiB
Makefile 51.8%
Python 48.2%
9d390bdb0d
Go to file
Andrew David Wong 9d390bdb0d
Use Markdown syntax instead of HTML 
Although the HTML tags are technically correct, it's probably more
important to preserve source readability and avoid the problems that
HTML-in-Markdown poses for localization and offline documentation.
2021-07-06 02:06:50 -07:00
_dev Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
developer Capitalize second word in title case compound adjectives 2021-07-03 15:43:16 -07:00
external Revert "Remove instances of title: from YAML headers" 2021-06-15 23:19:45 -07:00
introduction Wrap text; improve wording 2021-07-05 05:35:57 -07:00
project-security Update Qubes Forum URLs 2021-07-01 07:03:05 -07:00
user Use Markdown syntax instead of HTML 2021-07-06 02:06:50 -07:00
.gitlab-ci.yml gitlab-ci: use local project reference 2020-11-27 03:55:05 +01:00
.travis.yml Update travis to bionic 2020-09-29 15:12:04 +02:00
CONTRIBUTING.md Update heading syntax; wrap text 2021-06-19 20:24:57 -07:00
doc.md Update layout 2021-06-22 04:27:32 -07:00
README.md Update heading syntax; wrap text 2021-06-19 20:26:51 -07:00

README.md

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.