💻 Recap of True to the Core Deep Dive: Lightning Design System 2 (SLDS 2)
Thank you to everyone who joined True to the Core Deep Dive today, and to Salesforce Product Managers @Adam Doti, @Cliff Seal, and @Fiona Tang for sharing updates and answering your questions on SLDS 2.
🎥 Missed the session?
You can watch the full session on demand here.
💬 Still have questions?
Drop them in the comments below. We’ll do our best to get you answers!
📝 Vote on future TTTC Deep Dive topics!
Please take a moment to fill out this quick survey here to help shape future sessions.
🔗 Resources shared during the session:
🔹 Blog: The Admin Guide to Preparing Your Org for Dark Mode with SLDS 2
🔹 Design Systems on the RoadmapExchange
🔹 Trailhead Module: Dark Mode in SLDS 2: Quick Look
Have feedback on SLDS 2? Complete this survey to join the Salesforce Research Program and participate in SLDS 2 research. #True To The Core @IdeaExchange #AwesomeAdmins #Salesforce Developer #Architects #DreamDesigners #DesignersMind
@Salesforce Admins Live Sessions, @* Release Readiness Trailblazers *, @* Salesforce Platform *, @* Trailhead Official *, @Trailblazer Community Cove, @Admin Addicts, @* Salesforce Developers *, @TDX for Admins, @Architect Trailblazers
Could you help me in understanding an ISV, can we create a dedicated CSS utility file to LWC component that exists solely to export shared CSS tokens and utility classes for import across all LWCs in our package? I'm a little unclear if this is supported in packages or not.
We thought we were doing everything correctly and updating to global variables but are getting ESLint errors now tied to our LWC components.
"Using the --slds namespace for --slds-g-spacing-x-small isn't supported. Create the custom styling hook in your namespace. Example: --myapp-g-spacing-x-small"
Really just want to make sure we are handling this correctly in our 2GP.
Thank you.
