Category:Developing Qt::Documentation: Difference between revisions

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 expertise in a particular area are typically co-located with the developers of that area.

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.

Documentation Snapshots

Currently, Qt documentation is hosted online at:

• doc.qt.io: contains official releases
• snapshots: contains unreleased documentation from the Codereview repositories
• archives: contains legacy documentation

Also, when installing a version of Qt and Qt Creator, an offline documentation set of that particular release is included.

Setting Up for Documentation Writing

Here are the basic steps to help you get started contributing to the Qt documentation:

1. Familiarize yourself with the development process. In particular, the process of contributing code.
2. Create a Jira account and set up your Gerrit environment.
3. Download the Qt sources.
4. Read the page regarding code reviews.
5. Start by contributing small fixes. Don't hesitate to ask for help!

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. It is possible to create a documentation set for Qt modules and tools.

• QDoc Manual
• QDocRegressionTesting - how to test the Qt documentation set
• Building Qt Documentation

Writing Guidelines

The Qt Writing Guidelines can with creating and editing Qt documentation. We adhere to it for consistency and to create a singular voice. We also follow the QUIP system and follow the requirements regarding examples and images.

• Qt Writing Guidelines

Getting Help with Editing

The process for submitting a documentation patch is the same as for source code. For more information, read the Code Reviews page.

For documentation reviews, you may add the following for reviews:

Qt Oslo - Qt Reference Documentation and QDoc:

• David Boddie
• Andreas Eliasson
• Safiyya Moosa
• Jerome Pasion
• Topi Reiniö (QDoc maintainer)
• Luca Di Sera
• Venugopal Shivashankar
• Paul Wicking

Qt Berlin - Qt Tools (Qt Creator, Qt Assistant, and others), Foundations team

• Leena Miettinen (Qt Creator documentation maintainer)
• Jaishree Vyas (Qt Foundations)

Qt Oulu - Qt Products

• Esa Törmänen (Qt for MCU documentation)
• Inkamari Harjula (Boot2Qt documentation)
• Johanna Vanhatapio (Qt Design Studio documentation)
• Mats Honkamaa (Qt Design Studio documentation)
• Nicholas Bennet (Platform documentation)
• Pranta Dastider (Qt Design Studio documentation)
• Teea Põldsam (Qt Design Studio and Qt License Server documentation)

Also, the following people can help with English and technical reviews:

• Mitch Curtis
• Lorn Potter
• Edward Welbourne
• Sze Howe Koh

Filing Documentation Issues

Anybody with a Jira account may file a bug. For documentation bugs, please file the issue and fill in the Component field with Documentation and the relevant Qt library or tool. 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

Documentation Structure

The Qt Documentation Structure page provides information about the structure of the documentation.