Trail Assembly takes contributions from anyone working in the Salesforce ecosystem — admins, developers, consultants, architects. You keep your byline, your bio, and your links. There is no paywall and no exclusivity clause.
What we publish
- Error walkthroughs. A specific error, what causes it, how to fix each cause, how to verify. These are the most useful pieces on the site.
- How-tos you have actually performed in an org, start to finish, with your own screenshots.
- Feature assessments. What a new feature does, where it falls short, who should wait.
- Architecture and decision write-ups. Two viable approaches, the tradeoff, which you chose and why.
- Post-mortems. Something broke in production, here is what we learned. These are rare and valuable — write them if you can.
What we turn down
Anything restating documentation without adding experience. Untested tutorials. Certification exam questions or dumps, without exception. Thinly disguised product marketing. Pieces assembled from other blog posts. Anything containing real customer data or screenshots from a customer org.
What a submission needs
- Firsthand evidence. At least three of: your own screenshots, the release you tested against, a real error message you hit, an actual limit or number you reached, a gotcha the docs omit, an argued opinion, or what you tried that failed.
- The answer in the first paragraph. Tell the reader the fix, then explain it.
- Original writing. We run an originality check on every submission. Quote briefly and link; never paste and reword.
- Your own images, from your own dev org, with fabricated data. Never another site’s images, never Salesforce’s logos or mascots.
- Links to official documentation for the claims you make.
- A two-sentence bio and where you want links pointed.
How the process works
- Pitch first — two or three sentences on the problem and what you tested. Do not write the whole piece before pitching.
- If it fits, you get a contributor account and write directly in the site editor. You can save and submit for review; you cannot publish, which protects you as much as us.
- We edit for accuracy and structure and check every claim independently. We do not rewrite you into a house voice — your writing should still sound like you.
- You see the edits and approve them before anything goes live.
- Published with your byline, bio, and links.
What you get, plainly
There is no payment. What you get is a byline on a site built for search traffic, editing that makes the piece better, and a portfolio item you can point a hiring manager or a Salesforce MVP nomination at. If that is not worth your time, that is a completely reasonable conclusion.
Pitch
Email hello@trailassembly.com with your pitch. Put the problem in the subject line. We reply either way.