Splitting core functionality to separate plugins

Hello, dear contributors and Cerebro users!

In this issue I want to raise awareness and hear your feedback about my thoughts. I see that complexity and amount of core features are growing and now it is a time to split everything and leave only really core features in the main repository and move other stuff to separate packages. For that purpose I’ve already created repositories for everything, that I think should be moved out, such as:

https://github.com/KELiON/cerebro-ui – here I want to create another package, like cerebro-tools, but with common react-components, that could be reused in plugins. It will help to have consistent UI across all plugins

Repositories for plugins:

Moving all plugins to separate repositories/packages will help to keep them small, clear, and testable. It will reduce size of application installer. Also, it will help to involve more contributors, because some developers could be more interested in helping with a specific plugin instead of dealing with huge amount of code and building process of main application.

At the same time it helps us with UX, because after that change every plugin in the system could be installed or uninstalled by the user (so, i.e. currently some users already uses duck-duck-go search, but disabling google is not possible). I thought about adding “disable” option, but why should we keep plugins, that are not used?

So, I want to track here updates of moving code out. Contributors are welcome to help – it will increase our speed of doing it! Just leave a comment if you start to extracting any plugin.

As a last step here we will have to add initial installing of some plugins and we have to decide which plugins should be included as core. As I see it, it will be: