• Interesting approach, it sounds very like the approach used to generate resources for this website. I wouldn't shy away from calling it a framework, or from rewriting some libraries yourself. The downside with an agglomeration of libs/packages is that they gradually drift out of sync with each other and require vigilant updates, the upside is of course that you don't have to maintain them. There is some value I think in having examples of how to put all this together, and being able to quickly add new resources to your sites with templates.

    I would avoid the npm dependency and other libs like jquery - no need for that really. Also consider generating new resources using templates with something similar to the rails command - this is something I think rails got right.