# HTML Footer

## Description

The HTML Footer macro adds an \<footer> element on your page. It is the ideal place to put an HTML Address element into it to indicate the author/owner of the document.

## Adding the Macro

1. Edit your page.
2. Select “+” => Other macros
3. Type in “html” in the Search box
4. Select the “HTML Footer” macro

## Macro Options

### **Element ID**

If you need to address your element via an ID, e.g. in a stylesheet or via Javascript, enter the ID here. Make sure, the ID is unique on your page.

### **CSS Classes**

If you need to style your element via an external style sheet, enter all class names here, separated by a blank.

### **Inline Styles**

You can add inline styles to your element here, ending with a semicolon, e.g. “color:#ffffff;background-color:#000099;”.

### **Tooltip Title**

Enter a simple text here that will popup as a tooltip when the mouse is hovered over the element.

### **Custom Attributes**

You can enter fully specified custom attributes here separated by blanks, e.g.: data-animal=”cat” data-color=”red”.

### **Strip Body Wrapper**

By default, Confluence will wrap any macro body content into a \<p> tag. For custom HTLM tags, this might lead to unwanted results. Check this option to remove the Confluence \<p> wrapper.

## Body

You can put other elements into the body.

<figure><img src="https://3884669180-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fs1Vtfb5fcOs06GOHo0WA%2Fuploads%2F1sF6yuTvzNQU1OtzZjFm%2Fimage2017-11-4_18-51-44-768x281.png?alt=media&#x26;token=b97e5653-5d22-4963-bc59-0fc081c70b5c" alt=""><figcaption></figcaption></figure>


---

# 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://lewe.gitbook.io/html-and-aui-toolkit-for-confluence/html-macros/html-footer.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.