Dremweaver

The common (mis)conception with Dreamweaver is that Dreamweaver is designed to or is even capable of completely removing the agency of HTML and CSS coding from web design. This is like saying that a nail-gun can completely replace a hammer. A nail-gun will nail the boards together, but it is an imprecise tool, and there is a certain amount of danger while using it. If you can’t occasionally fall back on the hammer for more detail-oriented work, then there’s a definite limit to what you can build. A skilled carpenter knows how to use the hammer and occasionally does so when the nail-gun just isn’t doing what is intended.
Dreamweaver, like the nail-gun, is designed to make your life easier. You may never learn HTML or CSS, but without knowing them, you are limited to Dreamweaver’s way of doing things. This is not altogether a bad thing: 
Dreamweaver combines HTML and CSS plain text editing with a WYSIWYG tool which lets you check progress as you go or edit WYSIWYG on the fly. It's the industry standard tool for this sort of thing, although there are many, many programs which do more-or-less the same thing.
So if like us you're hooked up with the entire Adobe product family, you'll already have it - do try it out. You can also get a taster by downloading a 30 day trial.
What we normally do when we create HTML and CSS from a design, though, is split it up into different parts of the page and hand-code those parts to a high standard in terms of HTML and CSS best practice and accessibility, something Dreamweaver doesn't always encourage, and then feed those bits and pieces of HTML into the template side of a content management system (CMS).
htly narrow perspective on a large field.