> For the complete documentation index, see [llms.txt](https://docs.getkita.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getkita.org/set-up-your-lesson/create-and-edit-a-course.md).

# Create and edit a course

This guide covers editing an existing course and its lessons.

This guide builds one short course with one lesson, end-to-end. Students run a program, then change it so it prints a second line.

#### Step 1: Create the course

1. From the dashboard, select **Create Course**.
2. Enter a **Course name** and a **Description**. Students see both, for example `Year 8 Python Basics`.
3. Set the **Year**. This sets the reading level of AI marking feedback.
4. Save, then open your new course from the dashboard.

#### Step 2: Create the lesson

1. In **Course content**, add a lesson and name it, for example `Your first program`.
2. Open it.

The lesson opens the way your students see it: files on the left, the code editor in the middle, and the instructions on the right.

#### Step 3: Write the starting code

In the code editor in the middle, open `main.py` and give your students something to run:

```python
print("Hello World")
```

Select **Run**. The output appears in the **Console** tab on the right.

#### Step 4: Write the instructions

Select the edit icon at the top right of the instructions panel. Edit Mode shows the whole lesson in one scroll, and your students move through it one chapter at a time with **Next**.

Write the explanation and the task:

> In Python, `print()` puts text on the screen. Open `main.py` and select **Run**.
>
> Now change `main.py` so it also outputs `This is my first program.` on the line below.

Select **Save**.

You can also add blocks that change how students work through the lesson:

* **Accordion** for command summaries a student dips into, such as what `print()` does.
* **Reveal answer** for questions students should attempt before seeing the answer.
* **Image** and **Video** for flowcharts and short explanations.

#### Step 5: Choose what your class sees, then check it

1. In the file list, select the **eye button** next to `main.py` to show it. New files start hidden, so nothing reaches your students until you show it.
2. Open the file's actions menu and select **Create student template**, so each student gets their own copy to work in.
3. Switch to **Student Mode** at the top right and run the lesson the way a student would.

You should see `main.py` and no sign of any answer file you kept alongside it.

That is the whole loop. Write the lesson, choose what your class can see, then check it as a student.

#### Need help?

If a file is showing to students when it should not be, email <hello@getkita.com> with the course and lesson name.


---

# 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.getkita.org/set-up-your-lesson/create-and-edit-a-course.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.
