> For the complete documentation index, see [llms.txt](https://docs.eralis.live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eralis.live/documentation/getting-started/events-and-eras.md).

# Events and eras

Go from sign-up to your first deploy in under five minutes.

Events are the main chronological records in an Eralis project. Eras represent broader periods that help organize a timeline.

## Events

Create and edit events from the project workspace. Events can be duplicated from the command palette when you need a similar record without starting from scratch.

## Eras

Use eras to visually and conceptually group events within a larger period. Eras can be created, edited, and deleted from the Library panel.

## Version history

Eralis keeps snapshots when project material is edited or deleted. Open **Project settings → History** to inspect and restore earlier snapshots.

> Undo/redo and event trash/soft-delete are roadmap features and should not be relied on yet.


---

# 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://docs.eralis.live/documentation/getting-started/events-and-eras.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.
