deciding whether we should use or not a framework on a project depends on the project it's self , in web globally if the project is more statically then dynamically there is no need to use a framework , besides if your content will change permanently and need to be updated , in that case you should .
so we can not cite all case studies where we should use / not use a framework , it's up to the developer to make a decision based on the study he made
So if I understand correctly, for you, the biggest determinant is whether the project will have static or dynamic data. You say "if the project is more statically then dynamically there is no need to use a framework". Can you try to explain what more static than dynamic means to you? Maybe give us an example of a kind of project where you would not use a framework and one where you would.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.