<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dollesh Rathod on Medium]]></title>
        <description><![CDATA[Stories by Dollesh Rathod on Medium]]></description>
        <link>https://medium.com/@salesforcebydollesh?source=rss-1c3c1104520e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*B7TE2OtW_GuuRtqtY3WWaw.jpeg</url>
            <title>Stories by Dollesh Rathod on Medium</title>
            <link>https://medium.com/@salesforcebydollesh?source=rss-1c3c1104520e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:56:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@salesforcebydollesh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to become Salesforce Admin to Developer: Your LWC Journey Starts Here]]></title>
            <link>https://salesforcebydollesh.medium.com/how-to-become-salesforce-admin-to-developer-your-lwc-journey-starts-here-34e171e92ec1?source=rss-1c3c1104520e------2</link>
            <guid isPermaLink="false">https://medium.com/p/34e171e92ec1</guid>
            <category><![CDATA[salesforce-lwc]]></category>
            <category><![CDATA[salesforce-admin]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-developer]]></category>
            <category><![CDATA[lightning-web-component]]></category>
            <dc:creator><![CDATA[Dollesh Rathod]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 07:42:23 GMT</pubDate>
            <atom:updated>2026-06-22T07:42:23.560Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Salesforce Admin to Developer: Your LWC Journey Starts Here</h3><h3>LWC Series — Part 1 of 15</h3><h3>Introduction to Lightning Web Components</h3><h3>The Complete Beginner’s Guide for Salesforce Admins Moving to Development</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y6d2VHTMB9Ni1I0A_wjSug.png" /></figure><p>You have mastered Flows. You build automations that save your team hours every week. You know Salesforce better than most developers in your org.</p><p>But there is always that one requirement — the one that comes back with “this isn’t possible without code.”</p><p>That’s where Lightning Web Components come in.</p><p>LWC is Salesforce’s modern framework for building custom UI components — and it is the single most important skill a Salesforce Admin can learn to cross into development. Not Apex. Not SOQL. LWC.</p><p>Because LWC is what users see. It is what clients touch. It is what makes a custom page feel like a product, not a configuration.</p><p>In this 15-part series, I am going to take you from zero LWC experience to being able to build, test, and deploy real, production-ready Lightning Web Components.</p><p>We start today with the foundation — what LWC actually is, why it matters for your career, everything you need to set up before writing your first line of code, and the complete roadmap of where this series goes.</p><p>Let’s begin.</p><h3>What Is Lightning Web Component (LWC)?</h3><p>A Lightning Web Component is a reusable piece of UI — a button, a card, a custom table, a full page layout — built using standard web technologies and deployed to your Salesforce org.</p><p>The key word is standard.</p><p>LWC uses:</p><ul><li>HTML — to define the structure of your component</li><li>JavaScript — to handle logic and behavior</li><li>CSS — to control how it looks</li></ul><p>If you have ever written a Salesforce Flow screen, you have already been consuming components without knowing it. Every input field, every data table, every record form on a Lightning page is built from components. LWC is how you build your own.</p><h3>LWC vs Aura — What’s the difference?</h3><p>Salesforce has had two component frameworks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFuGdy06-ORZIJEnbmR3UA.png" /></figure><p>If you are starting today — start with LWC. Always. Aura still exists and you will encounter it, but all new development should be LWC.</p><h3>Why LWC Is the Right Starting Point for Salesforce Admins</h3><p>Admins have a unique advantage when learning LWC that pure developers don’t.</p><p>You already understand the data model. You know what an Account is, why Opportunities relate to Contacts, how Profiles control what users see. You understand business problems in Salesforce language.</p><p>A developer learning LWC has to learn both the technology AND the platform at the same time. You only have to learn the technology.</p><p>What LWC unlocks for Admins:</p><p>→ The ability to build custom UI that Flow Builder cannot produce → Unique record views, custom data tables, interactive dashboards → Integration points that connect Salesforce data to beautiful, branded experiences → The credibility gap between Admin and Developer — LWC is the bridge</p><p>The career shift LWC enables:</p><pre>Salesforce Admin<br>       ↓<br>Admin + Apex + LWC Skills<br>       ↓<br>Salesforce Developer<br>       ↓<br>Senior Developer / Technical Lead</pre><p>This series is that bridge.</p><h3>The Full 15-Part LWC Series Roadmap</h3><p>Here is every article in this series — bookmark this list and use it as your learning roadmap.</p><p>See content credentials</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSsHlb_i45Z1NFZXUuglJw.png" /></figure><p>By Part 15, you will have the skills to build, test, and deploy real LWC components in production. Not just follow tutorials — actually ship things.</p><h3>Prerequisites — What You Need Before Writing Your First Component</h3><p>Work through this checklist completely before opening VS Code.</p><h3>1. Salesforce Platform Knowledge (you likely have this)</h3><p>You do not need to be a developer, but you need to be comfortable with:</p><p>✅ Objects and Fields — you know what standard and custom objects are ✅ Relationships — you understand lookups and master-detail ✅ Record Pages — you have edited Lightning App Builder before ✅ Profiles and Permission Sets — you understand access control ✅ Basic Salesforce navigation — Setup, App Launcher, Developer Console</p><p>If any of those feel unfamiliar, spend two weeks on Trailhead’s “Salesforce Platform Basics” trail before continuing.</p><h3>2. HTML Basics (1–2 hours to learn if needed)</h3><p>You do not need to be an HTML expert. But you need to understand:</p><pre>&lt;!-- A basic HTML element looks like this --&gt;<br>&lt;div class=&quot;container&quot;&gt;<br>    &lt;h1&gt;Hello World&lt;/h1&gt;<br>    &lt;p&gt;This is a paragraph.&lt;/p&gt;<br>&lt;/div&gt;</pre><p>What you need to know:</p><ul><li>Tags open &lt;tag&gt; and close &lt;/tag&gt;</li><li>Elements can have attributes: class, id, type</li><li>Elements can nest inside other elements</li></ul><p>🆓 Free resource: MDN Web Docs HTML Introduction — <a href="http://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML">developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML</a></p><h3>3. JavaScript Basics (3–5 hours to learn if needed)</h3><p>This is the most important prerequisite. LWC’s logic layer is JavaScript.</p><p>You need to understand:</p><pre>// Variables<br>let name = &#39;Dollesh&#39;;<br>const greeting = &#39;Hello&#39;;</pre><pre>// Functions<br>function sayHello(name) {<br>    return &#39;Hello, &#39; + name;<br>}</pre><pre>// Classes (LWC components are JavaScript classes)<br>class MyComponent {<br>    constructor() {<br>        this.title = &#39;My Component&#39;;<br>    }<br>}</pre><pre>// Arrow functions<br>const double = (n) =&gt; n * 2;</pre><pre>// Template literals<br>const message = `Welcome, ${name}`;</pre><p>You do not need to be a JavaScript expert before starting. But variables, functions, and basic classes are non-negotiable.</p><p>🆓 Free resource: <a href="http://javascript.info/">javascript.info</a> — the clearest free JavaScript course on the internet. Focus on the first four chapters: Basics, Code Quality, Objects, and Functions.</p><h3>4. CSS Basics (1 hour to learn if needed)</h3><pre>/* CSS controls how elements look */<br>.container {<br>    background-color: #042C53;<br>    color: white;<br>    padding: 16px;<br>    border-radius: 8px;<br>}</pre><p>What you need to know:</p><ul><li>Selectors (.class, #id, element)</li><li>Common properties: color, background, padding, margin, font-size</li><li>Box model: every element is a box with content, padding, border, margin</li></ul><p>🆓 Free resource: <a href="http://css-tricks.com/">css-tricks.com</a> — A Complete Guide to Flexbox and CSS basics.</p><h3>5. A Free Salesforce Developer Org</h3><p>Every component you build in this series gets deployed to a real Salesforce org. You need one.</p><p>→ Sign up for free at: <a href="http://developer.salesforce.com/signup">developer.salesforce.com/signup</a></p><p>This gives you a permanent, free Salesforce org for development and testing. Create this now — you will need it in Part 2.</p><h3>6. Visual Studio Code (VS Code)</h3><p>VS Code is the industry-standard code editor for Salesforce development. It is free.</p><p>→ Download at: <a href="http://code.visualstudio.com/">code.visualstudio.com</a></p><p>After installing, you need two essential extensions:</p><p>Extension 1 — Salesforce Extension Pack → Open VS Code → Extensions (Ctrl+Shift+X) → Search “Salesforce Extension Pack” → Install</p><p>This pack includes:</p><ul><li>Salesforce CLI integration</li><li>LWC IntelliSense (code completion)</li><li>Apex and LWC syntax highlighting</li><li>Org authentication</li></ul><p>Extension 2 — Prettier — Code Formatter → Search “Prettier — Code formatter” → Install</p><p>Prettier automatically formats your code. This saves time and keeps your code consistent.</p><h3>7. Salesforce CLI (sf)</h3><p>Salesforce CLI is the command-line tool that connects your VS Code to your Salesforce org — pushing code, pulling metadata, running tests.</p><p>→ Install at: <a href="http://developer.salesforce.com/tools/salesforcecli">developer.salesforce.com/tools/salesforcecli</a></p><p>After installing, verify it works:</p><pre># Open your terminal (VS Code has one built in: View → Terminal)<br>sf --version</pre><pre># You should see something like:<br># @salesforce/cli/2.x.x ...</pre><h3>8. Node.js (required by Salesforce CLI)</h3><p>Node.js is a JavaScript runtime that Salesforce CLI depends on. You install it once and never think about it again.</p><p>→ Download at: <a href="http://nodejs.org/">nodejs.org</a> — download the LTS (Long-Term Support) version</p><p>After installing:</p><pre>node --version<br># Should show: v18.x.x or higher</pre><pre>npm --version<br># Should show: 9.x.x or higher</pre><h3>9. Git — Version Control (Optional for Part 1, Required from Part 3)</h3><p>Git tracks changes to your code. Every serious developer uses it.</p><p>→ Download at: <a href="http://git-scm.com/downloads">git-scm.com/downloads</a></p><p>You do not need to use Git in Part 1 or 2, but install it now so it is ready when you need it.</p><h3>Environment Setup — Step by Step</h3><p>Once you have all prerequisites installed, connect everything together.</p><h3>Step 1 — Authenticate VS Code with your Developer Org</h3><p>Open VS Code → open the terminal (Ctrl+`) → run:</p><pre>sf org login web --alias MyDevOrg</pre><p>A browser window will open — log in to your Salesforce Developer Org. After login, return to VS Code. Your terminal should show:</p><pre>Successfully authorized your-email@example.com with org ID 00D...</pre><p>✅ VS Code is now connected to your Salesforce org.</p><h3>Step 2 — Create your first Salesforce Project</h3><p>In VS Code, press Ctrl+Shift+P (Cmd+Shift+P on Mac) → type “SFDX: Create Project” → select “Standard” → name it LWCSeries → choose a folder → press Enter.</p><p>VS Code creates a project structure:</p><pre>LWCSeries/<br>├── force-app/<br>│   └── main/<br>│       └── default/<br>│           ├── lwc/          ← Your LWC components live here<br>│           ├── classes/      ← Apex classes live here<br>│           └── objects/      ← Custom object metadata<br>├── .sfdx/<br>└── sfdx-project.json</pre><p>The folder you care about most: force-app/main/default/lwc/</p><p>Every LWC component you build in this series goes inside that folder.</p><h3>Step 3 — Set your default org</h3><pre>sf config set target-org MyDevOrg</pre><p>This tells Salesforce CLI which org to deploy to by default. You only do this once per project.</p><h3>Step 4 — Verify everything is working</h3><pre>sf org display</pre><p>You should see your org information — username, instance URL, status “Active.”</p><p>If you see this output, your environment is fully set up. You are ready to write your first LWC component in Part 2.</p><h3>🧪 Practical Demonstration — Build &amp; Deploy Your First “Hello Admin” Component</h3><p>This is the section most Part 1 articles skip. We are not skipping it.</p><p>By the end of this demonstration, you will have a real, working LWC component deployed to your Salesforce org, visible on a Lightning page. Every step is explained line by line — nothing is assumed.</p><p>What we are building:</p><p>A simple “Hello Admin” component that:</p><ul><li>Displays a personalized welcome message</li><li>Shows the current date</li><li>Has basic Salesforce styling using SLDS</li></ul><p>Simple. Focused. 100% real.</p><h3>DEMO STEP 1 — Create the component folder and files</h3><p>In VS Code, open the terminal (View → Terminal or Ctrl+`).</p><p>Make sure you are inside your project folder, then run:</p><pre>sf lightning generate component --name helloAdmin --output-dir force-app/main/default/lwc</pre><p>VS Code creates this folder automatically:</p><pre>force-app/main/default/lwc/<br>└── helloAdmin/<br>    ├── helloAdmin.html          ← We write this<br>    ├── helloAdmin.js            ← We write this<br>    ├── helloAdmin.css           ← We write this (optional)<br>    └── helloAdmin.js-meta.xml  ← We configure this</pre><p>✅ You now have an empty component ready to fill in.</p><h3>DEMO STEP 2 — Write the HTML template</h3><p>Open helloAdmin.html and replace everything inside with this:</p><pre>&lt;!-- helloAdmin.html --&gt;<br>&lt;template&gt;<br><br>    &lt;!-- Card container using Salesforce Lightning Design System --&gt;<br>    &lt;lightning-card title=&quot;Welcome to LWC&quot; icon-name=&quot;custom:custom14&quot;&gt;<br><br>        &lt;div class=&quot;slds-m-around_medium&quot;&gt;<br><br>        &lt;!-- Greeting message — binds to the &#39;greeting&#39; property in JS --&gt;<br>            &lt;p class=&quot;slds-text-heading_medium&quot;&gt;{greeting}&lt;/p&gt;<br><br>           &lt;!-- Today&#39;s date — binds to the &#39;todayDate&#39; property in JS --&gt;<br>            &lt;p class=&quot;slds-text-body_regular slds-m-top_small&quot;&gt;<br>                Today is: &lt;strong&gt;{todayDate}&lt;/strong&gt;<br>            &lt;/p&gt;<br><br>            &lt;!-- A simple styled badge --&gt;<br>            &lt;div class=&quot;slds-m-top_medium&quot;&gt;<br>                &lt;span class=&quot;slds-badge slds-badge_inverse&quot;&gt;<br>                    LWC Series · Part 1<br>                &lt;/span&gt;<br>            &lt;/div&gt;<br><br>        &lt;/div&gt;<br><br>    &lt;/lightning-card&gt;<br><br>&lt;/template&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*abtJbJKSSIGMU_3d" /></figure><h3>DEMO STEP 3 — Write the JavaScript controller</h3><p>Open helloAdmin.js and replace everything with this:</p><pre>// helloAdmin.js<br>import { LightningElement } from &#39;lwc&#39;;<br>export default class HelloAdmin extends LightningElement {<br>    // This property holds the greeting message<br>    // The value in the HTML {greeting} comes from here<br>    greeting = &#39;Hello, Salesforce Admin! Welcome to Lightning Web Components. 👋&#39;;<br>    // This property calculates today&#39;s date<br>    // JavaScript&#39;s Date object gives us the current date<br>    get todayDate() {<br>        const today = new Date();<br>        return today.toLocaleDateString(&#39;en-GB&#39;, {<br>            weekday: &#39;long&#39;,<br>            year:    &#39;numeric&#39;,<br>            month:   &#39;long&#39;,<br>            day:     &#39;numeric&#39;<br>        });<br>    }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/0*_BoI8xaUZAExbBJ7" /></figure><h3>DEMO STEP 4 — Add optional CSS styling</h3><p>Open helloAdmin.css and add this:</p><pre>/* helloAdmin.css */<br>/* This styles ONLY the elements inside THIS component */<br>/* LWC CSS is scoped - it never affects other components on the page */<br>p {<br>    line-height: 1.6;<br>}<br>.slds-badge {<br>    font-size: 12px;<br>    letter-spacing: 0.5px;<br>}</pre><p>Why this matters:</p><p>In standard web development, CSS rules can leak out and accidentally affect other parts of the page. LWC automatically scopes your CSS — the rules in helloAdmin.css apply ONLY to elements inside helloAdmin. This is one of the reasons LWC is considered a robust, production-grade framework.</p><h3>DEMO STEP 5 — Configure the metadata file</h3><p>Open helloAdmin.js-meta.xml and replace everything with this:</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;LightningComponentBundle xmlns=&quot;http://soap.sforce.com/2006/04/metadata&quot;&gt;<br>&lt;!-- API version - always use the latest supported by your org --&gt;<br>    &lt;apiVersion&gt;62.0&lt;/apiVersion&gt;<br>  &lt;!-- isExposed: true = this component can be added in Lightning App Builder --&gt;<br>    &lt;isExposed&gt;true&lt;/isExposed&gt;<br>&lt;!-- targets = which page types can use this component --&gt;<br>    &lt;targets&gt;<br>        &lt;target&gt;lightning__AppPage&lt;/target&gt;      &lt;!-- Lightning App pages --&gt;<br>        &lt;target&gt;lightning__RecordPage&lt;/target&gt;   &lt;!-- Record detail pages --&gt;<br>        &lt;target&gt;lightning__HomePage&lt;/target&gt;     &lt;!-- Home pages --&gt;<br>    &lt;/targets&gt;<br>&lt;/LightningComponentBundle&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/0*lVINfe4gxuKpdHoU" /></figure><h3>DEMO STEP 6 — Deploy the component to your org</h3><p>Save all four files (Ctrl+S on each). Then in the terminal, run:</p><pre>sf project deploy start --source-dir force-app/main/default/lwc/helloAdmin</pre><p>You should see:</p><pre>Deploying v62.0 metadata to your-email@example.com using the v62.0 SOAP API<br>Deploy ID: 0Af...<br>Status: Succeeded</pre><pre>Deployed Source<br>──────────────────────────────────────────────────────────────────────<br>State   Full Name                            Type<br>──────────────────────────────────────────────────────────────────────<br>Add   <br>  helloAdmin/helloAdmin.html           LightningComponentBundle<br>Add   <br>  helloAdmin/helloAdmin.js             LightningComponentBundle<br>Add<br>  helloAdmin/helloAdmin.js-meta.xml    LightningComponentBundle<br>Add     <br>  helloAdmin/helloAdmin.css            LightningComponentBundle</pre><p>✅ Your component is now live in your Salesforce org.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*FmWtYVBgNMAyEYX5" /></figure><h3>DEMO STEP 7 — Add it to a Lightning page in App Builder</h3><p>Now let’s make it visible to a real Salesforce user.</p><ol><li>Go to your Salesforce Developer Org in the browser</li><li>Click Setup (gear icon, top right) → Setup</li><li>In Quick Find, type App Builder → click Lightning App Builder</li><li>Click New → select App Page → click Next</li><li>Give it a label: My LWC Test Page → click Next</li><li>Choose One Region layout → click Done</li></ol><p>You are now in the Lightning App Builder canvas.</p><p>To find your component:</p><ul><li>Look at the left panel — it shows all available components</li><li>Scroll down to Custom section</li><li>You will see Hello Admin listed there</li><li>Drag it onto the canvas</li></ul><p>To save and activate:</p><ol><li>Click Save (top right)</li><li>Click Activate</li><li>In the Activation panel, click Activate</li><li>Click Save again</li></ol><p>To see it in action:</p><ul><li>Click the Back arrow to leave App Builder</li><li>Click the App Launcher → type My LWC Test Page → open it</li></ul><p>You should now see your component live on a real Salesforce page — the card, the greeting message, the date, and the LWC Series badge.</p><h3>DEMO STEP 8 — Make a live change and see it update</h3><p>Let’s prove that LWC is reactive — change a property, redeploy, and see the page update.</p><p>In VS Code, open helloAdmin.js. Change the greeting:</p><pre>// Before<br>greeting = &#39;Hello, Salesforce Admin! Welcome to Lightning Web Components. 👋&#39;;</pre><pre>// After — change to something personal<br>greeting = &#39;Hello, Dollesh! You just built your first Lightning Web Component. 🚀&#39;;</pre><p>Save the file. Deploy again:</p><pre>sf project deploy start --source-dir force-app/main/default/lwc/helloAdmin</pre><p>Refresh your browser on the Salesforce page.</p><p>Your component now shows the updated message — with zero changes to Salesforce configuration, no record updates, no Flow builder, no admin setup. You changed a line of code and it appeared on screen.</p><p>That is what it feels like to be a developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*5IwH0TYSYJ8VP-Wz" /></figure><h3>What Makes Up a Lightning Web Component?</h3><p>Every LWC component is a folder containing exactly three files:</p><pre>myFirstComponent/<br>├── myFirstComponent.html       ← The template (structure)<br>├── myFirstComponent.js         ← The controller (logic)<br>└── myFirstComponent.js-meta.xml ← The metadata (where it can be used)</pre><p>The HTML file defines what the user sees.</p><p>The JS file is a JavaScript class that controls what happens — reactive data, event handling, Apex calls.</p><p>The meta XML file tells Salesforce where this component can be placed — on a Record Page, an App Page, a Home Page, or any combination.</p><p>Here is the smallest possible valid LWC component:</p><pre>&lt;!-- myFirstComponent.html --&gt;<br>&lt;template&gt;<br>    &lt;p&gt;Hello from LWC!&lt;/p&gt;<br>&lt;/template&gt;</pre><pre>// myFirstComponent.js<br>import { LightningElement } from &#39;lwc&#39;;<br>export default class MyFirstComponent extends LightningElement {}</pre><pre>&lt;!-- myFirstComponent.js-meta.xml --&gt;<br>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;LightningComponentBundle xmlns=&quot;http://soap.sforce.com/2006/04/metadata&quot;&gt;<br>    &lt;apiVersion&gt;62.0&lt;/apiVersion&gt;<br>    &lt;isExposed&gt;true&lt;/isExposed&gt;<br>    &lt;targets&gt;<br>        &lt;target&gt;lightning__AppPage&lt;/target&gt;<br>        &lt;target&gt;lightning__RecordPage&lt;/target&gt;<br>        &lt;target&gt;lightning__HomePage&lt;/target&gt;<br>    &lt;/targets&gt;<br>&lt;/LightningComponentBundle&gt;</pre><p>Do not worry about fully understanding these files yet — we will dissect every line in Part 2. For now, recognise the three-file pattern. It is consistent across every LWC component you will ever build.</p><h3>The LWC Lifecycle — How a Component Is Born</h3><p>When Salesforce renders a Lightning Web Component, it follows a lifecycle:</p><pre>Component is needed on page<br>          ↓<br>constructor() fires     ← Component object created<br>          ↓<br>connectedCallback()     ← Component added to the DOM<br>          ↓<br>render()                ← HTML template rendered<br>          ↓<br>renderedCallback()      ← Template is visible, DOM is available<br>          ↓<br>User interacts<br>          ↓<br>Property changes → re-render<br>          ↓<br>disconnectedCallback()  ← Component removed from page</pre><p>Right now, remember two of these:</p><ul><li>connectedCallback() — runs when your component loads. This is where you fetch data.</li><li>disconnectedCallback() — runs when your component is removed. This is where you clean up.</li></ul><p>The rest become natural as you build more components throughout this series.</p><h3>5 Things That Confuse Every LWC Beginner (and How to Avoid Them)</h3><h3>Confusion 1 — “Do I need to know Apex before LWC?”</h3><p>No. You can build useful LWC components without a single line of Apex — using Wire adapters to connect to Salesforce data declaratively. We cover Apex in Parts 9 and 10 — everything before that is pure LWC.</p><h3>Confusion 2 — “Is LWC the same as React or Angular?”</h3><p>Conceptually similar — all three are component-based UI frameworks. But LWC is specific to Salesforce, uses the Web Components standard (not a proprietary model like React’s virtual DOM), and is deeply integrated with Salesforce data and security. What you learn here applies to Salesforce specifically, though the concepts transfer.</p><h3>Confusion 3 — “The meta XML file — what is apiVersion?”</h3><p>The API version tells Salesforce which platform version your component targets. Use the latest version your org supports. For 2026, that’s typically v62.0. We will always use the current version in this series.</p><h3>Confusion 4 — “Why does VS Code underline my LWC imports in red?”</h3><p>The Salesforce Extension Pack needs to be properly indexed. Press Ctrl+Shift+P → “SFDX: Refresh SObject Definitions” — this usually resolves import errors.</p><h3>Confusion 5 — “Do I deploy every time I make a change?”</h3><p>During development, yes — you push changes to your org to test them. In Part 2 we will set up a faster feedback loop using local development tools. But for now, expect to deploy and refresh the browser for every change.</p><h3>Free Resources for This Series</h3><p>Every resource below is completely free:</p><p>🆓 LWC Developer Guide (Official) <a href="http://developer.salesforce.com/docs/component-library/documentation/en/lwc">developer.salesforce.com/docs/component-library/documentation/en/lwc</a></p><p>🆓 LWC Component Library — All base components <a href="http://developer.salesforce.com/docs/component-library/overview/components">developer.salesforce.com/docs/component-library/overview/components</a></p><p>🆓 Trailhead: Lightning Web Components Basics <a href="http://trailhead.salesforce.com/">trailhead.salesforce.com</a> → search “Lightning Web Components Basics”</p><p>🆓 LWC Recipes — Real working examples <a href="http://github.com/trailheadapps/lwc-recipes">github.com/trailheadapps/lwc-recipes</a></p><p>🆓 Free Developer Org <a href="http://developer.salesforce.com/signup">developer.salesforce.com/signup</a></p><p>🆓 VS Code (Free) <a href="http://code.visualstudio.com/">code.visualstudio.com</a></p><p>🆓 Node.js (Free LTS) <a href="http://nodejs.org/">nodejs.org</a></p><h3>Final Thought</h3><p>Every Salesforce developer you look up to started exactly where you are right now.</p><p>They did not know what a JavaScript class was. They did not know what the meta XML file meant. They were confused about why their component was not showing up on a page.</p><p>The difference between them and where you are today is simply time spent building.</p><p>This series gives you the structure. You supply the time.</p><p>Part 2 is upcoming stay connected — we will write our first real LWC component from scratch, deploy it to your org, and see it live on a Lightning page for the first time.</p><h3>Question for You</h3><p>Where are you starting from today?</p><p>🔵 Salesforce Admin — no development experience at all</p><p>🟡 Admin with some HTML/CSS knowledge</p><p>🔴 Already written some Aura — moving to LWC</p><p>⚪ Something else — tell me in the comments</p><p>Drop your starting point below. I read every comment and I use them to shape upcoming parts of this series.</p><p>Enjoying Salesforce Pulse?</p><p>Subscribe to get every part of this LWC series — plus Agentforce, Data Cloud, Order of Execution, and Salesforce career content — delivered every two weeks.</p><p><em>Written by </em><a href="https://www.linkedin.com/in/dolleshrathod"><em>Dollesh Rathod</em></a><em> .</em></p><p><em>Part of the </em><a href="https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7471088887554244608"><em>Salesforce Pulse</em></a><em> Newsletter series</em> <em>LWC Mastery Series — Part 1 of 15</em></p><p>#LWC #LightningWebComponents #SalesforceAdmin #SalesforceDeveloper #Salesforce #JavaScript #Trailblazer #SalesforcePulse #LWCSeries #SalesforceCareer #WebComponents #CRM #LWC #Salesforce #SalesforcePulse</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34e171e92ec1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>