Tab
Use Tab to organize several named content panels in one section.
Content settings
| Setting | What it controls |
|---|---|
| Tabs | Add, remove, reorder, and edit tabs. |
| Title | Text shown in the tab navigation. |
| Icon | Optional icon for the tab. |
| Active icon | Icon shown when the tab is active. |
| Expand option | Expand/collapse behavior when available. |
| Tab content | Elements nested inside each tab panel. |
Style settings
| Style area | What you can adjust |
|---|---|
| Direction | Horizontal or vertical tab layout. |
| Justify and alignment | How tab navigation is distributed and aligned. |
| Gap and distance | Gap between tabs and distance from content. |
| Nav | Navigation padding, background, border, and spacing. |
| Title | Normal, hover, and active text colors and typography. |
| Icons | Position, size, spacing, normal color, hover color, and active color. |
| Contents | Content padding and responsive spacing. |
Best practices
- Keep tab titles short.
- Test all tab panels on mobile.
- Use tabs when users need to choose between related content.
FAQ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Tab, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Tab, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Tab, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Tab, keep a short checklist of the fields you changed and test the result in the same browser session.