> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/webcomponents-overview/web-components-4.x./guides/quick-start/your-first-search.md).
# Your First Search
Adapt the record-list demo to run your first search.
We recommend using the [ff-record-list demo](https://github.com/FACT-Finder-Web-Components/demos/blob/release/4.x/ff-record-list/index.html) as a starting point. It is lightweight and therefore ideal to get familiar with FactFinder Web Components.
If you want a **quick overview** about all possible features, please refer to [`ff-record-list`](file:///api/4.x/ff-record-list#tab=docs) in the API documentation.
The following sections cover all necessary steps to adjust the demo to fit your setup.
{% stepper %}
{% step %}
### Change Configuration
In case you skipped previous sections please read more about the configuration [here](file:///documentation/4.x/configuration).
First, you want to change the `url`, `channel`, `version` and possibly the `api` attributes. If you don't know the channel name or FactFinder version, please refer to your FactFinder UI.
```html
```
In most cases the `default-query="backpack"` won't make sense for your shop. Simply change it to a term suitable to your product range. If you don't want to specify a default query term, just remove the attribute entirely and it will default to `*` which is the shorthand for searching for all products.
{% endstep %}
{% step %}
### Change Template Strings
The data used to display product information is provided by the CSV file you specified in the FactFinder UI to teach FactFinder about your product data.
**This product data is returned in a one-to-one manner.** This means that a field named `Price` in the CSV file will also appear as `Price` (case-sensitive) in the `searchResult.records[index].record` property of the HTTP response's JSON.
The same `record` object is also available in several FactFinder Web Components. You can insert its values into your custom HTML using the double curly braces syntax `{{record.Title}}`. Here is an example using the [`ff-record`](file:///api/4.x/ff-record-list#tab=docs) element:
```html
![]()
{{record.Title}}
{{record.Price}}
```
See the [Template Engine documentation](file:///documentation/4.x/template-engine) for more details on this topic.
{% endstep %}
{% endstepper %}
---
# 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.fact-finder.com/webcomponents-overview/web-components-4.x./guides/quick-start/your-first-search.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.
{{record.Title}}
{{record.Price}}