Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-01-13 16:29:59 -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.
5,958 Commits 5 Branches 2,526 Tags 87 MiB
Makefile 51.8%
Python 48.2%
401447bcde
Go to file
Andrew David Wong 401447bcde
Encourage users to stay informed of QSBs 
- Add "Next steps: Security" section to installation guide
 - Add social media section to support page, as a way to receive news
   updates

Discussed in:
 - QubesOS/qubes-issues#6299
 - https://qubes-os.discourse.group/t/safety-when-forced-not-to-use-updater/2085
2021-01-03 08:08:37 -08:00
_dev Use HTTPS everywhere (mechanical edit using util from https-everywhere) 2020-12-19 19:57:07 +01:00
developer Add info on adding and updating community links in ToC 2020-12-25 08:21:46 -08:00
external Fix links 2020-12-21 08:22:40 -08:00
introduction Encourage users to stay informed of QSBs 2021-01-03 08:08:37 -08:00
project-security Define "QSB" 2021-01-03 08:06:53 -08:00
user Encourage users to stay informed of QSBs 2021-01-03 08:08:37 -08: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 Fix link 2017-04-04 21:52:06 -07:00
doc.md Update Index's Split SSH link 2020-12-30 01:46:54 +00:00
README.md Fix typo 2016-03-22 22:52:54 +00: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.