> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/integration-and-extensions/support-for-all-websites.md).

# Support for all websites

### Does AppMySite support websites made on all platforms?

Absolutely! AppMySite supports websites built on various platforms, ensuring compatibility and ease of integration. Whether your website is on WordPress, WooCommerce, or any other platform, our app-building platform is designed to cater to your needs seamlessly. AppMySite supports websites across various platforms.&#x20;

If you have a WordPress website, leverage our 'WordPress to app' product. For WooCommerce websites, opt for 'WooCommerce to app.' If your website is on a different platform, our 'Web to App' product ensures all functionalities are seamlessly rendered on your native iOS or Android app. Moreover, with our 'Custom app' product, you can create an app from scratch, even without a website. AppMySite caters to diverse needs, making app creation effortless and flexible.

{% hint style="success" %}
Websites made using web technologies like HTML, CSS, JavaScript, and more can also be converted into mobile apps by simply using web-views.
{% endhint %}


---

# 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.appmysite.com/frequently-asked-questions/integration-and-extensions/support-for-all-websites.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.
