> For the complete documentation index, see [llms.txt](https://help.aristotlemetadata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aristotlemetadata.com/registry-configuration/homepage-editor.md).

# Homepage Editor

{% hint style="info" %}
The Homepage Editor can only be used by an Administrator.
{% endhint %}

The Homepage Editor allows you to customize the homepage of your registry, giving you the power to personalize its appearance and content. This tool allows for specific adjustments, including modifying layout elements, adding or removing sections, and incorporating relevant content. By utilizing the Home Page Editor, you can create a distinct and engaging user experience for visitors to your registry's homepage.

### Homepage Editor Functions

The Homepage Editor allows for two methods of editing the homepage

* HTML editor: Allows you to add HTML code to modify the homepage.
* Safe editor: Allows you to modify the homepage without the use of HTML.


---

# 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.aristotlemetadata.com/registry-configuration/homepage-editor.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.