> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/microsoft-excel-output/options-microsoft-excel-output/custom-tab/header-font.md).

# Header font

| Option                      | Description                                                                                                                                                 |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Header font name**        | Specify the font name for the text in the header.                                                                                                           |
| **Header font size**        | Specify the font size for the text in the header.                                                                                                           |
| **Header font bold?**       | Select to make the header text boldface.                                                                                                                    |
| **Header font italic?**     | Select to set the header text in italics.                                                                                                                   |
| **Header font underline**   | Specify whether to underline the header text.                                                                                                               |
| **Header font orientation** | Specify an attribute for the header font if you want left-slanted text (minus), right-slanted text (plus), stacked text, horizontal text, or vertical text. |
| **Header font color**       | Specify a font color for the header text.                                                                                                                   |
| **Header background color** | Specify a background color for the header text area.                                                                                                        |
| **Header height**           | Specify the height, in pixels, for the header.                                                                                                              |
| **Header alignment**        | Specify left, right, or centered alignment for the header text.                                                                                             |
| **Add image** (button)      | Click **Add an image** to specify the location of an image file to use in header. For example, a company logo.                                              |


---

# 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.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/microsoft-excel-output/options-microsoft-excel-output/custom-tab/header-font.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.