A web framework.
It is a series of steps you can follow to build up to a real, production-ready application. I also think the way you will build out things implies a set of principles you can follow to make your life simpler.
It's reasonable to ask "in what way is that a framework?"
I view frameworks as being fundamentally about getting large groups of people to use similar technologies and approach problems in similar ways. Giving a branded set of cohesive libraries maintained by some central group is just one approach.
This will be a different one.
The idea is that there is no "it just works!" button. You have to follow through with building up the entire demo app. After that you will have something you can continue to build upon.
It is a "framework" in the sense of "it provides a direction/uniformity", but by directly tackling the education problem by having each step be incremental and "experienced." The approach here is to do things the absolute "dumbest" way possible. No automation. No boilerplate reduction. Just write the code That, in a codebase of significant size, is what scales the best.
Why does this exist?