> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/customizations/template-customization/tricks-for-building-a-super-flexible-template-that-can-apply-to-most-jobs.md).

# Tricks for building a super-flexible template that can apply to most jobs

Maintaining one template is hard enough. Maintaining multiple templates is just a drag. This video show why you might be able to use just a single template for all your different jobs.

**This video goes over three main concepts**

1. Blank sections of chapters do not print in a finished report
2. You can copy chapters and sections and rename them as needed to fit a specific job
3. You can adjust your boilerplate on the fly to suit a specific job.

{% embed url="<https://www.youtube.com/watch?v=ES8PdkrN3Ac>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/customizations/template-customization/tricks-for-building-a-super-flexible-template-that-can-apply-to-most-jobs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.