> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/enhanced-template-editor/supported-file-formats-for-enhanced-templates.md).

# Supported File Formats for Enhanced Templates

The enhanced template editor supports two distinct file formats designed to drive process optimization and improve operational workflow efficiency. While the initial setup steps remain identical to the classic editor, the new editor provides an upgraded, modern interface for designing new templates.

### PDF

Creating a standard PDF template follows the traditional template record configuration workflow:

1. Navigate to the **S-Docs Templates** from the navigation menu
2. Click **New** to create an S-Docs template record
   1. Select **PDF** for the **Template Format**
   2. Configure additional template options
3. Click **Save**

Click the **Template Editor** button to launch the Enhanced Editor Experience.

{% hint style="info" %}
The Template Editor button remains unchanged, but **all newly created PDF templates will automatically open within the enhanced template editor experience.** Existing templates created inthe classic editor will continue to route to the classic editor.
{% endhint %}

### PDF Components

PDF component templates allow you to build modular, reusable blocks of content to simplify tempalte design and create more flexible document processes.

Creating a Component template follows the traditional template record configuration workflow:

* Navigate to the **S-Docs Templates** from the navigation menu
* Click **New** to create an S-Docs template record
  1. Select **Component** for the **Template Format**
  2. Configure additional template options
* Click **Save**

Click the **Template Editor** button to launch the Enhanced Editor Experience.

{% hint style="info" %}
Once you publish a PDF component template, it automatically becomes available as a selectable option within the *Variables* panel for your PDF parent templates of the same record type as defined by the **Related to Type** option in the template record.
{% endhint %}

***

#### Limitations

When managing PDF component templates, please note the following behavioral constraints:

* **Record type matching:** Component templates only appear in the *Variables* panel if their underlying record type matches the parent template. For example, if you are building a PDF parent template for Opportunity records, only PDF components created specifically for Opportunity records will display.
* **Advanced options:** PDF component templates do not currently support the advanced data options for **related lists** and **conditional logic**.


---

# 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://help.sdocs.com/sdocs/enhanced-template-editor/supported-file-formats-for-enhanced-templates.md?ask=<question>&goal=<endgoal>
```

`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.