Background Context
We’ve seen a common pattern emerge when it comes to FIs, vendors, 3rd party developers in general requesting to meet with the DevRel team to ‘Discuss the Banno Digital Toolkit’.
Historically, we’ve tried to steer folks in the direction of first reviewing the resources from our Public Resources to Share before coordinating a meeting. Folks often respond by saying that they have indeed read the docs but still have questions (which at this point are usually not provided to us in advance).
However, once we end up in the actual meeting itself, it becomes obvious that they haven’t read the docs. We then spend most of the meeting listening to their questions and responding with links to the materials in the docs that directly answer their questions.
This doesn’t scale.
We need a way to firmly (but professionally) steer folks in the direction that helps them and helps us. The pre-canned messages below are a quick and easy way to respond to emails that are requesting a meeting with us to ‘Discuss the Banno Digital Toolkit’.
Pre-canned Messages
Plugin Framework
This is a pre-canned message that can be used if folks are looking to meet with us about building a plugin or otherwise ’extend the Banno UI'.
Copy-and-paste this into the email
Our model for supporting financial institutions, fintechs, and vendors is such that we really encourage folks to read our documentation for the Digital Toolkit and work through the free, publicly available resources: https://jackhenry.dev
We prefer for folks to post their questions on Stack Overflow for the collective benefit of all developers using the Digital Toolkit: https://stackoverflow.com/questions/tagged/banno-digital-toolkit
We also have a monthly Digital Toolkit Meetup where we answer live technical questions from the online audience. We encourage developers to register: https://www.jackhenry.com/resources/events
After having done all of the above, we are more than happy to answer specific technical questions that are not covered in the documentation.
If there are technical questions which are not answered by the documentation, not resolvable via Stack Overflow, or could not be covered in the Digital Toolkit Meetup, then we request sending a list of those questions first. We'll work to answer them via email and jump on a call only for those questions that we can’t answer via email.
When to use?
The Plugin Framework is an increasingly popular part of the Toolkit. As such, this is the most likely reason that FIs, vendors, 3rd party developers in general would want to meet with our team.
Also, the Plugin Framework documentation exercises a bunch of different aspects of the Toolkit and is useful for providing broad general knowledge of the Toolkit.