> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/site-themes/site-themes-glossary.md).

# Site themes glossary

**Instant Site**\
Website builder created by Ecwid that allows creating for both ecommerce and non-ecommerce sites.

Read more about Instant Site in the [**Help Center**](https://support.ecwid.com/hc/en-us/sections/360001694100-Instant-Site).

**Instant Site Editor**\
Native UI for building Ecwid websites available to all Ecwid users right from the Ecwid admin.

**Ecwid admin**\
A one-for-all tool, where users can manage all aspects of their store: products, orders, customers, website, integrations, etc.

**Site theme**\
A pre-defined configuration for the website that includes design and content settings, overall style, and in some cases custom widgets that extend the store functionality.

**Theme file**\
A `theme-name.ts` file inside the `themes` folder that contains the custom sections – building blocks for the website – with different demo data and default values.

**Preview store**\
A store with the Site template applied that serves as a fully set up working example for public Site templates. It allows merchants to see how the template can be used before committing to the purchase decision.


---

# 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.ecwid.com/site-themes/site-themes-glossary.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.