To prevent you being considered a spammer, I removed all the URL's from your post - they don't add anything and could easily get you hit with the Ban Hammer.
Quote:People say do projects to learn but I really don't know how that works.
It works the same way as learning to ride a bicycle! You can watch the Tour de France all you want, frame by frame if you want to - the first time you get on a bicycle you are going to fall off because you don't have the "muscle memory" and "ingrained reflexes" keep one upright. The way you teach a child to ride a bike is to fit training wheels, and let their body slowly work out what to do. At some point, the training wheels can come off and the body takes their place.
But you could ask the child "How do you do that? What keeps the bike up?" and they still couldn't tell you - they don't know how they do it!
That's what a skill is: something that you only ever develop by using it.
Coding is the same: you can watch all the tutorials you want (though to be honest if you are watching them on YouTube et al that's normally a complete waste of time anyway) but you won't learn how to develop your own apps.
Same goes for ES6, C#, and all the "detail languages" - they are complicated beasts these days thanks to the highly necessary frameworks (or "baggage" as some call them) they rely on.
Practice is the only thing which gets you competent at anything - even eating with a fork took a good deal of that before you stopped missing the mouth.
If you want to proceed and get a job in the industry, you have to practice:
1) Specify what you want to produce - overview, detail, user interface, completion conditions
2) Design a system that gets you through those stages, and decide what you need to make it work: Databases, test data, structures, algorithms.
3) Code the basic framework. Really basic. Test it. Make it work.
4) Flesh out a tiny bit of the project. Really tiny. Test it. Make it work.
5) Repeat 4!
At some point you reach the completion conditions, and you're done.
If you decide it's too much bother and forget about it, then maybe the project was too big for you, so shelve it and try something smaller then come back when you are more skilled.