> For the complete documentation index, see [llms.txt](https://docs.lamsfoundation.org/tbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lamsfoundation.org/tbl/tbl-for-teachers/getting-started.md).

# Getting Started

Your first steps with TBL in LAMS.

{% hint style="info" %}
All you need to get started and running with, it's within this pages. It case you get stuck, [let me](https://lamslearning.medium.com/) know and I'll do my best to help you. 
{% endhint %}

In this section, we'll cover how to:

* [**Create your own TBL design**](/tbl/tbl-for-teachers/getting-started.md#create-your-own-tbl-design)
* **Using your TBL design,** [**create a lesson**](/tbl/tbl-for-teachers/creating-a-lesson.md) **for the students in your course**
* [**Monitor and interact the students and teams' progress**](/tbl/tbl-for-teachers/monitoring-a-tbl-lesson.md)

{% hint style="info" %}
TBL for Students

Want to see how a students run TBL lessons? Check out the [TBL Student Guide](/tbl/tbl-for-students/students-tbl-guide.md).
{% endhint %}

## **Create your own TBL design**

In the [previous section](/tbl/tbl-with-lams.md#tbl-with-lams), we looked at how we use LAMS to support the entire [TBL process](/tbl/tbl-process.md). 

While what we show is pretty much how you can create a TBL design from scratch, there's is a better and simpler way to create TBL designs. 

Let's first look at the [TBL Design Wizard](/tbl/tbl-for-teachers/getting-started/tbl-design-wizard-1.md).


---

# 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.lamsfoundation.org/tbl/tbl-for-teachers/getting-started.md?ask=<question>&goal=<user_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.