Global Style
Global Style controls broad visual styling for a page.
Use it to set consistent design foundations before fine-tuning individual sections, containers, and elements.
When to use Global Style​
Use Global Style when you want a consistent base across the page.
Examples:
- Page-wide typography direction.
- Common colors and visual style.
- Reusable spacing or design patterns.
- General page appearance before element-level edits.
Global style vs element style​
| Style area | Best use |
|---|---|
| Global Style | Broad page-wide visual consistency. |
| Element Style | Specific adjustments for one selected element or container. |
Start with Global Style, then adjust individual elements only where needed.
Best practices​
- Define broad page styling before detailed element styling.
- Keep typography and colors consistent across repeated sections.
- Avoid over-customizing every element if a global rule can achieve the same result.
- Check responsive views after changing broad style settings.
- Save after major style updates.
Related docs​
FAQ​
When should I use this Global Style page?
Use this page when you need to understand the workflow, settings, or decisions related to Global Style. It is most helpful before editing a live asset, publishing changes, or troubleshooting behavior in an Atomicat workspace.
What should I check before changing Global Style?
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 Global Style 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 Global Style 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.