A reference book that grew into a whole learning hub.
Salesforce Dictionary started as a glossary. It is now where 1,300+ terms, cert prep, interview prep, developer tools, daily quizzes, study cohorts, and a community of learners live under one roof. Free.
Hi, I'm Dipojjal.
I've been a B2C Salesforce Solution Architect for 13+ years now, and the same thing kept happening: I'd hit a term in a release note, a customer call, or a study guide, and the official docs would assume I already knew it. So I started keeping a notebook of plain-English definitions for myself.
That notebook became a website. The website became a habit. Somewhere along the way it stopped being just a glossary, picked up cert prep, then tools, then a community, and turned into the thing you're looking at today.
I still write and review every entry myself. If something on the site is wrong, unclear, or missing, that's on me, and I want to hear about it.
How a personal cheat sheet became a learning hub
The first version of Salesforce Dictionary was a single page of definitions I'd written for myself while studying for certifications. Every time a teammate asked me "what does Xactually mean?" I'd send them my notes. After the twentieth time, I figured I should just put it online.
Then people started asking for more. Can you cover errors too? Can you put the acronyms in one place? Can you compare Flow vs Process Builder side by side? Can you write practice questions?Every "yes" turned into a new section. The site you're looking at now is what happens when you keep saying yes for a few years in a row.
What hasn't changed: every term is still written or reviewed by someone who works in Salesforce every day, every entry has a definition anda real-world example, and the whole thing is free. No paywall. No "upgrade to see the answer." No selling your email to a course bundle.
What has changed: there's now a whole platform around the dictionary. Here's the short tour.
What's on the site today
Six product pillars, all free, all built to fit together. Use what you need, skip the rest.
Dictionary
The original mission, still the heart of the site. Plain-English definitions with real-world examples, plus acronyms, error look-ups, side-by-side comparisons, pillar guides, how-to walkthroughs, code snippets, and a Salesforce reference library.
Cert & Interview Prep
Practice questions, full mock exams, and daily warm-ups across Admin, Developer, AI Associate, Agentforce, and Architect tracks. Role-based interview Q&A, an AI mock interviewer, and a salary calculator built on live community data.
Free Developer Tools
Two dozen in-browser utilities that run without an account: SOQL formatter, Apex code cleaner, 15-to-18 ID converter, JSON-to-Apex DTO generator, Cron builder, Org Organizer, and more. Nothing leaves your browser.
Daily Learning Habit
Daily Salesforce news, a daily quiz, a daily crossword, themed weekly challenges, spaced-repetition flashcards, structured learning paths, setup paths, and a release-notes digest filtered by your role.
Community & Streaks
Activity feed, member profiles, study cohorts, leaderboards, badges, XP and level progression from Apprentice to Trailblazer, streak buddies for accountability, and a community wishlist where you vote on what gets built next.
Content & Mobile
In-depth blog guides and a Salesforce news feed with auto-linked dictionary terms. iOS and Android apps for learning on the move. A weekly newsletter if you prefer it in your inbox.
Our editorial principles
If you can't define it without using three more jargon words, you don't understand it yet. Every entry starts with a one-sentence definition a non-Salesforce person could read.
Abstractions are useless without a concrete instance to anchor them. Every term ships with a real-world scenario, not just a docs-style restatement.
No paywall, no email-required, no 'sign up to unlock'. Sign-in is only there if you want to save terms, track streaks, or take notes. Free.
Written by someone working in Salesforce every day, for admins, developers, consultants, architects, and anyone trying to learn the platform without dying inside the docs.
Spotted an error? Want to suggest a term?
This is still a one-person project at the core, and feedback from the community is what keeps it moving. Drop a note, suggest a term, vote on the community wishlist, or just say hi. Every message helps.