No trivial answer here. I have previously replied to related questions. Here's one that seems pertinent, related to what to learn, depending on what web role you pick...
https://answersrip.com/question/index?qid=20100709002048AA26YdD
As for "how" - that's kind of personal. I've never had difficulty reading textbooks...well, good ones, like the O'Reilly texts I mention on my richarduie "client-side programming resources" site (http://home.comcast.net/~richarduie/). I get the basic understanding of the general principles and then apply them - always been that way for me. I know people that prefer lots of examples with less formalism - not less effective in my experience, just slower. During the course of applying general principles, I make mistakes, try to figure them out, research things online, read examples, etc. I read a lot of articles on the sites listed on my resources page.
I've been professionally programming web stuff for about 12 years after programming for food in other areas for about 14 years before that...I'm getting good at it - finally. In general, be patient with yourself, take note of what works best for you and repeat, but remain willing to try new approaches.
I don't use DreamWeaver and keep trying to seduce the other developers at my shop away from it. I use Eclipse on Linux, but have also used it as well as IntelliJ IDEA on Windows in large, corporate settings. However, I'm currently in a small shop, and everyone is free to pick the tools they prefer (note that my present shop also has Mac with other tools as well...we're VERY eclectic). If DW's your IDE, you're stuck using Windows too - if you just love Windows, no worries, maybe. Using a platform-neutral IDE such as Eclipse may give you more employment opportunities in the long run, if you hope to work for larger companies. Whether you stick with DW or pick another IDE, learn to use it inside and out. Learn to make it hook up to version control repositories like CVS or (better) svn (Subversion). Final Note: out of the 100+ developers in the biggest two corporate web-dev units I've worked, only 4 (of whom I'm aware) have used DW - it MAY be suitable, if you plan to remain in small and relatively independent shops.
If you pick the developer or UIE role, learn more about how to program...not how to write a particular language, but how to think about programming. Learn about procedural programming, functional programming, object oriented programming (concentrate on OOP first) - methodologies. Learn about data design and databases. Learn XML data representations. Study Design Patterns.
To summarize, figure out the role you want to play, e.g., designer, user interface engineer, (server-side) developer, and focus on the languages, techniques, and development tools best suited to that role. Recognize that you can't be professionally competitive in all areas related to web design and development, at least not in a hurry...25+ years and I'm excellent as a developer on the server and a UIE on the client-side - I will likely never be a design wizard when it comes to graphics. There's WAY too much to learn ever to get done learning; make a good start on a subset that lets you become sufficiently expert to fill one role, and plan to explore other areas of interest as time goes by. The requirements of different jobs (freelance or corporate) may lead you to learn things in orders you wouldn't have predicted - be flexible.