> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/masterstudy-theme-documentation/woocommerce/woocommerce-courses-not-lms.md).

# Woocommerce Courses (not LMS)

Default Masterstudy layout Courses are built on WooCommerce Products. To create a course you need to add a Product:

![](https://2021837383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDO9V_qgvV5cQdw04iz%2F-MTUjGx3Rk6jiM2lV-gq%2F-MTUmomygIOFhndfuCHG%2FScreenshot_77.png?alt=media\&token=3b94d1bb-e5a7-46c4-8c80-0542d2d643c1)

For each course, you can specify the Category, add Course name and Description. For the Description, we use standard Content area with Visual Composer, where you can insert any shortcode you would like to display.

Moreover, you can add the course image or image gallery:

![](https://support.stylemixthemes.com/storage/stm-manuals/April2020/courses-2.jpg)

For the Content area – if you want to add a Course plan, Course sections or Course lessons overview, just insert the Course Lessons shortcode:

![](https://2021837383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDO9V_qgvV5cQdw04iz%2F-MTUjGx3Rk6jiM2lV-gq%2F-MTUn1USYpacfxmXKWit%2FScreenshot_78.png?alt=media\&token=73b089a7-36ff-4628-a2d3-9d2dd0dbcf86)

After you insert it, you have the option to add a lesson into the Course section:

![](https://2021837383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDO9V_qgvV5cQdw04iz%2F-MTUjGx3Rk6jiM2lV-gq%2F-MTUnUiDN4Lc0X-12axJ%2FScreenshot_79.png?alt=media\&token=53443d29-da33-4979-8a4a-a5822a058a21)

After you add a Lesson, it has additional options:

![](https://2021837383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDO9V_qgvV5cQdw04iz%2F-MTUjGx3Rk6jiM2lV-gq%2F-MTUn_x4nks3tLRuisct%2FScreenshot_80.png?alt=media\&token=dfcd345a-d152-4e8b-a9e9-2c358d31b6ea)

Once you complete the Course description, go to the Product Data to specify the Price:

![](https://2021837383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDO9V_qgvV5cQdw04iz%2F-MTUjGx3Rk6jiM2lV-gq%2F-MTUnm04uMrUs8gq086K%2FScreenshot_81.png?alt=media\&token=eb6ccd15-50b7-4f27-8069-39aac15df8d3)

If it’s a Free course, you just put 0 for Regular Price.

If you have limited seatings in classes, you should go to the Inventory tab specify Stock Qty.

After that, you can specify the Course Details information and assign a Teacher of that Course.

![](https://2021837383-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MDO9V_qgvV5cQdw04iz%2F-MTUjGx3Rk6jiM2lV-gq%2F-MTUo-XAP87ceEGSAZfT%2FScreenshot_82.png?alt=media\&token=6f8e27e0-7094-4948-9316-72e8cb9e224b)


---

# 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.stylemixthemes.com/masterstudy-theme-documentation/woocommerce/woocommerce-courses-not-lms.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.