]> git.proxmox.com Git - pve-docs.git/blame - howto-improve-pve-docs.adoc
fix #1959: remove any information regarding 'auto'
[pve-docs.git] / howto-improve-pve-docs.adoc
CommitLineData
3ef512ec
DM
1[[howto_improve_pve_docs]]
2Improving the Proxmox VE Documentation
3--------------------------------------
3ef512ec
DM
4ifdef::wiki[]
5:pve-toplevel:
6endif::wiki[]
7
8Depending on which issue you want to improve, you can use a variety of
9communication mediums to reach the developers.
10
1d9109f0
DC
11If you notice an error in the current documentation, use the
12http://bugzilla.proxmox.com[Proxmox bug tracker] and propose an
3ef512ec
DM
13alternate text/wording.
14
15If you want to propose new content, it depends on what you want to
16document:
17
18* if the content is specific to your setup, a wiki article is the best
19option. For instance if you want to document specific options for guest
20systems, like which combination of Qemu drivers work best with a less popular
21OS, this is a perfect fit for a wiki article.
22
23* if you think the content is generic enough to be of interest for all users,
24then you should try to get it into the reference documentation. The reference
25documentation is written in the easy to use 'asciidoc' document format.
26Editing the official documentation requires to clone the git repository at
100194d7 27`git://git.proxmox.com/git/pve-docs.git` and then follow the
470d4313 28https://git.proxmox.com/?p=pve-docs.git;a=blob_plain;f=README.adoc;hb=HEAD[README.adoc] document.
3ef512ec
DM
29
30Improving the documentation is just as easy as editing a Wikipedia
31article and is an interesting foray in the development of a large
32opensource project.
33
34NOTE: If you are interested in working on the {pve} codebase, the
35{webwiki-url}Developer_Documentation[Developer Documentation] wiki
36article will show you where to start.