> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/tutorials/introductory-animal-race.md).
# Introductory: Animal race
This tutorial is aimed at people who are new to the Experience Editor but have some experience with the ENGAGE application. However, before your start, we recommend that at a minimum you through the [Controls](/engage/experience-editor/user-interface/controls.md) section.
In this tutorial you’ll create a race between two animals and learn about the following features of the Experience Editor:
* Adding IFX
* Transforming objects
* Creating keyframe animations
* Using animation overrides
* Using the timeline
* Retiming animations on the dope sheet
* Editing curves
The following image shows a top-down view of the layout that we’ll use:
Top-down view of the layout for this tutorial
For step by step instructions on how to create the animation, watch the following video or read the written instructions in the following sections:
{% embed url="" %}
Creating an animal race in the Experience Editor
{% endembed %}
---
# 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.engagevr.io/engage/experience-editor/tutorials/introductory-animal-race.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 `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.
