> For the complete documentation index, see [llms.txt](https://help.lumintheme.com/lumin-theme-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.lumintheme.com/lumin-theme-documentation/product-page/auto-generate-tabs-with-the-products-content.md).

# Auto generate tabs with the product's content

**Auto Description Tabs**

### **Organize product description in tabs to check features easily for the convenience of buyers** <a href="#id-4ddtjqcsv005" id="id-4ddtjqcsv005"></a>

How to auto generate tabs

1. Add product description normally
2. If you want to show part of the description into different tab, then simply add the heading and change it’s formatting to “Heading 4”, this will show as tab heading and content below will show as tab’s content.
3. You can repeat the step 2 to add more tabs.

Note: The text before the first \<h4> ( Heading 4) will be shown above all tabs, otherwise added to the first tab

![](/files/3cKBkMlfBD3hlIIG2hJK)


---

# 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://help.lumintheme.com/lumin-theme-documentation/product-page/auto-generate-tabs-with-the-products-content.md?ask=<question>&goal=<endgoal>
```

`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.
