Paragraph
Use Paragraph for normal body copy and supporting text on a page.
When to use Paragraph
- Explain an offer, feature, product, or step.
- Add disclaimers, notes, helper text, or short descriptions.
- Support a heading with readable body copy.
- Add text that should not be treated as a page heading.
Content settings
| Setting | What it controls |
|---|---|
| Text field | The visible paragraph copy. |
| Type | Paragraph uses the p text tag. |
| Inline formatting | Bold, links, highlights, or inline formatting when available. |
Style settings
| Style area | What you can adjust |
|---|---|
| Alignment | Left, center, right, or justified text alignment. |
| Typography | Font family, size, weight, line height, letter spacing, and responsive typography. |
| Color | Normal text color. |
| Highlight | Highlight text colors and highlight background when highlighted text is used. |
| Hover | Hover colors when the style tab exposes hover state. |
| Spacing | Margin, padding, width, and responsive spacing from shared style controls. |
Best practices
- Keep paragraphs short enough to scan on mobile.
- Use headings for structure and Paragraph for explanation.
- Avoid pasting formatted text from external editors if it brings unwanted hidden styles.
- Check mobile line height and font size before publishing.
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 Paragraph, 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 Paragraph, 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 Paragraph, 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 Paragraph, keep a short checklist of the fields you changed and test the result in the same browser session.