Resources
Links and resources
The sources this guide draws from. OmniStudio is mid-transition from the managed package to the platform-native standard runtime, so always cross-check against the release notes for your org's version.
Official Salesforce documentation
- Custom Styles for OmniScripts: the overview of every supported styling method.
- Apply Custom Styling to OmniScripts with Static Resources: the Custom Lightning Stylesheet File Name mechanics.
- Customize SLDS Design Tokens in OmniScript: the tokens field, the naming conversion, the multi-runtime prefixes, and the Safari limitation.
- OmniScript Best Practices: the official design, performance, and accessibility guidance, including the element and nesting limits quoted in this guide.
Design system references
- Lightning Design System: component blueprints, utility classes, and the token catalog.
- SLDS 2 Global Styling Hooks: the --slds-g- system that replaces design tokens in SLDS 2 themes.
- SLDS Design Tokens in LWC: which tokens have global access and how the --lwc- conversion works.
- SLDS Styling Hooks in LWC: component-level hooks like --slds-c-icon-color-background.
- What Are Styling Hooks?: the readable introduction to the hook system.
- Newport Design System on GitHub: the CSS framework behind the Newport theme, with build and deploy documentation.
What's changing
- What's New in OmniStudio Standard Designers: the move from the managed package to platform-native designers and runtime.
- Release notes for your org's version: markup and setup screens shift three times a year, and this is where the shifts are announced.
Learning paths
- Trailhead: OmniStudio OmniScripts: the designer fundamentals.
- Trailhead: OmniStudio Development Essentials: best practices and developer tooling.
OmniStyler tools
- The generator: scoped Experience Cloud CSS, OmniScript static resource CSS, Setup design tokens, safety checks, and placement instructions, all from one set of brand inputs.
- The OmniStyler Inspector Chrome extension: pick a live component on any Experience Cloud page, test that a selector really reaches it, preview CSS in place, and hand the capture off to the generator.
A note on freshness: this guide was last verified against Salesforce documentation and live portal markup in June 2026. The stable selector families and the three-placement model have held for years; the setup screen locations are what move. When in doubt, trust your org's DOM over any article, including this one.