> 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-lms/introduction.md). # Introduction | MasterStudy LMS Documentation **Thank you for choosing ****the best**** WordPress LMS Plugin 🎉** MasterStudy LMS will convert any WordPress website into a specialized online portal that supports all e-learning & LMS functionality unique to the industry. It gives you the tools to build and sell online courses. It manages all types of content, including videos, quizzes, lessons, slides, assignments, announcements, FAQs, emails, conferences, webinars, streams, certificates and more. This documentation covers all the great features of MasterStudy! *** ## Discover MasterStudy LMS
⭐️ Free VS Pro Plus VersionGetting Started
Getting StartedSystem Requirements
️Pro AddonsLMS PRO Addons
LMS SettingsLMS Settings
LMS Course FeaturesLMS Course Features
LMS AnalyticsLMS Analytics
Plugin TranslationPlugin Translation
Multilingual LMSWPML
ChangelogRelease Notes
Email ManagementEmail Manager and Branding
Divi Builder IntegrationDivi Builder Integration
Additional FeaturesIntegrations
PayPal PayoutsPayPal Payouts Setup
WooCommerceWoocommerce
TroubleshootingTroubleshooting
Developer's GuideDeveloper's guide
--- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stylemixthemes.com/masterstudy-lms/introduction.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 `build a script that syncs our docs to a CMS` 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.