Container
Use Container to structure page sections, rows, columns, cards, and nested layouts.
Content settings
| Setting | What it controls |
|---|---|
| Nested content | Elements placed inside the container. |
| Element actions | Move, duplicate, delete, or reorder child elements. |
| Layout structure | Rows, columns, and nested containers. |
Style settings
| Style area | What you can adjust |
|---|---|
| Layout | Direction, alignment, justification, gap, wrapping, and ordering. |
| Size | Width, max width, min height, height, and responsive sizing. |
| Spacing | Padding and margin per device. |
| Background | Color, image, gradient, overlay, and positioning. |
| Border | Border style, width, color, radius, and shadow. |
| Advanced display | Position, transform, animation, conditional display, and HTML ID/classes when available. |
Best practices
- Build page structure with containers before adding detailed content.
- Use responsive direction and spacing instead of fixed desktop-only layouts.
- Name and organize sections clearly for easier editing.
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 Container, 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 Container, 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 Container, 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 Container, keep a short checklist of the fields you changed and test the result in the same browser session.