Make using and contributing to the docs more accessible

(QubesOS/qubes-issues#1714)

developers/contributing.md

@@ -19,6 +19,7 @@ First you should decide what you are interested in (and good in). The Qubes proj
 -   Code audit (e.g. gui-daemon)
 -   New features
 -   Artwork (plymouth themes, KDM themes, installer themes, wallpapers, etc)
+-   [Documentation](/doc/doc-guidelines)
 
 Perhaps the best starting point is to have a look at the [issues](https://github.com/QubesOS/qubes-issues/issues) to see what are the most urgent tasks to do.
 

developers/doc-guidelines.md

@@ -8,8 +8,8 @@ redirect_from:
 - /doc/DocStyle/
 ---
 
-Guidelines for Documentation Contributors
-=========================================
+Documentation Guidelines
+========================
 
 All Qubes OS documentation pages are stored as plain text files in the
 dedicated [qubes-doc] repository. By cloning and regularly pulling from

doc.md

@@ -13,8 +13,11 @@ redirect_from:
 
 The Basics
 ----------
+ *  [A Tour of Qubes OS](/tour/)
+ *  [Getting Started](/getting-started)
  *  [Users' FAQ](/doc/user-faq/)
  *  [Mailing Lists](/doc/mailing-lists/)
+ *  [Documentation Guidelines](/doc/doc-guidelines/)
  *  [Further reading: How is Qubes different from...?](http://blog.invisiblethings.org/2012/09/12/how-is-qubes-os-different-from.html)
  *  [Further reading: Why Qubes is more than a collection of VMs](http://www.invisiblethingslab.com/resources/2014/Software_compartmentalization_vs_physical_separation.pdf)
 
@@ -159,6 +162,5 @@ For Developers
  *  [Qubes OS Version Scheme](/doc/version-scheme/)
  *  [Supported Versions](/doc/supported-versions/)
  *  [Coding Guidelines](/doc/coding-style/)
- *  [Documentation Guidelines](/doc/doc-guidelines/)
  *  [Books for Developers](/doc/devel-books/)
  *  [Qubes OS License](/doc/license/)