Configuration packages provide a nice way to put all configuration items related to the same thing in one place - helpers, templates, scripts, automations, etc. Conversely, blueprints put the templates in a file in one folder, the automations in a different file in a different folder and the scripts in yet another file and folder. This diminishes the convenience of the author, the understandability by a maintainer and the ease of use by the consumer. Also, blueprints do not support helpers so helpers have to go in a normal configuration file, also diminishing the author’s, maintainer’s and user’s ease of use.
I would agree that keeping all blueprints in one dedicated folder is not convenient.
There should be a possibility to keep them in any folder / any file in a config-split configuration.