If you have tools like Dreamweaver, why do you need to learn HTML and CSS? -

Web beginners. Since DW can be used directly to achieve what you see is what you get, why should we learn HTML and other languages to code a line? Web beginners. Since DW can be used directly to achieve what you see is what you get, why should we learn HTML and other languages to code a line? Reply content: Yes. Using HTML and CSS to write the front-end is much easier than using Dreamweaver to make the same page, and the code is much more neat.
The subject can find a friend who is familiar with HTML + CSS to play the game, not to mention the framework and interaction effect, or bully you than that.
For this static page, the subject is written in DW, and your friend is written in a normal editor. Generally, it should be faster than your friend.
Even if you are fast, the learning cost of writing so quickly with DW will definitely exceed the learning cost of HTML + CSS. It's like the person who can play the dagger with the same attack power has been practicing it for a long time. I used DW to do a web job. It was too late to find a programmer friend to help me ......
"Isn't your job a 10-minute workload? You threw it to me. I will write it to you later ."
"Sauce, sauce! Great. Er, write? We need to use DW ...... "
"...... You are testing me. Using DW to slow me down, right. "
"...... Then you use the magic horse! "
"(Sent to a javascript) This is neatly written. "
"You Write it neatly, and then mess it up in DW! "
Then he made this look ~ Then he made this look ~ I am stupid. I have never used DW's visual design and assembly to successfully assemble a page. I have to look at my colleagues who usually work with DW. I don't know why everyone doesn't need it.
DW has only one good memory for me. It was a long time ago that we were not very familiar with the combination of colspan and rowspan for table cells, instead, DW will be opened to drag a table and merge it to see how the code is written.
Image hotspot links can be quickly obtained using DW.
Other Visualization Methods Using DW are very slow.
What DW sees and gets is not necessarily correct. For me, seeing the code is truly reliable. Otherwise, the front-end always uses various Developer Tools to view the code in the browser to debug the page.
I have never used this software since DW8.0. You drive to ask if the wheel is used ......
Okay, no. I spoke about it both upstairs and downstairs.

1. DW is generally friendly to beginners. just drag it and pull it out. What a wonderful thing. This is similar to how I learned to drag controls in. NET ......
This is not to say that this is not good, but that this convenience is not blinded.
You drag the wheel, but the important thing is how to use it.

2. I also said it downstairs. What I see is what I get.
The Compatibility solution for the front-end of the web page is too valuable.
Maybe the web page you dragged out in DW is good in the local browser, and you will kneel down when you change the browser.
What should I do? This is why we need to understand how the wheel works.

3. Writing speed. Using a notepad is enough ......

4. Support for JavaScript scripts.
The DW age should be the VBScript age. It was a long time ago and it was a recent language.

I want to add something else. I went to work.

Come back to work overtime.

5. As the comments said, DW is a drag-and-drop operation that adds more than a dozen or even 20 lines of code. What you see is a combination of effects, this CSS combination is terrible.
I'm talking about Sa? Look.
I don't mean to be ugly when I'm low. You can't drag it out in DW anyway. I don't mean to be ugly when I'm low. You can't drag it out in DW anyway.

6. If you just want to do a web job and take the test, DW will be like this. It will not be a problem. If you really want to become a front-end developer by following a learner, hurry up and study. The road to front-end is long. There is a restaurant at the door. Why should I learn to cook? If there is PS, you will not learn to use slr? Zhihu is so cheap. I always make these problems on my own and hurt the friendship between programmers and Tom. You say that PS directly generates html by cutting the graph page. Ah, hahahahaha, if the webpage layout is simple, DW does not save much time;
If the webpage layout is complex, DW may take longer;
Besides, DW is only helpful for layout. Can you use DW to write CSS 3 interactive animations?
Can you write a response using DW?
Can you use DW to write search engine optimization?

Dare not use DW to write a page and check its actual layout Implementation Method to force the powder DW?
When DW is used together, those front-ends of page layout Have to get off work?

For the front-end, the View Interface cited by beginners as an artifact is actually a pretty ridiculous chicken.

(Please don't mind if your tone is refreshed, because many front-end beginners have asked this question before, and I am so impatient ......)