Elements
Elements are the content, layout, media, conversion, product, quiz, and page-level components you add in the Atomicat Page Builder. Each element has a content drawer for what it says or does and, when supported, a style drawer for how it looks across desktop, tablet, and mobile.
How Atomicat Organizes Elementsβ
Atomicat 3.0 registers element editors through dynamic content and style interfaces. Content editors include Text, Advanced Text, Button, Form, Container, Countdown, Menu, HTML, IFrame, Interactive Quiz, Product, Announcement, Selling Point, Audio, Height Weight, and more. Some palette entries are preconfigured versions of another element: Alert is a Text element with alert styling, and Multiple Choice is a Quiz Option configured as checkbox.
Main Element Familiesβ
- Text and headings include Text, H1, Animated Text, Advanced Text, and alert-style text presets.
- Layout includes Container, Spacer, Divider, Tab, Menu, and other structure-focused blocks.
- Media and proof include Audio, Chart, Comment, FunFact, Google Maps, Icon List, Image Comparison, Selling Point, Social Icon, and similar blocks.
- Conversion includes Button, Redirect, Countdown, Star Rating, Roulette, Product, Form, and supporting proof widgets.
- Quiz includes Quiz, Interactive Quiz, Quiz Option, Multiple Choice, and Height Weight fields.
- Singular page controls include Cookie, Notification, and WhatsApp, which are applied once at page level.
Element guide indexβ
Use these groups to jump from the overview into the exact element guide:
| Need | Recommended docs |
|---|---|
| Write and format page copy | Text, H1, Advanced Text, Animated Text |
| Build page structure | Container, Spacer, Divider, Tab, Accordion |
| Add conversion actions | Button, Redirect, Countdown, Forms, Product |
| Add media and proof | Audio, Video, Google Maps, Comment, Star Rating |
| Build quizzes | Interactive Quiz, Quiz Elements, Multiple Choice, Height Weight |
| Add advanced embeds | HTML, IFrame, Menu, Icon List |
| Configure page-level widgets | Cookie, Notification, WhatsApp, ScrollUp |
Choosing The Right Elementβ
- Use the most specific native element before adding custom HTML or iframe code.
- Use Container for layout, not for text semantics.
- Use Button or Redirect for actions, not linked decorative text when the action is important.
- Use Product when the page needs product data from the product editor.
- Use Quiz elements only when answers, logic, or lead output matter.
- Use singular elements sparingly so Cookie, Notification, and WhatsApp do not compete for the same screen space.
Testing Before Publishingβ
- Preview desktop, tablet, and mobile after adding or changing layout elements.
- Click every Button, Redirect, Menu item, WhatsApp link, and Star Rating action.
- Submit Forms and Quizzes with realistic test data.
- Check third-party embeds such as IFrame, HTML, and Google Maps on the published domain.
- Verify conversion claims such as countdowns, ratings, comments, and announcements for accuracy.
Related Docsβ
- Text Element
- Button Element
- Container Element
- Forms
- Quiz Elements
- Product Element
- HTML Element
- IFrame Element
- WhatsApp Element
FAQβ
Why do some palette items share behavior?
Some items are preconfigured versions of another element. Alert uses Text with alert presets, and Multiple Choice uses Quiz Option checkbox behavior.
Why does an element have no style tab?
Not every element has a dedicated style interface. Some rely on parent containers, singular component settings, or embedded third-party behavior.
What should I test after changing elements?
Test the visitor path: layout on all devices, clicks, forms, quiz answers, embeds, tracking events, and published-page behavior.