> For the complete documentation index, see [llms.txt](https://help.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.whaly.io/training/for-builders/setting-up-the-training-material.md).

# Setting up the training material

**Objectives:** in this section, you will be guided on setting everything up in order to start training.

{% hint style="info" %}
This steps are usually done on your behalf by Whaly's team before the first onboarding call. You should just check that everything is set-up properly before heading on to the next article :relaxed:
{% endhint %}

## High level plan

1. Connecting the "Jaffle Shop" source
2. Creating our base exploration
3. Creating our base report
4. Adding our first chart

### 1. Connecting our Jaffle Shop source

The first thing we will need to do is connect our training source. In order to do so, simply head to the source catalog and click on the `Jaffle Shop (Training material)` source. Then, click on the `Connect` button.&#x20;

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

The Jaffle Shop source is composed of three data tables:

* Customers
* Orders
* Payments

A customer has between 0 and n orders. An order has a customer, and between 1 and n payments. A payment is linked to an order.&#x20;

![Jaffle Shop database schema](/files/MnUqIrMSe08L2koV1xu6)

### 2. Creating our training exploration

In order to create our training exploration, head to workbench, then create a new exploration from a template. Select the Jaffle Shop (training) template. Then, simply click on "use template".

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

The following exploration will be automatically created in your workspace :&#x20;

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

### 3. Creating our base report

In order to create our training report :&#x20;

1. Head to your workspace. Click on "Create a dashboard", give it a name (Training for example) and a folder, then and click on "Continue"
2. Add a text tile with the following text :&#x20;

> Exercise:
>
> 1. \[New Chart] Add Order breakdown per Order status
> 2. \[New Chart + New Metric] Add the payment amount paid with gift cards per month
> 3. \[New dashboard filter] Filter the dashboard on a customer
> 4. \[New model + New Exploration+ New Chart + New Drill] Add the number of customers per number of orders

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

### 4. Adding our first chart

The first chart we will add is the number of order per week. To do so:&#x20;

1. On the report, click on Edit
2. Click on the Add chart button
3. Select the "Order" exploration from the list&#x20;
4. Then, reproduce the following query :&#x20;
   1. Drop "number of orders" and "order date" in the chart.
   2. Select the line chart under timeserie
   3. Set the time to "all times", and group by week
   4. Click on Run query, and display as a bar chart
   5. Click on "Add tile" to add the chart to your dashboard

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

Our dashboard should look like this now :&#x20;

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

That's it, we are now ready to work on the training exercices. Head on the the next step in order to deep dive on charts creation :diving\_mask:


---

# 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://help.whaly.io/training/for-builders/setting-up-the-training-material.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.
