> For the complete documentation index, see [llms.txt](https://docs.flowstatecoders.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowstatecoders.com/blog-product-spotlight/how-to-use-the-app.md).
# How to use the app?
In this article we will show you how you can get pop-ups to work with a new or edited blog .
The first step is adding a new product link to you blog which can be done like this. Select the text that refers to the product and click on insert link.
Then you will get the following screen where you can insert a product link.
After all the product links are placed, click "Save"
After your article is saved, click on "More actions" and then click "Scan Product Links"
You can now go to your blog article and you will see a pop-up when you hover or click on the product link depending on your settings.
When you hover over the product link
When you click on the product link
---
# 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.flowstatecoders.com/blog-product-spotlight/how-to-use-the-app.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.