> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/experience-cloud/experience-components/ax-tabs.md).

# AX - Tabs

## Overview

**AX - Tabs** is an Experience Cloud component that organizes content into labeled tabs on Experience Sites pages, letting portal users switch between different sections without leaving the page.

Use it to organize related content that doesn't all need to be visible at once—like product details across multiple tabs, multi-section forms, categorized resources, or grouped information. Choose horizontal or vertical tab layouts and configure styling in Experience Builder.

Perfect for product information pages, multi-step forms, resource categories, account sections, or anywhere your portal needs to organize content into switchable views.

{% hint style="danger" %}
This component [leverages slots](/experience-cloud/getting-started/learning-the-basics.md#understanding-slots) for advanced customization, making it ideal for LWR sites. Aura sites do not support this level of customization.
{% endhint %}

## Configuration

### Properties

**Orientation** sets the layout of the tabs — horizontal or vertical — optimizing it for user navigation and content visibility.

**Scoped** enables scoped styling so styles are confined to the component, preventing unintended conflicts with other page elements.

**Scrollable** makes the tabs scrollable, and **Show Scroll Buttons** (with its mobile variant) manages the visibility of the scroll buttons, ensuring easy navigation even with a larger number of tabs.

**CMS Content Background Image** and **Content Background Image URL** customize the background of the tab content area by choosing an image from the CMS or providing a URL; **Content Overlay Color** applies a color overlay on top for readability.

**Data Source** defines the source of the tab labels and content, enabling manual configuration of tab properties such as labels, icons, and tooltips.

## Styling

{% tabs %}
{% tab title="Size Settings" %}
Define the width and height of the tabs, ensuring they fit seamlessly within your layout.
{% endtab %}

{% tab title="Background and Border Styles" %}
Customize backgrounds and borders with options like colors and sizes, enhancing the visual distinction of each tab.
{% endtab %}

{% tab title="Tab Styles" %}
Adjust various aspects such as vertical alignment, width, height, and spacing to refine the appearance and layout of the tabs.
{% endtab %}

{% tab title="Label and Subtitle Styles" %}
Tailor the look of the text within the tabs, applying colors and font styles to enhance readability and aesthetic appeal.
{% endtab %}

{% tab title="Overflow Button Styles" %}
Customize the appearance of the overflow button, adjusting text and background colors for visual consistency.
{% endtab %}
{% endtabs %}


---

# 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.avonnicomponents.com/experience-cloud/experience-components/ax-tabs.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.