The SFITDelivery Knowledge Hub is now live at sfdevops.info and fully open source on GitHub.
This launch turns nearly four years of notes, templates, and delivery lessons into a public knowledge base for Salesforce teams. The goal is simple: make practical DevOps and Delivery Management guidance easier to find, reuse, and improve. Too many teams still rebuild the same release process, branching model, deployment checklist, and environment controls from scratch. This hub is meant to help with that.
What You Can Read Today
The site already includes practical content across the core areas of Salesforce delivery:
- Roles and responsibilities for DevOps specialists and Delivery Managers
- Git strategies for Salesforce teams, including Trunk-Based Development, Git Flow, Org Branch, parallel releases, feature branches, and hotfix paths
- Release management topics such as planning, release on demand, incremental releases, large-scale delivery, and anti-patterns
- Salesforce deployment fundamentals, metadata delivery options, test execution, destructive changes, Quick Deploy, and packages
- Delivery strategies such as phased rollouts, dark launches, blue-green deployment, big bang, and A/B testing
- Environment management and operational controls, including monitoring, backups, debug logs, Event Monitoring, and Security Health Check
- Tooling guidance comparing platforms such as Copado, Gearset, and Salesforce DevOps Center
The strongest content today is intentionally practical and Salesforce-specific: branching, release process, deployment, environments, and operational reliability. This is not generic DevOps advice rewritten for a different platform. It is focused on the decisions Salesforce delivery teams actually make.
What Comes Next
This is only the first public release. The roadmap continues into Delivery Management, process maturity, prioritization, quality control, audit, automation, and AI-assisted workflows for Salesforce teams.
You can follow planned and upcoming content on the Knowledge Hub Content Board.
Who This Is For
If you work in Salesforce delivery as a DevOps engineer, Delivery Manager, release manager, architect, admin, or tech lead, this project is for you.
Start with the introduction, explore the sections that match your current challenge, and use the repository as a practical reference point for building better delivery processes.
Contribute
This is a living knowledge base, not a finished book. If you have a better branching model, a stronger rollout checklist, a deployment edge case, or a lesson learned from a real project, contributions are welcome.
Open an issue, suggest an article, submit a pull request, or share the hub with your team. The more practical experience we can capture, the more useful this project becomes.
Meet in Berlin
If you'll be in Berlin on May 8, 2026, I'll also be speaking at Wir sind Ohana about optimizing releases for Salesforce projects in a session called Small or Large, Often or Rare? How to Optimize Releases. It is closely connected to the same problems this Knowledge Hub is built to solve, so feel free to join the session and say hello.