Comment
Use Comment to display comment-style social proof or discussion content.
Content settings
| Setting | What it controls |
|---|---|
| Name | Comment author name. |
| Avatar | Author image. |
| Comment text | The comment content. |
| Actions | Like, reply, count, or date text when available. |
| Replies | Nested reply content where supported. |
Style settings
| Style area | What you can adjust |
|---|---|
| Typography | Name, comment, reply, and date text styles. |
| Avatar | Size, radius, and spacing. |
| Container | Background, border, radius, shadow, padding, and gap. |
| Responsive layout | Comment spacing and stacking on mobile. |
Best practices
- Use accurate and compliant social proof.
- Avoid overly long comments.
- Test mobile readability.
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 Comment, 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 Comment, 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 Comment, 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 Comment, keep a short checklist of the fields you changed and test the result in the same browser session.