Salesforce Calls SLDS 2 'a Path to the Future' — Details Are Thin

Salesforce has published an article titled "What is SLDS 2? It's a Path to the Future," framing the second generation of its Lightning Design System as a strategic bet rather than a routine version bump. That's the strongest fact available: a vendor committing, in its own headline, to a successor of the design system that has governed its UI since the Lightning era. What the announcement does not include matters just as much.

The piece offers no version number, no release date, and no migration timeline. It names no WCAG criteria, ships no Figma libraries, and cites no research method or sample size. For a design system used across Salesforce's entire product surface — from Sales Cloud consoles to Flow builders — that absence is loud.

What is SLDS, and why does a sequel matter?

The original Salesforce Lightning Design System gave the company a shared vocabulary: tokens, component specifications, and markup patterns that third-party developers on AppExchange depend on. Any successor rewrites the contract those developers build against. When a platform the size of Salesforce touches its component layer, ISV teams re-audit every screen.

SLDS 2, per the article's framing, is positioned as direction-setting. The phrase "path to the future" signals intent — an architecture meant to carry the next decade of interface work. But intent isn't a spec. Skeptics will note that design-system sequels at enterprise scale usually arrive with deprecation schedules, codemods, and a compatibility matrix. None of that appears here.

What does the announcement leave unsaid?

Plenty. Three gaps stand out:

• No accessibility commitments. Nothing references WCAG 2.2, success criterion 4.1.1's removal, or keyboard-navigation guarantees — baseline expectations for any enterprise design system in 2024 onward.
• No adoption mechanics. Will SLDS 2 ship as an opt-in package, a parallel library, or an in-place upgrade? Silence.
• No outcome claims. The article promises a future without quantifying one. No task-time improvements, no reduced CSS payload, no component-count targets.

This is a teaser, not documentation. That's fine as marketing. It's thin as guidance for the thousands of teams who build on SLDS today.

Should teams prepare now?

Not yet, on this evidence. One article with a forward-looking headline gives designers nothing to prototype against. The disciplined move is to watch for the artifacts that make a design system real: token files, changelogs, component APIs, and a stated date.

Salesforce says SLDS 2 is a path to the future. The company has yet to publish the map — and until it does, teams building on the Lightning Design System should treat the claim as a promise, not a plan.