If you want to implement a web framework, keep in mind that it will be a slow and iterative process. And don't expect to create it in a vacuum (1. make super gr

If you want to implement a web framework, keep in mind that it will be a slow and iterative process. And don't expect to create it in a vacuum (1. make super great framework 2. use it). It will be more like, you notice some patterns of repetition in the code of your existing project(s), and then you devise a way to factor that into a library. Try to implement your web framework as libraries instead of a monolithic pile of spaghetti. There are tons of design decisions you'll have to take and it's better if you can use different parts of the web framework (and perhaps write new ones) for different projects. At first your web framework will be pretty specific to your project, and you'll hit walls whenever you want to go in a direction you hadn't thought of yet. You'll see what is truly general and what's really project/section/page-specific once you have a good corpus of samples. That's how it goes for my slowly-evolving will-release-it-someday-when-it's-ready CL web framework anyway.