> For the complete documentation index, see [llms.txt](https://help.canoa.supply/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.canoa.supply/docs/collect/how-to-start-a-canvas-from-public-catalogs.md).
# How to start a Canvas from Public Catalogs
Learn how easy it is to start a Canvas while searching for products in our Public Catalog.
As you browse through our Public Catalogs and select a product, you can start a Canvas directly from that product.
1. Go to our [**Public Catalog**](https://www.canoa.supply/products)**.**
2. Click on a product, and the product details will appear on the side panel.
3. Click on **Start a Canvas** below the product image, and a new Canvas will launch automatically.
4. Add an inspiration image or additional products, toggle between views, and start designing.
Start a Canvas from the Product Details view
{% content-ref url="/pages/isT6ZbaPOPyXlDVHsQ9b" %}
[How to create a furniture & accessories presentation](/docs/collect/how-to-create-a-furniture-and-accessories-presentation.md)
{% endcontent-ref %}
{% hint style="info" %}
For Pro, Studio, and Custom Accounts, you'll see the option to **Save to My Catalog**, as well as **Start a Canvas**. Remember, My Catalog can be seen as your favorites folder.
{% endhint %}
Start a Canvas or Save to My Catalog available for Pro & Unlimited
---
# 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.canoa.supply/docs/collect/how-to-start-a-canvas-from-public-catalogs.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.
