Tails documentation would greatly benefit from your help.
Good documentation is difficult to keep up-to-date. If you find a typo or an error in the documentation please let us know — ideally, by submitting a patch with your correction.
The documentation on the website is not freely editable. The way we document things has serious security implications. People should be able to trust the Tails website as much as they trust Tails itself. Furthermore, every change in the documentation possibly breaks the translations that were made of the previous version.
But there are still many ways you can start contributing:
Small fixes and enhancements to the current documentation are greatly welcome. This can be done by sending Git patches to email@example.com or by publishing a Git branch (for example to a fork on GitLab). In general, documentation changes should be based on the
Documentation writers coordinate themselves on firstname.lastname@example.org mailing list, our development mailing list.
Documentation writers should also read our documentation guidelines.
New documentation should be wrapped to 80 characters; however, please do not submit patches that merely re-wrap existing text, as this makes it harder to read the git history.
We recommend you to build an offline version of the documentation to test your contributions before sharing them with us.
Images on our website are compressed and cleaned using the compress-image.sh script. To run this script you need the
For example (run from Tails' source root):
Creates a QR code in tails_boum_org.png. And:
You can subscribe to email@example.com, our development mailing list.