Qt documentation is written by a small global team of technical writers and developers working at The Qt Company, complemented by a number of contributors from other parts of the Qt community. Since different parts of Qt are developed in different locations, writers with expertize in a particular area are typically co-located with the developers of that area. For example, the documentation for Qt Creator is written in Berlin.
Qt's technical writers are also responsible for many of the examples provided with Qt and related projects. However, the demonstrations provided with these projects are typically created by developers, and these are often not intended to be documented or supported by the Qt documentation team.
The documents in this category aim to cover the many aspects of Qt documentation creation, including the process we use to accept contributions from other community members.
Currently, Qt documentation is hosted at three sites:
- doc.qt.io: contains official releases
- snapshots: contains unreleased documentation from the Codereview repositories
- archives: contains legacy documentation
Contributing to Qt Documentation
Here are the basic steps to help you get started contributing to the Qt documentation:
- Familiarize yourself with the development process. In particular, the process of contributing code.
- Create a Jira account and set up your Gerrit environment.
- Download the Qt sources.
- Read the page regarding code reviews.
Style and Language Guidelines
Qt documentation adheres to the Microsoft Style Guide. The documentation follows American English grammar and spelling.
The Language Guidelines page provides further information about idioms and usage, punctuation and grammar issues.
Qt's documentation tool is QDoc. QDoc scans through the source and generates html pages regarding the classes, enums, QML types, and other parts of the reference documentation.
To get started, the QDoc Guide explains how QDoc generates documentation from QDoc comments.
QDoc Regression Testing
Submitting a Patch
The process for submitting a documentation patch is the same as for source code. For more information, read the Code Reviews page.
Approvers and Editors
For language reviews, documentation reviews, and technical reviews, you may add any of the relevant maintainers as reviewers as well as the following individuals:
- Andreas Eliasson
- Esa Törmänen (Qt for MCU documentation)
- Inkamari Harjula (Boot2Qt documentation)
- Jaishree Vyas (Qt Foundations)
- Johanna Vanhatapio (Qt Design Studio documentation)
- Leena Miettinen (Qt Creator documentation maintainer)
- Luca Di Sera
- Mats Honkamaa (Qt Design Studio documentation)
- Nicholas Bennet (Platform documentation)
- Paul Wicking
- Pranta Dastider (Qt Design Studio documentation)
- Safiyyah Moosa
- Topi Reiniö (QDoc maintainer)
- Venugopal Shivashankar
- Sze Howe Koh
For language reviews (particularly for non-native English speakers) only, you may also add any of the following individuals:
- Mitch Curtis
- Lorn Potter
- Edward Welbourne
For documentation help, join the #qt-documentation channel in Freenode.
Filing Documentation Issues
Anybody with a Jira account may file a bug. For documentation bugs, please file the issue and enter Documentation AND the relevant library or module in the Component field. The process of fixing code bugs also apply to documentation issues.
Before filing an issue, please check that it has not already been fixed in a later version of the documentation. The latest documentation snapshots are at doc-snapshots.qt.io
Modular Qt Documentation
The organization and development of modular Qt documentation is covered in another wiki: Qt5DocumentationProject
The Qt Documentation Structure page provides information about the structure of the documentation.
This category has only the following subcategory.