Salesforce Lightning Design Systems

-

Salesforce Lightning Design Systems

Lightning Design System 

Salesforce Lightning Design System (SLDS) is a set of tools and guidelines provided by Salesforce for building user interfaces consistent with the Salesforce Lightning Experience. Benefits include efficiency, scalability, interoperability with the larger Salesforce ecosystem, and consistent design. Let’s just make sure we follow Salesforce Lightning Design Guidelines, Principles, and Best Practice 

Here are a few links -

Salesforce Figma UI Kit (Unleash the power of the SLDS UI Kit in Figma.) -Salesforce (@salesforce) on Figma Community 

Lightning Web Components (View web component JavaScript, HTML, and CSS code, then preview the output.) - Components - Salesforce Lightning Component Library 

Design System Starter Kit (Run prototypes of all sizes in the browser using SLDS.) - GitHub - salesforce-ux/design-system-starter-kit: Rapid prototyping environment using the Salesforce Lightning Design System 

Component Blueprints (Ready-to-use HTML and CSS UI elements provide the foundation for Salesforce experience development) - Blueprint Overview - Lightning Design System 

Tokens (Visual design values and attributes that ensure branding and UI consistency at scale) - Design Tokens - Lightning Design System 

Design Guidelines (Design principles and best practices that guide beautiful, consistent, user-friendly product experiences) - Design Guidelines - Lightning Design System 

Tools (Easy-to-use tools help all Trailblazers optimize workflows and bring Salesforce ideas to life)- Tools Overview - Lightning Design System 

Anti-Patterns for Styling Components (common mistakes developers make when styling Lightning web components) - Salesforce Developers 

Share CSS Style Rules (Create a consistent look and feel for Lightning web components using a common CSS module)- Salesforce Developers 

CSS (Salesforce CSS framework) - Salesforce Developers 

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more