My question has more to do with 'best-practice' approach of creating plugins for Atto, and not so much a technical query. I use an example below, but I'm more interested in discussing the best overall approach, and not in finding a solution to this particular case.
Use Case: We need to be able to set the colour of font to predefined brand-specific colours. However the generic FontColor plugin, that ships with Atto, has only a few select colors to choose from (not the exact colours we want).
My question: should we create a new plugin, that mimics the functionality of the existing FontColor plugin exactly, the only exception being the colors it makes available? Or should we edit the existing FontColor plugin to offer our brand-specific colours?
I prefer the original approach as we then dont have to fiddle with the FontColor plugin at all, and therefore benefit from any code maintenance to that plugin moving forward. The downside being that the additional button in our toolbar is going to clutter the editor, and will suck up more of my dev time.
The lazy developer in me points out that it would take only a few small changes (and not much time) to edit the plugin and make the new colours available. The downside of this approach being that we have custom changes to a plugin that may be updated in future and may conflict with our changes.