We’re always looking for people who want to get involved! You don’t have to be a Flow expert.
If you’re an Admin looking to get more involved with the Flowhana…
Some great ways you can help build the site:
- Pick a piece of the Flow Wiki that needs attention and add some content to it by searching out useful articles and information on the web and adding it.
- Get familiar with the different extensions on UnofficialSF and keep your eyes out for questions on the web and Trailblazer Community where an UnofficialSF may provide a solution.
- Try out newly published extensions and new Flow functionality and blog about your experience. We’ll publish you, or if you have your own blog, we’ll blog about you and send you traffic.
If you’re a Beginner Developer looking to build your skills:
Our Developer resources start here. Consider taking an existing extension and improving it in a small way. That way you don’t have to start from scratch. When you’re done, create a pull request to contribute your improvement to the published versions of the source code and the package
If you’re a Seasoned Developer looking to build your profile in the community:
- If you have built an extension that you think might belong on UnofficialSF, send a message to us. The comment form on the homepage (unofficialsf.com) works well.
- If you post on your own, let us know when you do your own posting on Flow topics so we can drive some traffic over to you
- Keep an eye out for comments on extensions where users are reporting bugs or making feature requests. We really appreciate help making extensions better
I’m thinking of building an extension. What guidance do you have?
The two best ways to proceed are to either:
- create a new extension that solves an existing user problem that is either not possible without code, or takes too many steps, or is too complicated
- start with an existing extension and improve it by adding a useful feature or capability
The one thing that we recommend against:
- Duplicating functionality that exists already in an extension on the site. The problem with this is that users end up having to figure out and choose between similar extensions. For example, suppose you try the Generate Collection Report component and realize that it would work better with 3d graphics, and you create a separate extension called Generate 3D Reports that has most of the functionality of the original Generate Collection Report. At this point, users have to either choose between them or try to manage them both, which can be confusing. It’s just so much better for everyone to add and improve existing components, when there’s a fit. There are definitely exceptions. Sometimes, it just makes sense to start over. But this is the exception and no the rule.
Should I add a Custom Property Editor to my extension?
Yes! It’s a huge usability win to add custom property editors. Learn more here. You don’t need to start from scratch; just take an existing CPE for something like Send Better Email, Datatable, or Lookup, and modify the code.
Where can I try out ideas and get feedback?
Feel free to post to either the broad Salesforce Automation community or the smaller Unofficialsf community. For established developers of Flow extensions, there’s also an invite-only private Slack channel. In the future, we’ll have a public slack channel for extension discussion.