> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/how-to-guides/modifying-venue-homepages/how-to-customize-your-venue-homepage.md).

# How to customize your venue homepage

You can customize your venue homepage using Markdown. All Markdown should be validated to ensure that it will not break the layout of the page: <https://stackedit.io/>

Many properties can be modified using the Group Content tab of your venue's workflow page: [https://openreview.net/group/edit?id=Your/Venue/ID#groupContent](https://openreview.net/group/edit?id=HCAL/2026/Call_for_Chapters#groupContent). Here you can use the `Edit` button to update properties of the venue including the Venue URL, location, and start date, among others.

To add additional custom text to your venue, go to the UI Code tab of the same page [https://openreview.net/group/edit?id=Your/Venue/ID#groupUICode](https://openreview.net/group/edit?id=HCAL/2026/Call_for_Chapters#groupUICode) and edit the instruction variables to include a custom markdown string in the format `"instructions": "Your Markdown String"` .


---

# 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.openreview.net/how-to-guides/modifying-venue-homepages/how-to-customize-your-venue-homepage.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.