Skip to main content
Featured group

Design Trailblazers

Welcome Trailblazers! ✨ Whether you’re an admin, developer, or designer, we’re here to help you design and build with Lightning Design System 2 (SLDS 2). This is your space to connect with fellow Trailblazers, ask questions, share your experiences, and collaborate on all things SLDS 2. So, what are you waiting for? Tell us how SLDS 2 is bringing your brand to life!

We'd like to turn on the setting to use SLDS 2 for pages that include <apex:slds> when an SLDS 2 theme is active in User Interface in order to take advantage of dark mode and SLDS 2 for our custom Visualforce pages. 

 

However, when we do so, some of our managed package Visualforce pages have significantly degraded appearance. This includes Salesforce's Nonprofit Success Pack Contact Merge page in particular.  

 

Is there a way to enable SLDS 2 on particular Visualforce pages (the ones we have control over) and leave SLDS 1 for the managed package ones that we can't update (and may not be able to get Salesforce to update)? It looks like there is a way to force <apex:slds> to use SLDS 1, but that doesn't really help us as we can't edit the managed packaged pages where that would be necessary. 

 

I can try opening a Salesforce support case, but since they started replacing everything with AI, it's been much more difficult to get a decent response. I suspect the answer will be to create an Idea, which will then languish for years or just be closed (which doesn't really help solve our problem).  

 

@Nonprofit Success Pack @Design Trailblazers

1 answer
  1. Sep 16, 9:21 PM

    Hi , 

     

     

    Unfortunately, I don't believe Salesforce currently provides a way to selectively enable SLDS 2 for some Visualforce pages while forcing managed-package Visualforce pages to remain on SLDS 1. If a managed package page such as NPSP Contact Merge is broken by SLDS 2, this is likely an issue that must be addressed by the package provider or Salesforce itself.

0/9000

It appears that in the Winter '27 release the "Header and Three Regions" App Page template is no longer configured with three equally sized regions, defaulting to a 60-20-20 split.  I can't find anything in the release notes about this.  Is this a planned change or an error in the release preview?

1 answer
0/9000

After enabling an SLDS2 Theme we are having reports from users that some text is difficult to read on certain monitors. In particular it seems to be the default text in list views, where the color is a light gray. I have tried changing the accent colors in the 'Advanced Configuration' section but this seems to make no difference. I have tried the default 'Salesforce Cosmos' theme as well as a new theme with the brand color set to #000000 (black) but nothing seems to change the color of this particular style of text.  

We just enabled SLDS2 and our list view text is a light-medium gray and hard to read for some users

 

 

1 answer
0/9000
0/9000
5 answers
  1. Jun 24, 10:15 PM

    Salesforce UX Designers should have these two certifications minimum depending on their level and responsibilities: https://trailhead.salesforce.com/en/credentials/designeroverview/

     

    If they are in production delivery they will need additional Consultant and Developer certifications depending on what they are designing for (ie. Admin, Platform App Builder, Business Analyst, Sales Consultant, Agentforce Specialist) 

0/9000

We have noticed that some text in emails and comments section of cases are hard to read when the text there is black or gray.  Users have to switch to light mode to read that.  

9 answers
  1. Mar 16, 5:31 PM

    Hi @Jeremy York, I'm the PM for Dark Mode & SLDS 2. You are correct Dark Mode is currently in beta, so thank you for reporting this bug. I was able to reproduce this issue in a test org on the chatter feed, so I will get this triaged in our backlog to fix. Let me know if you have encountered any other Dark Mode issues!

0/9000

Hey, builders 👋 

 

If you're building Salesforce experiences with AI tools like AF Vibes, Cursor, or Claude, the new 👉  

SLDS 2 AI Starter Kit is the best place to start. 

 

The kit gives AI the context it needs to generate SLDS 2-compatible components every time you build, alongside a local preview environment to verify the build in light and dark mode - no org required. 

 

Check it out and share your thoughts!  

Could this accelerate how you build with SLDS 2 and AI?  

 

CC: 

@Design Trailblazers

5 comments
  1. Jun 14, 7:58 AM

     Thanks for sharing, Shannon! This looks like a great way to streamline component development. I'm definitely going to test how this integrates with my current workflow and share my thoughts here. 

0/9000

Dear all, 

 

Are you able to share any expected final release date for dark mode? My Org won't allow using it since it is in Beta.

2 answers
0/9000

Hi everyone,

We are working with Salesforce Agentforce Employee Agent, and we need to store the conversations that users have with the agent for auditing and analytics purposes.

Our goal is to save:

  •  user questions 
  •  agent responses 

We would like to know if there is any standard or recommended Salesforce configuration to store the full conversation between the user and the Employee Agent, so we can later perform analysis on those conversation records.

We are especially interested in understanding:

  •  whether Agentforce already provides built-in conversation persistence 
  •  recommended architectures or best practices 
  •  if teams typically use custom objects, Platform Events, Data Cloud, Apex, Flows, or another approach 
  •  and how other organizations are handling conversation logging in production environments 

Has anyone implemented this successfully or can share the recommended pattern?      @* Customer Success * @* Known Issues * @* Salesforce Administrators * @Salesforce Flow Automation @* Salesforce Developers * @Design Trailblazers @Slack + Agentforce

  

How to save a user's conversation log with an AgentForce employee agent?

 

 

3 answers
  1. May 21, 10:15 AM

    Hi, Keep in mind that Event logs store information for seven days and consumes Data 360 credits. Enable it with below steps:

    1. From Setup, in the Quick Find box, enter and then select Agentforce Agents.
    2. Select your agent.
    3. Click the edit icon next to Keep a record of conversations with enhanced event logs to review agent behavior.
    4. Select Keep a record of conversations with enhanced event logs to review agent behavior.
    5. Save your changes.
0/9000