> 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/v1/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:
Go to your homepage
1. Click on "Edit Group" button above the title of the venue.
2. Scroll down to "Group Content", click to open the edit box and find the field "instructions".
3. In the "value", you can include your instructions in markdown or html as a string.
View of the Group Content edit box, highlighting the instructions field
Markdown example, to customize:
```
"# Important Dates\n
- Submission Deadline: Sept 11, 2021 11:59pm AOE\n
- Author Response Period: Oct 11, 2021 - Oct 18, 2021\n
- Decision Notification: Nov 1, 2021\n
- Camera Ready: Nov 15, 2021\n\n
# Submission Format\n
- Proceedings track: 8 pages. Findings (extended abstract) track: 4 pages. Excluding references and appendices.\n
- Submissions must be anonymous for the double-blind review process\n
- Latex template: [Proceedings](https://www.overleaf.com/latex/templates/proceedings-template/trtrvjxchjdw) or [Findings](https://www.overleaf.com/latex/templates/ml4h-2024-findings-template/vkvrxcgdkcmn)"
```
which will be displayed as:
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openreview.net/v1/how-to-guides/modifying-venue-homepages/how-to-customize-your-venue-homepage.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
