> For the complete documentation index, see [llms.txt](https://docs.bytenite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bytenite.com/create-with-bytenite/building-blocks/job-templates.md).
# Job Templates
A **Job Template** (or simply *Template*) combines Building Blocks into one configuration file for your jobs. It:
* Provides instructions to the services that execute your job.
* Ensures your app and data engines are connected correctly.
By default, ByteNite generates a job template when you start building a new app. This allows you to focus on developing your app without needing to configure the other components upfront.
However, since your app may expect specific data types or formats, you can create and customize a job template to link your app to the appropriate partitioning and assembling engines.
### Job Template file
Example:
{% code title="template.json" %}
```json
{
"id": "img-gen-diffusers-template",
"description": "A template for my img-gen-diffusers app",
"app": "img-gen-diffusers@1",
"partitioner": "replicate-fanout",
"assembler": "zipper",
}
```
{% endcode %}
#### **How to create a job template**
You can either:
1. Define the fields manually as shown in the example, or
2. Generate a blank template using the ByteNite CLI:
```
bytenite template new [template_name]
```
#### Key notes
* When you create a new app, a [template is generated automatically ](/create-with-bytenite/building-blocks/apps.md#app-directory-overview)and is uploaded with the app.
* If you prefer to manage templates separately, you can move your template out of the app folder and use the CLI to manage it independently.
Your template includes a user-defined `id` and an optional `description`. Use the `app`, `partitioner`, and `assembler` fields to specify which components should be used in jobs built from this template:
app string
**Description:**
An **app tag** to be used with this template.
**Supported Format:**
Please refer to the [Glossary](/other/glossary.md#tag) definition.
**Examples:**
* `"img-gen-diffusers"`
* `"img-gen-diffusers@1"`
* `"img-gen-diffusers@1.2"`
partitioner string
**Description:**
An **engine tag** to be used with this template.
**Supported Format:**
Please refer to the [Glossary](/other/glossary.md#tag) definition.
**Examples:**
* `"replicate-fanout"`
* `"replicate-fanout@2"`
* `"replicate-fanout@0.4"`
assembler string
**Description:**
An **engine tag** to be used with this template.
**Supported Format:**
Please refer to the [Glossary](/other/glossary.md#tag) definition.
**Examples:**
* `"zipper"`
* `"zipper@3"`
* `"zipper@1.0"`
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.bytenite.com/create-with-bytenite/building-blocks/job-templates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.