> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/get-started/installation.md). # Installation Add the GreatStore chat widget to your storefront. ### Add the script tag Paste this inside the `` tag on each relevant page, or in your template to enable it site-wide. ```html ``` The assistant loads in the background and stays hidden until it's opened, so it causes no layout shift. There's no built-in launcher, so add your own trigger: a button or link that calls `GreatStore.open()`. ```html ``` For panel controls, page context, structured content, and link-based opening, see the [JavaScript API](/maker-greatstore/developer-reference/javascript-api.md). ### Platform guides Step-by-step instructions for where the script and buttons go on your platform:

Shopify

Online Store 2.0 and vintage themes.Shopify

WooCommerce

Block and classic themes, with product-page questions.WooCommerce

Magento

Magento Open Source and Adobe Commerce 2.4.Magento

WordPress

Block and classic themes.WordPress

Custom React

Next.js and Vite apps.Custom React
--- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.maker.co/maker-greatstore/get-started/installation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.