> For the complete documentation index, see [llms.txt](https://boomi.markusschmidt.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomi.markusschmidt.pro/boomi-console/commands/comp-components/create-doc.md).

# DOC

Create Markdown documentation and process UML diagrams

Create documentation for the specified components.

```batch
bc create doc {Source}
```

{% content-ref url="/pages/UwgQlsv5NdeY5UDGw3jr" %}
[COMP DOC Arguments](/boomi-console/commands/arguments/comp-arguments/comp-doc-arguments.md)
{% endcontent-ref %}

## Documenting a single Component

```batch
bc COMP DOC /c {yourComponentId}
```

The simplest form of creating documentation is to document a single component. The documentation is created in the Markdown format and stored in the *Out/Doc* folder.

You can *preview Markdown* documents directly in Visual Studio Code:

<figure><img src="https://856602315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJ5pAMZk3evA8VCVuQL%2Fuploads%2Fgit-blob-fc5ad4f8bccda6a6a501227348939973859bb42d%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

{% file src="/files/ZzYvwQZkWGTALR0SN0Rp" %}
An PDF example containing a process documentation (printed Markdown)
{% endfile %}

### Documenting a Packaged Component

By using the [Common Arguments](/boomi-console/commands/arguments/common-arguments.md#packageversion-pv) or [Common Arguments](/boomi-console/commands/arguments/common-arguments.md#packageid-p) arguments you can quickly document a packaged component. This will also create a nice *readMe* file for the package content.

<figure><img src="https://856602315-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJ5pAMZk3evA8VCVuQL%2Fuploads%2Fgit-blob-aa6bad0b5c6c24954c82dcac379631c1974e4963%2Fimage_6.png?alt=media" alt=""><figcaption><p>.\doc\_packageVersions\2024-07-23-msc.01m.md</p></figcaption></figure>