> For the complete documentation index, see [llms.txt](https://help.microweber.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.microweber.com/user-guide/introduction.md). # Introduction About Microweber Website Builder and CMS ## What is Microweber? Microweber is modern open-source website builder and CMS. With the functionality of Microweber anyone can build website without need of codding. Using it you can build easily from simple website to medium website or online store. ## How can I use Microweber? We providing two options to use Microweber website builder. 1. As a SaaS (Software as a Service) product, on Microweber.com where you are using the product to build a website and the website is hosted on the servers of Microweber. You can choose and subscribe from the different plans depending of your needs. This solution is perfect for non technical people who wants to build their own website or e-commerce as for small and medium web-design companies which use Microweber to build website fast for their customers. 2. As a open-source product anyone can download the latest version of Microweber and hosted in their own server. You can get the last version from Microweber.org. --- # 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.microweber.com/user-guide/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 `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.