Get Help and Support with SLDS 2
Learning Objectives
After completing this unit, you’ll be able to:
- Answer some of the most frequently asked questions about SLDS 2.
- Describe how to get support if you need it.
- Explain how to support your org through its lifecycle in SLDS 2.
Got Questions?
As you learned, transitioning your code to SLDS 2 isn’t scary. In fact, it’s a great opportunity for efficiency gains and code modernization. Even so, sometimes you still have questions. Here are some of the most common questions that we receive.
Will SLDS 2 affect my existing customizations?
Most customizations transition smoothly to SLDS 2 due to the reliance on styling hooks. However, we recommend testing your SLDS 2 code thoroughly in your sandbox environment. Check the Get Started: Developers Guide for a full list of tests and checks.
Here are some common, expected behaviors.
Usage Pattern |
Expected Behaviors |
|---|---|
Uses Lightning Base Components (LBC) |
No action required because LBC automatically adopts SLDS 2. The only exception is if you applied custom CSS overrides to your LBC. |
Uses supported SLDS styling hooks and classes correctly |
|
Uses CSS overrides |
|
Uses deprecated syntax |
Update old BEM syntax. Example:
|
Doesn’t use SLDS styling hooks and classes correctly |
|
Can I switch back to SLDS 1 if needed?
Yes, you can toggle between SLDS 1 and SLDS 2 by following these steps.
- In your org, in Setup, search for and select Themes and Branding.
- Choose an SLDS 1 theme and select Activate.
SLDS 1 is now on for the entire org. We do recommend that you transition fully to SLDS 2.
Will this new design be available for Experience Cloud sites?
SLDS 2 is not currently available on Experience Cloud.
How will the new design for Lightning UI affect my AppExchange solutions?
Most AppExchange solutions work with the new design, but we recommend testing each in your sandbox environment. The transition of an AppExchange solution to SLDS 2 is dependent upon the ISV partner who created that solution. For issues, reach out to the ISV partner who developed and maintains your solution.
Will I need to retrain my users on SLDS 2?
While the new design is intuitive, we recommend familiarizing your users with the changes. Read the SLDS 2 website for more information.
What’s currently supported and what’s not supported?
We’re rolling SLDS 2 out incrementally across Salesforce products and editions. Read Salesforce Cosmos Theme and SLDS 2 Availability for the most up-to-date availability info.
What are some of the known gaps with SLDS 2?
Here are some of the most common known issues or gaps.
- Variable content density, also called Cozy or Compact mode, isn’t currently supported.
- Some AppExchange solutions may not be fully compatible.
- Custom Lightning components can require additional adjustments.
- Some design tokens and styling hooks aren’t supported. For example, deprecated classes and component-level styling hooks aren’t supported.
- Some functionality in SLDS Validator, such as the design-token-to-styling-hook-mapping feature, is subject to change.
How to Get Help with SLDS 2
You transitioned your org to SLDS 2 and everything works and looks great. But maybe from time to time you still have questions. Be sure to bookmark these resources.
- Join the Design Trailblazers group (login required) to post questions, get community support, and participate in discussions.
- Read the release notes on the SLDS 2 website for announcements about SLDS 2 and developer tools.
Next Steps to Support Your Org in SLDS 2
To support your org and brand through its lifecycle in SLDS 2, follow some of the same steps you took to transition to SLDS 2. As you write and deploy new code, continue using SLDS Validator and our SLDS 2 developer tools to validate your code against SLDS 2 latest standards. Read our release notes and participate in our Trailblazer community. And be sure to share your UI designs and wins on the community, too.