Skip to main content
New tool CRON Expression Builder — preview next run times before you schedule Apex. Open the builder →
Contribute

Write for SFDC Developers

Publish work that other Salesforce engineers will actually use. We edit hard, test the code and give you a byline with a do-follow link — reviewed within a week.

Pitch an article
What we publish

Three kinds of piece

If it answers a question a working Salesforce developer typed into Google this week, we want it.

Step-by-step tutorials

Apex, LWC, Flow, integration and DevOps walkthroughs with code we can paste into an org and run.

Architecture and best practice

The decision rules behind a pattern — when it holds, when it breaks, and what it costs.

Career and interview material

Interview rounds, certification paths and the practical side of moving from admin to developer.

Submission process

Four steps, about a week

  1. 01 Submit the pitch Working title, outline and the one thing a reader will be able to do afterwards.
  2. 02 We reply in 3–5 days Either a go-ahead with notes, or a specific reason it is not a fit. No silence.
  3. 03 Editorial pass We test the code in a real org, tighten the copy and check every claim that carries a number.
  4. 04 Publish with your byline Author bio with a do-follow link to your profile, then promotion across our channels.
Pitch

Send us the outline

0/300

LinkedIn, personal website, GitHub, or Trailhead profile

Article Details

0 chars — aim for 50–70 for best SEO

0 characters — minimum 100 required. Use headings, lists, and code blocks for better readability.

Submission guidelines: Articles must be original, Salesforce-related, at least 600 words, and not published elsewhere. We accept tutorials, best practices, case studies, and career tips. We'll edit for clarity and SEO before publishing.