> 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/getting-started/the-kita-interface.md). # The Kita interface This page describes what each area is for. For the tasks you carry out in them, follow the links in See Also. Kita has three main surfaces. The dashboard is where you land after signing in. A course page holds the lessons you teach and the students enrolled on them. The lesson view is the coding workspace, with the instructions, the code and the output side by side. #### The main navigation The sidebar runs down the left of every page. Your instance name sits at the top, your profile at the bottom, and the panel collapses from the control at its top right to widen the working area. | Item | What it holds | | ------------- | ------------------------------------------------------ | | **Dashboard** | Where you land after signing in | | **Courses** | Every course on your instance, including quick courses | | **Projects** | Standalone code files you share with a link | | **Students** | Student records, groups and enrolments | | **Marking** | Submitted work waiting to be marked | A dot next to **Marking** means there is work waiting for you. The badge beside the Kita logo shows your role, so a teacher account shows **TEACHER**. This is separate from Teacher Mode, described below. #### The Courses page **Courses** lists everything on your instance, split into **Quick Courses** and **Courses**. **All courses** shows everything, and **Available** narrows it to what you can open. The tags across the top filter by type: **STANDARD**, **QUICK** and **CYBER**. **Create** makes a new course. **Kita Library** opens the shared catalogue, and **Search courses** finds one by name. Each card shows the course type, its level, and how many lessons it holds. The lock icon shows whether the course is open or closed to students, and the kebab menu holds the actions for that course. #### A course page A course page opens on two tabs, **Sections** and **People**. **Sections** holds the course content: your lessons, in the order students move through them. Drag the handle at the left of a row to reorder them, and use the **All**, **Easy**, **Intermediate** and **Hard** filters to narrow the list. Each row shows the lesson name, its description, and its points value. **People** is where collaboration groups are prepared before a lesson. Across the top of the page: * **Enrol Student** adds a student to this course directly. * **Course settings** opens the course's own options. * **Student Progress** shows how the class is moving through the lessons. The pencil beside the course name renames it. #### The lesson view The lesson view is where code is written and run. It has three columns, with a narrow icon rail on the far left. **The left panel** **Current Lesson** is a dropdown naming the lesson you are in, so you can move between lessons without leaving the view. **Files** lists everything in the workspace. Each file has an eye icon to show or hide it from students, and a kebab menu for its actions. Files can be dragged to reorder. **Add new** creates a file, **Manage Files** opens the file options, and the download icon beside the heading downloads the workspace. **The code editor** Open files appear as tabs across the top of the centre column, with line numbers down the left. A toolbar sits above the code, holding **Run** at its right-hand end. Run executes the current program and sends its output to **Console**. **Ask AI for help** sits below the editor, with **Open AI Help** to open it. What the AI is allowed to give a student is set per lesson. **The right panel** Four tabs sit across the top: * **Instructions**, what the student is asked to do * **Glossary**, the terms used in the lesson * **Tests**, the checks a submission is run against * **Console**, the program output The pencil at the top right edits the panel's content. #### Marking **Marking** opens with a count of how much work is waiting and across how many courses, then a **Weekly overview** showing what has been submitted and how much of it arrived on time. Below that, each course with work waiting appears as a card with the number to mark and a **Start Marking** button. Filters narrow the list by course or lesson, by status, and by the dates work was created. Opening a lesson shows **Submitted / Enrolled**, **Needs Marking** and **Average Score**, then the submission list: each student, the lesson they are on, their score, whether they submitted on time, and their test results. **Release all marks** returns marks to the whole class at once. #### Students **Students** has three tabs. * **Manage Students** is the central directory of everyone on your instance, with their username, groups, last login and temporary password. **Add Student** adds people, and **Student Credentials** downloads sign-in details. * **Groups & Sub Groups** is where your teaching classes live. * **Enrolments** shows which groups are on which courses. #### Teacher Mode **Teacher Mode** appears at the top right of course and lesson pages, not on the dashboard. --- # 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://docs.getkita.org/getting-started/the-kita-interface.md?ask=&goal= ``` `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.