Hello @neatudarius. I wish I had seen this topic earlier, I came to the same conclusion and I wrote this topic here. All in all, we need a core infrustructure repo that will evolve with the new standards, best practices it will add new pipelines and improve existing ones. The starting template (examplar) will have a way to update it’s core in a non-intrusive manner to the developer of the Library. The examplar (alone) is a good step forward but it doesn’t scale with the number of the new libraries created since making a change to the examplar requires to make the same change manually to all libraries that forked from the examplar. To make this happen we have to draw a line of what functionality the core infrastructure should own, what portion of this can be modified by the developer of a library that was forked by the examplar and what is the interface (folder structure, configuration files) between the two.