Module documentation

Documentation for a subproject as a whole, as well as packages in that subproject, can be provided as separate Markdown files.

File format

Inside the Markdown file, the documentation for the subproject as a whole and for individual packages is introduced by the corresponding first-level headings. The text of the heading must be Module <module name> for a subproject, and Package <package qualified name> for a package.

The file doesn't have to contain both subproject and package documentation. You can have files that contain only package or subproject documentation. You can even have a Markdown file per subproject or package.

Using Markdown syntax, you can add:

Headings up to level 6
Emphasis with bold or italic formatting
Links
Inline code
Code blocks
Blockquotes

Here's an example file containing both subproject and package documentation:

# Module kotlin-demo

This content appears under your subproject name.

# Package org.jetbrains.kotlin.demo

This content appears under your package name in the packages list.
It also appears under the first-level heading on your package's page.

## Level 2 heading for package org.jetbrains.kotlin.demo

Content after this heading is also part of documentation for `org.jetbrains.kotlin.demo`

# Package org.jetbrains.kotlin.demo2

This content appears under your package name in the packages list.
It also appears under the first-level heading on your package's page.

## Level 2 heading for package org.jetbrains.kotlin.demo2

Content after this heading is also part of documentation for `org.jetbrains.kotlin.demo2`

To explore an example project with Gradle, see Dokka gradle example.

Pass files to Dokka

To pass these files to Dokka, you need to use the relevant includes option for Gradle, Maven, or CLI:

Use the includes option in General configuration.

If you are using command line configuration, use the includes option in Source set options.

If you are using JSON configuration, use the includes option in General configuration.

18 December 2025