Skip to content
Agent Jimmy at the centre of branching Salesforce learning paths for administration, development, and architecture.

Salesforce Guides

Choose a connected learning journey or go straight to the Salesforce skill, product, or role you need.

Salesforce is too broad for one sensible reading order. Someone learning how objects and sharing fit together needs a connected foundation. Someone diagnosing a non-selective query or deciding whether to use SOSL needs a direct route to that problem.

JamForce organises guides in both ways. Follow the Salesforce Developer Journey when each concept needs to build on the one before it, or choose a specialist collection when you already know where the friction is.

Start with the row closest to the decision in front of you. You can follow a collection in order, but you do not need to restart from platform basics every time you need one focused answer.

What you needStart hereWhere it leads
A complete route through SalesforceSalesforce Developer JourneyPlatform foundations, administration, development, UI frameworks, and production judgement.
A stronger platform foundationHow the Salesforce Platform worksUsers, data modelling, automation, reporting, data management, and sharing.
Help running an existing orgOrg Health and MonitoringUI customisation, Flow, approvals, metadata, email, sandboxes, and release discipline.
A move from clicks into codeDeveloper Mindset and ToolkitApex, queries, triggers, asynchronous work, integrations, testing, and deployment.
Safer and more capable queriesSOQL FundamentalsFiltering, relationships, aggregates, dates, performance, security, APIs, and dynamic SOQL.
Search across objects and fieldsWhen to use SOSLSearch syntax, result shaping, limits, security, and Apex integration.
Clarity about the ecosystemSalesforce Products or Salesforce RolesProduct boundaries, role responsibilities, career direction, and the hand-offs between teams.

🚀 Follow the connected Developer Journey

Section titled “🚀 Follow the connected Developer Journey”

If you are unsure where to begin, start here. The Developer Journey moves from the platform model into real org administration, then into code and the UI layer. It is designed so that later decisions about Apex, security, integrations, and deployment rest on context you have already built.

Salesforce Developer Journey moving from platform fundamentals through administration and development to user interface frameworks

The route is intentionally wider than a developer syllabus. Good Salesforce developers need to understand how admins operate the org, how access is designed, and why a technically valid change can still create an operational problem.

You do not have to start at the beginning. These are the four points people most often join at:

Use these when you have a defined subject rather than a whole career path to work through. Each collection has its own starting page and reading order, while cross-links bring in the wider platform context where it matters.

🎯 Start with the decision in front of you

Section titled “🎯 Start with the decision in front of you”

If you are learning Salesforce from the beginning, use the Developer Journey and keep a practice org beside you. If you arrived with a specific problem, open the closest specialist collection and follow its cross-links only when you need more context. The aim is not to read every page. It is to understand the next decision well enough to make it safely.

Looking for a release change, migration deadline, or a production incident rather than a learning path?