# What Makes a Good Marker

When designing or selecting a marker to use for your projects, visually 'busy' images work best. Try including designs with hard, contrasting edges, colours and shapes as this will provide more visual 'anchors' for the camera to see. Avoid using images that have minimal visual interest e.g. just text or simple outlines.

{% content-ref url="<https://app.gitbook.com/o/QMsd5hT6sxA9FBIB03yh/s/3UKy7VHRJWrNarYaMp13/>" %}
[Blippar Documentation Centre](https://app.gitbook.com/o/QMsd5hT6sxA9FBIB03yh/s/3UKy7VHRJWrNarYaMp13/)
{% endcontent-ref %}

<figure><img src="https://content.gitbook.com/content/cvoJ5rkZRlTAmKNdfteg/blobs/s4E1CUyHkdCdEeto4MKI/Screenshot%202022-12-21%20at%203.40.57%20PM%20(1).png" alt=""><figcaption><p>Good and Bad Marker Examples</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.blippar.com/webar-sdk/v1.7.4./integrations/what-makes-a-good-marker.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
