Every day, Salesforce Architects across the ecosystem are solving complex challenges, exploring new patterns, and helping define what the next generation of enterprise architecture looks like. As they build the Agentic Enterprise, shared experiences, real-world insights, and lessons learned help the entire community learn, grow, and innovate.
The Salesforce Architecture Blog is a place where architects come to learn, challenge their thinking, and discover what’s possible. Now we’re expanding the voices shaping that conversation.
We’re excited to introduce the Salesforce Architecture Blog: Community Author Program. Real architects. Real insights. Real impact.
Submissions are open from June 1, 2026 at 8:00 a.m. PT through June 19, 2026 at 5:00 p.m. PT. Read on for program details and submission guidance.
The Salesforce Architecture Blog: Community Author Program is an opportunity for Salesforce Architects to contribute to the Salesforce Architecture Blog, the same channel where the community already comes for real-world perspective, architectural guidance, and innovative thinking on what it means to build and design like a Salesforce Architect.
This isn’t about adding more content. It’s about adding more voices. Voices from the field, from real implementations, from architects who have navigated complexity, made hard trade-offs, and built something worth sharing. Just as community members share their expertise at events and in conversations, this program creates a new opportunity to do the same, one that lives permanently, reaches the full community, and connects your experience to the people who need it most.
We’re looking for submissions grounded in real implementation experience, including practical insights, architectural decisions, lessons learned, and patterns others can apply. Strong submissions will reflect lived experience, not just theory. Here’s what we have in mind:
If you’ve done something worth sharing, we want to hear about it.
Review the Salesforce Architecture Blog: Community Author Program Submission Guide and Blog Template for details on the submission process, program guidelines, editorial collaboration, content expectations, and blog formatting requirements.
The Salesforce Architecture Blog is read by architects who are looking for content that helps real world architectural decision making. A strong submission does not just describe what you did, but gives the reader enough of your thinking that they can make a better decision in their own context.
Before you think about writing about a product or capability, ask yourself: what is the architectural story here? What were you navigating? What were the stakes? Technology decisions become meaningful when the reader understands the context in which they were made and the alternatives that were ruled out and why.
If your post could be summarized as “here is how Feature X works,” it is not ready yet.
An architect’s value is not in providing a solution, but in being able to justify the rationale. That applies to your writing too. For every decision you describe, explain what you considered, any assumptions you made and what you ruled out. This also means going into the details of the trade-offs, rather than focusing on outcomes alone.
The reader’s context will not be identical to yours, so they will need enough of your reasoning to adapt to their specific situation. If a section only states conclusions without explaining the conditions under which they hold, expand it to provide insights into the reasoning and what made you go for one approach over another. This way other architects can apply the reasoning to their particular situation.
You do not need to share every detail of the engagement or even the entire architectural landscape. Instead, make your situation specific enough for the reader to be able to orient themselves. “We ruled out Platform Events because the subscriber could not guarantee a processing order” is more useful than “we evaluated several options.”
A well-chosen scenario or use case anchors the article in a way that generic guidance never can. Concrete yet universally applicable examples are what makes your experience genuinely useful.
Finally, what are the transferrable or universal lessons that can be learned from your experience? Can you refer to an existing resource on the Architecture Center or did you leverage a pattern that is of use to others? Increasing relevance also includes calling out the conditions that made your approach the right one, and flagging where it would not apply. If your preferred approach requires a capability that is not universally available, tell the reader what to do when they do not have it.
Tips earn their place when they are specific and grounded. “Test your automation density before choosing a pattern” is a tip. “Ensure proper governance” is not.
Prepare for your submission by completing the following:
Not every submission will be selected for publication. If selected, you’ll work with the Salesforce Architect Relations team through the review and publishing process. Authors will receive an email notification regarding their submission status by July 15, 2026.
Get the latest news related to the Salesforce Architecture Blog: Community Author Program, including submission windows, publishing opportunities, and resources for contributors.
Post them in the Salesforce Architects Trailblazer Community Group.
We look forward to seeing the decisions, patterns, and solutions you’ve been working through and how you’ll share them with the Salesforce Architect Community.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。