> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/sell-on-lid/courses.md).
# Courses
Sell a course on Lid: modules, lessons, free previews, hosted by Lid, unlocked the moment someone buys. Publish it whole, or while it is still in progress.
A course is a product with structure: modules, lessons, and progress, unlocked the moment someone buys.
## Steps
1. Open **My store** in your [dashboard](https://lid.pro/dashboard) and click **New course**.
2. Name the first module and the first lesson. The lesson is a video, audio or PDF file, or text.
3. Say whether the course is **Available now** or **In progress**. Buyers see this before they pay, so you can sell a course while you are still recording it.
4. Add the rest of your modules and lessons, in the order you want. Mark any lessons you want as free previews.
5. Set the price and the commission you share.
6. Publish.
Buyers get access automatically after they pay, and they can see where they left off.
## FAQ
Do I need a separate hosting tool?
Lid hosts the course page and the lessons for you.
How do I get paid?
Like any Lid sale: in seconds, automatically, with a flat 3% fee.
Build your course at [lid.pro](https://lid.pro). That is the link if you want to sell.
---
# 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.lid.pro/sell-on-lid/courses.md?ask=&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.