# Project & Exercise Structure

<img src="/files/pwIsNchL78D5ipIgTf1r" alt="Project &#x26; exercise structure" class="gitbook-drawing">

In the Editor before creating/selecting an exercise, you'll see this screen which displays all **projects and exercises**:

<figure><img src="/files/8uVHnWnIJB7KfABsRzCg" alt=""><figcaption></figcaption></figure>

| Projects                   | Exercises                              |
| -------------------------- | -------------------------------------- |
| Projects contain exercises | Exercises contain all authored content |

## Exercise structure

Within exercises, designers can organise their work in different ways:

<figure><img src="/files/wnkZHE2N65tEDQ8UH8Jr" alt=""><figcaption></figcaption></figure>

### Chapters and serials

| Chapters                                                                                     | Serials                                                                               |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| These are like MELs in the team-based Editor, but they're purely for organisational purposes | Allow you to split chapters into sections, keeping material tidy and easy to navigate |

Chapters and serials do not affect publishing and have no impact on what the learner sees in the exercise. They exist solely in the Editor to help designers manage large exercises.

### Rows

Within chapters and serials are rows. These contain the steps of your exercise content. Unlike chapters and serials, rows do affect publishing. They act as the timeline of your exercise, meaning that during playback rows run from top to bottom.&#x20;

#### Narrative block

Narrative blocks group rows for story logic or authoring clarity. This is because narrative steps require no player interactions, so a narrative block must end with a question step to further the exercise.

<figure><img src="/files/COn0e8Dk1cqZ6axwYQgd" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://helpdocs.conducttr.com/colibri/getting-started/core-concepts/project-and-exercise-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
