In reply to Álvaro.

That's similar with plugins already now. Currently you find your needed functions in different plugins, the majority of each plugin functions are never used, and majority of WordPress site owners do not know how to write own plugins. That's why wp.org provides a plugin repository.

A blocks repository needs to be provided by wp.org itself, similar to plugin repository, but for single blocks. Third party repositories (this can be "plugins with many blocks" or "some external blocks cloud") are no solution. Would be a loss of qualitycontrol as well as gdpr issues.

CMS-agnostic blocks would require js-only blocks, which Gutenberg tries to achieve (at least in its theoretical concept), but as @Otto explains above, it does and will never work for more complex serverside provided dynamic data. The current REST API is not abtract enough, it is just a "hacked up" version of the old REST API and atm. causes more problems than it solves.

To get CSM-agnostic serverside data, a whole new and well structured API would be necessary, name it "Fields API" or whatever you like, but as @photomatt explained in "State of the word 2017", this proposal has been rejected for the time being.

TLDR: Since you're not a dev, you need to hire devs, with Gutenberg even more than before.