Elements
Elements are the building blocks you add to a page in the Atomicat Page Builder.
Use elements to create page content, media, buttons, forms, product areas, quiz interactions, layout blocks, and page-level features such as WhatsApp, notifications, cookies, and scroll-up controls.
Element groups in the builderβ
The builder sidebar organizes elements into groups so you can find the right component faster.
| Element group | Examples |
|---|---|
| Text | Paragraph, H1, H2, H3, Animated Text, Advanced Text. |
| Media | Image, Video, Audio, Icon, Icon List, Slider, Tab, Chart, Pie Chart, Alert, Testimonial, Selling Point, FunFact, Social Icon. |
| Button | Button and Redirect button. |
| Blocks | Container, Form, Countdown, Divider, Footer, Accordion, Menu, HTML, IFrame, Google Maps, Roulette, Progressbar, Star Rating, Price, Product, and related structural blocks. |
| Singular | Cookie, WhatsApp, Notification, and ScrollUp. |
How elements are editedβ
After you add or select an element, the edit drawer shows available controls for that element.
Most elements can include:
- Content controls for text, URLs, fields, media, or element-specific data.
- Style controls for spacing, color, typography, background, borders, sizing, and alignment.
- Advanced controls for additional behavior or configuration.
- Template controls when the selected element supports reusable templates.
Some elements have limited style controls because their behavior depends on embedded content or structural logic.
Choosing the right elementβ
Use the simplest element that matches the goal.
| Goal | Recommended element type |
|---|---|
| Add a heading or paragraph | Text elements. |
| Add an image, video, audio, icon, slider, or chart | Media elements. |
| Send visitors to another URL or page section | Button or Redirect button. |
| Capture lead information | Form. |
| Organize page structure | Container, section, divider, or layout-focused block. |
| Add checkout or offer information | Product or Price. |
| Add custom embedded content | HTML or IFrame. |
| Add page-level floating behavior | Singular elements such as WhatsApp, Cookie, Notification, or ScrollUp. |
Best practicesβ
- Start with layout and content before advanced styling.
- Use headings in logical order for readability and SEO.
- Keep forms focused on the information you need.
- Test buttons and redirect behavior before publishing.
- Preview mobile layouts after adding media, forms, products, or custom HTML.
- Avoid unnecessary custom HTML when a native builder element can do the job.
Related docsβ
FAQβ
When should I use this Elements page?
Use this page when you need to understand the workflow, settings, or decisions related to Elements. It is most helpful before editing a live asset, publishing changes, or troubleshooting behavior in an Atomicat workspace.
What should I check before changing Elements?
Confirm that you are in the correct workspace, project, page, funnel, site, or account area. Review access permissions, saved changes, publishing status, and any connected integrations before making updates.
How do I verify that Elements is working correctly?
Preview the affected page or feature, test the main user path in a fresh browser session, and confirm that forms, redirects, tracking, products, quizzes, or publishing states behave as expected.
What should I do if Elements does not work as expected?
Recheck the configuration described on this page, save the changes again, clear browser cache if needed, and test with a simple version of the setup. If the issue continues, collect the page URL, workspace details, and screenshots before contacting support.