Before you learn any Framework read this:
https://www.nairaland.com/3522621/what-need-know-before-learning#51983842

dhtml18:
I am not condemning frameworks mind you, but everything has its tools. I just developed a website of recent - it is my biggest work so far (not financially but in terms of scope - like 100k+ users bombarding the website simultaenously, combining 2 servers to power the site plus mobile application API, third party APIs etc). I was going to use my framework but when i weighed the options properly, I eventually used drupal 7 CMS and it worked fine.
I figured that I could have done custom coding, but really, I did not have the time to do that.

Mmm?

I have coded RAW and with FRAMEWORKS, frameworks have way too many advantages compare to it's disadvantages.

Truth is - you only enjoy frameworks when you understand how it was built.

Instead of building my own framework, i'll rather pick one framework then tear it into pieces, hide it's traces (this is like building urs too as that's what most people who claim to have built a framework do), then build extensions/packages for it.

This way, i have saved time and i still maintain standard codes, proper directory structure and good naming conventions (so i don't start calling something "manager" instead of "controller"). Besides, there are frameworks that puts you in complete control, you only require certain dependencies when you need them. It also makes it easier to work as a team ( a fellow team member knows where to find routes and middlewares and need not ask too many questions).

Finally, the proper way to learn should be to learn the language, then pick a framework if need be.