> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/naming.md).

# Naming

Gotta give it a catchy name, right?

This page allows you to edit some basic name information about your event.

### Name

The **actual name of your** **event**, used throughout the platform.

<details>

<summary>Example:</summary>

Terra Nova Festival 2026

</details>

### Moderator navigation name

The **name of the event in the navigation bar** on top of the page. This is very useful for events with a very long name.

<details>

<summary>Example</summary>

TNF26 (see previous example & compare)

</details>

### Domain

This is the URL of your event which can be shared with new and existing members so they can sign up as volunteer at your event.

{% hint style="warning" %}
To change it, please [contact us](https://www.eventication.com/contact_us).
{% endhint %}

### Time zone

The time zone your event takes place in. This is not changable.


---

# 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.eventication.com/event/general/naming.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.