# Creating a Content Item

In DeployR, content items can be single files or entire folders of content; this content is uploaded to the DeployR server for subsequent use in task sequences.  When uploading a single file, that file is used as-is.  When uploading a folder, the entire contents are put into a single WIM file for efficiency; that WIM file is automatically extracted before the content is used in a task sequence step.

Different types of content items can be created.  In some cases, additional metadata needs to be configured on the content item to tell DeployR how to use that content item.  The types available include:

* Operating system.  For Windows OSes, this content item is a single WIM file containing one or more OS images.
* Application.  This specifies a folder of content needed to install an app on a device, along with the command line, working directory, and successful exit codes the app installer may return.
* Driver pack.  This specifies a folder of Windows driver files, along with the manufacturer and model of the device that can use the driver pack.
* Other.  Anything else is presently grouped into the "other" category.  This can include answer files, or any other content that might be needed by a task sequence.

To get started, you may want to:

* Create a operating system item for a Windows 11 OS WIM file.
* Create a driver pack for one or more device models.
* Create an application that can be installed on a new OS.

These can be added by navigating to the **Content items** node in the StifleR dashboard.  Click the **+Add** button and specify the needed details.

<figure><img src="/files/49gkPaNDozmAuf92lc1D" alt=""><figcaption></figcaption></figure>

Once the content item has been added, a new version (initially version 1) needs to be added.  Once that version has been added (specifying the type-specific details), you can then upload the needed content. &#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.2pintsoftware.com/deployr/getting-started/creating-a-content-item.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.