> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/colibri/getting-started/core-concepts/project-and-exercise-structure.md).
# Project & Exercise Structure
Understand project and exercise structure in Colibri
In the Editor before creating/selecting an exercise, you'll see this screen which displays all **projects and exercises**:
| Projects | Exercises |
| -------------------------- | -------------------------------------- |
| Projects contain exercises | Exercises contain all authored content |
## Exercise structure
Within exercises, designers can organise their work in different ways:
### 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.
#### 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.
---
# 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://helpdocs.conducttr.com/colibri/getting-started/core-concepts/project-and-exercise-structure.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.
In the Editor before creating/selecting an exercise, you'll see this screen which displays all **projects and exercises**:
