Discovery for working with plugins

[gabor-boros]

Summary

The version v0.2.0 is all about plugins, but before diving deep into the plugin architecture implementation, we should have some discovery and at least an ADR for plugins.

The following questions must be answered (at least):

• What plugin system to use, or should we build our own?
• How the plugin system will communicate with the plugins?
• What overhead would it mean to have plugins in the chosen implementation?
• What data should be available for plugins?
• What could the plugins modify?
• How would the plugins be installed?
• How could the plugins extend the front-end? Should they? How to handle cases when front-end modification is needed by the plugins?

Example Use-cases

• Let other companies to integrate
• Easy interface for Elemo to extend its functionality without being feature creep?

Drawbacks

If the plugin ecosystem is not implemented well, the code can be way harder to maintain.