LIGHTNING WEB COMPONENTS
YOUR DOOR TO PROGRAMMING WITH WEB STANDARDS
The agenda is to combine
Salesforce knowledge
with familiar technologies like
HTML, JavaScript and CSS
to build next-gen Salesforce applications — a model shaped around user experience and development.
1. THE LWC MODEL
A programming model that lets you build modern Salesforce UI using core web technologies instead of proprietary workarounds.
🔑 BUILT ON
HTML — structure of your component
JavaScript — defines the core business logic
CSS — look, feel and animation of your component
💡 CORE IDEA
Combines Salesforce knowledge with web dev skills
Centred on user experience and development
2. WHY LWC
Modern browsers are built on web standards — LWC is designed to take full advantage of that.
Get Siddarthsaidutt’s stories in your inbox
Join Medium for free to get updates from this writer.
✅ KEY REASONS
Modern browsers are based on web standards.
Standards keep evolving, constantly improving what browsers can present to a user.
LWC uses core web component standards.
Provides only what’s necessary to perform well in the browsers Salesforce supports.
Because it leans on native browser capability rather than a heavy framework layer, LWC stays lightweight and fast.
3. TOOLS & ENVIRONMENT
To develop LWC efficiently, set up the following tools and environment first.
📦 WHAT YOU NEED
a. Developer Org / Console
b. Code Builder
c. Dev Hub and Scratch Orgs
d. GitHub — version control
e. These tools together give you a place to create, test and version your Lightning Web Components.
4. SETUP & DEVELOP
Local development is done using VS Code together with the Salesforce Extension Pack.
📋 SETUP STEPS
To build a data display element for a specific field or custom object, first set up an org
Develop LWC locally using VS Code
Add the Salesforce Extension Pack after installing VS Code
</> REQUIRED TOOLS
// what you need installed
1. VS Code
2. Salesforce Extension Pack
3. Salesforce CLI
Why It Matters :
The mindset shift LWC brings to Salesforce dev
▶ Web-standards first, not platform-proprietary first
▶ Reuses skills developers already have in HTML/JS/CSS
▶ Lighter weight than older component frameworks
▶ Built for performance across supported browsers
▶ Designed around real user experience
▶ Scales from a single field to full custom-object UIs
