> For the complete documentation index, see [llms.txt](https://docs.tachyon.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tachyon.video/user-guide/4.-programming-a-show/timeline-editor.md).

# Timeline Editor

The Timeline module can be broken up into different subsets of tools. Each subset corresponds to a specific window section of the Timeline module (with the notable exception of the Color Correction Tools which have their own window). This section of the documentation focuses on the Timeline Editor window section, which is used for organizing media, cues, effects, etc.

The **lower section** of the Timeline window is called the **Timeline Editor** and regroups the tools you will use to edit a Show. Shows are constructed by **placing Clips sequentially in the tracks** of the Timeline.

The horizontal axis of the Timeline shows the time progression of a Show, expressed in *hours:minutes:seconds:frames*.

Screens (see Screens in Programming a Show) are positioned on the vertical axis of the Timeline. Each Screen can contain one or many Layers, which in turn contain different types of Clips: media, cues, effects, etc.

![](/files/-MZNkbxfeAJHGCpmVud6)


---

# 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.tachyon.video/user-guide/4.-programming-a-show/timeline-editor.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.