> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/motors-theme-documentation/listing-management/listing-manager-legacy/extra-features.md).
# Extra Features
Legacy Version
The **Features** widget manages adding and removing the items that a car has, such as ABS, Bluetooth, auxiliary heating, tire pressure monitoring sys., turbo engine, nitro, etc.
To select the items to be shown in the **Features,** tick the checkboxes. You can use the **Preview** button to see how it appears on the page:
Overview of the Features tab of the Listing Manager
{% hint style="info" %}
This tab is divided into several **feature lists** that have been entered by the user in [plugin settings](/motors-theme-documentation/single-listing/features-list.md). So the tab may vary based on the added feature lists.
{% endhint %}
Refer to this page to learn about it in detail:
{% content-ref url="/pages/mji2vDPf2GDJ1LQCrn9o" %}
[Features List](/motors-theme-documentation/single-listing/features-list.md)
{% endcontent-ref %}
{% hint style="danger" %}
Unlisted features will **not be visible** in the **Features tab** of the **Listing Manager.**
{% 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.stylemixthemes.com/motors-theme-documentation/listing-management/listing-manager-legacy/extra-features.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.
