Tweet
I'm just beginning my journey with EspoCRM and I'm curious if there is a widely accepted set of best practices about making easy to add additions similar in nature (not functionality) to the add-ons that EspoCRM provides. My thought is building customizations to espoCRM as standalone "plugins" similar to WordPress publicly avaiable on github that would be just as easy to add as EspoCRMs add-ons. Has EspoCRM published an add-on standard?
For example I want to investigate one of my team members spending some time to create an add-on that adds the options to "Encrypt This Field" and stored an encrypted version in the database tapping into the same encrpyption that the password systems uses. I also want to add a Show Text so that it's displayed as ***** until you reveal it.
Then... I want to host it on github or similar repo so that anyone who wants to add it to their instance can do it somewhat easily.
Is there a standard process for this already? Just want to make sure any time/energy we spend on this goes back to the community and can be re-used. Just floored by how robust this free tool is.
For example I want to investigate one of my team members spending some time to create an add-on that adds the options to "Encrypt This Field" and stored an encrypted version in the database tapping into the same encrpyption that the password systems uses. I also want to add a Show Text so that it's displayed as ***** until you reveal it.
Then... I want to host it on github or similar repo so that anyone who wants to add it to their instance can do it somewhat easily.
Is there a standard process for this already? Just want to make sure any time/energy we spend on this goes back to the community and can be re-used. Just floored by how robust this free tool is.
Comment