> For the complete documentation index, see [llms.txt](https://help.meltingspot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meltingspot.io/english/spot-content/courses/draft-mode.md).

# Draft mode

By default, when a course is created, it's in draft mode, to give you time to configure and fill it in peacefully.&#x20;

## Draft mode&#x20;

While your course is in draft mode, it is only visible to Spot admins. In the course list, the course card is displayed in light gray with a `Draft` status. Once your course and all its stages are ready, you can publish it!&#x20;

## Publishing a course&#x20;

To publish a Course, go to that course, and from the reading view, click on the `Publish` button next to the `Edit` button in the top right-hand corner of the page. A modal will open to confirm your action! Once the Course has been published, it will be visible in the course list for Spot members and authorized visitors.&#x20;

<figure><img src="https://3055204660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrzBxnWaSListMwx3rzKu%2Fuploads%2F8ORtJcKRldpt97O4iTLB%2FScreenshot%202024-07-11%20at%2017.33.52.png?alt=media&amp;token=dc049c05-29a6-4b87-9c00-83e353326cc0" alt="Publishing a course"><figcaption></figcaption></figure>

At any time, you can decide to return a course to draft mode! To do so, simply click on the `Convert to draft` button next to the `Edit` button in the top right-hand corner of the screen. Once a course has been converted to draft mode, no member or visitor will be able to view or access it; only admins will be able to.

{% hint style="info" %}
If members have already started a course and you convert it to draft, their existing data will remain accessible from the course participants table.
{% endhint %}


---

# 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://help.meltingspot.io/english/spot-content/courses/draft-mode.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.
