Qt Writing Guidelines

The Qt Writing Guidelines contains information about writing Qt documentation in a consistent way. Though there are exceptions, maintain the consistency level outlined in the guidelines or the existing Qt documentation.

This guideline is maintained by the Qt Documentation Team, with members across the different Qt Group sites. Visit their page at: Category:Developing Qt::Documentation

Language Style

We use the Microsoft Writing Style Guide in the Qt documentation. Essentially, use clear and direct language in American English. We write to a diverse audience and we need to communicate Qt topics in an approachable and understandable manner.

Here are some specifics for Qt:

1. Use active voice, not passive. Passive does not make a sentence formal, but unnecessarily weakens the sentence. See Verbs
2. Use the pronoun you in to address the reader when appropriate. See Nouns and Pronouns.
3. Use because instead of "since" or "as". See Use simple words, concise sentences.
4. Use a serial comma, also known as the Oxford comma. See Commas
5. Use the correct spelling and case for Qt Products. See Qt Terms and Concepts
6. Use US spelling and avoid latin abbreviations. See Use US spelling and avoid non-English words. Here is a summary :

Use	Instead of
that is	i.e.
namely	viz.
therefore	ergo

New in Qt 6.8, the Qt Reference Documentation is available in translated formats. Think about how translatable the sentence you are writing. If it is too complicated, then

it may confuse the reader, even if it is English.

Tip: Say the text out loud. If it sounds weird, then it is weird...then it may also be wrong.

Vale Support

Vale is a linter that detects improper use of language and can make suggestions in-place. Vale has command-line interface and is also available for Qt Creator and VS Code

For more information about Vale, visit Setting Up Vale.

Writing API Documentation

We document Qt APIs in the sources and use QDoc to generate the HTML for the doc.qt.io site and an offline version for Qt Creator.

C++ and QML documentation follow a similar style, but there are differences. See the following pages for documenting APIs.

• C++ Documentation Style
• QML Documentation Style

For designing Qt APIs, visit:

• API Design Principles

Using QDoc to Write Documentation

These QDoc guidelines complement the QDoc Manual

• Style Guidelines - proper use of commands, code blocks, markup, and indentation
• Linking Guidelines
• QDoc Project Templates
• Checklist for Adding Documentation for a New Module
• Documentation Structure page contains a map of how the directory structure of a repository or module should be

Documenting Examples

• Examples and Tutorials Style - writing example documentation and tutorials
• Integrating Examples - configuring an example for integration into the Qt repositories
• Qt6/Example-Guideline - do's and don'ts for examples

Writing Example Documentation and Tutorials

Contributing Examples to Qt

Qt Examples Guidelines

Including Images

The requirements for images in Qt documentation is outlined in QUIP-21.

• QUIP-21 Using images in Qt documentation

Qt 5 Documentation Requirements

For Qt 5 documentation, or those who create documentation using Qt 5, see the following pages:

• Qt 5 Documentation

QDoc changes should pass the QDocRegressionTesting

Using Images in Documentation

It can be useful to include images in documentation, such as screenshots, diagrams, icons, or even animated images and embedded YouTube videos. QUIP-21 describes the requirements and considerations for use of images in Qt's documentation.