<div>
Not much. &nbsp;Adobe claimed that you can configure Dreamweaver a certain way and use it to provide template/theme editing capability for WordPress. &nbsp;Problem is the claim doesn't match reality and DW ends up breaking things or, at worst, isn't any better than any other code editor. &nbsp;The WYSIWYG function is not any better than using Appearance | Customizer in WordPress at this time.
</div>


<div>
I'm not so concerned about having ability to edit an existing theme. &nbsp; Guess what I remain hopeful is there exists an stand-alone application like DW or in the old days FrontPage that would allow development that in turn would post process the necessary PHP, CSS, HTML and become a Wordpress theme. &nbsp;This idea of having to install a plugin for every feature seems like a major overkill. &nbsp; And having to get under-the-hood to actually write code seems so old-school. &nbsp; Feel like I should be able to concentrate within a design screen and let the application crunch out all the necessary code.
</div>


<div>
Well Jason, glad to have a professional clarification on post processing even though a bitter pill. &nbsp;At least that will stop me from wasting any more time digging.<br />
<br />
I read an article the other day from someone (WP purest) who was scolding WP developers about using any more than 5-plugins, otherwise learn to write code. &nbsp;Most of the reasoning due to all the overhead required for combined number of plugins, ongoing maintenance updates, etc. &nbsp;Also, he wrote, plugins, like mini-apps, naturally have a lot of code baggage just to provide easy way to add features without having to code by hand. &nbsp;Again, this was from someone in that perfect world however the project I am about to inherent currently has 32-active plugins and the website does not seem that complicated. &nbsp;Quite possibly a naive observation.
</div>


<div>
Another example of bloated code: &nbsp;when I dig through the various plugins, I see common .js libraries being used. &nbsp; Not unusual to see 10 active plugins using the same libraries rather than having a central repository.
</div>


<div>
<blockquote>
 WP developers about using any more than 5-plugins, otherwise learn to write code.
</blockquote>
<br />
Well, I'm sure if all the people using WordPress could write their own code, they would :) &nbsp;That being said, 5 plugins is a little optimistic for most sites. <br />
<br />

<blockquote>
Most of the reasoning due to all the overhead required for combined number of plugins, ongoing maintenance updates, etc. &nbsp;Also, he wrote, plugins, like mini-apps, naturally have a lot of code baggage just to provide easy way to add features without having to code by hand. 
</blockquote>
<br />
Yes and no. &nbsp;There is a bit of hit but that's what caching and optimization are for.<br />
<br />

<blockquote>
inherent currently has 32-active plugins and the website does not seem that complicated. 
</blockquote>
<br />
Depends on what the plugins are and how they are used. &nbsp;I've seen sites get away with 10 or fewer and other sites running 50+<br />
<br />

<blockquote>
Not unusual to see 10 active plugins using the same libraries rather than having a central repository. 
</blockquote>
<br />
This is where WordPress helps, though. &nbsp;Plugins should be queuing those library calls with wp_enqueue_script() which ensures only one call gets made on the front end. &nbsp;The plugins themselves don't know what is installed or running, so there is a trade-off made. &nbsp;The thing is, it works.
</div>


<div>
<blockquote>
The days of letting an application write the code for you from the design screen are mostly dead and gone.
</blockquote>
<br />
Maybe not.<br />
<a href="https://wp-types.com/" rel="ugc">https://wp-types.com/</a><br />
<a href="http://www.elegantthemes.com/gallery/divi/" rel="ugc">http://www.elegantthemes.com/gallery/divi/</a><br />
<a href="http://www.cozmoslabs.com/wck-custom-fields-custom-post-types-plugin/" rel="ugc">http://www.cozmoslabs.com/wck-custom-fields-custom-post-types-plugin/</a>
</div>


<div>
Thought you wanted to stay away from adding overhead? Those all add extra crap to a WordPress install, including lots of JavaScript and CSS includes. <br />
<br />
If plugins or &quot;plugins as themes&quot; are considered to be in the same level as Dreamweaver then my answer has to change out of necessity.
</div>


<div>
Beaver Builder is an intuitive drag and drop page builder plugin for WordPress that aims to help you build custom websites in minutes not months.<br />
<br />
<a href="http://www.wpkube.com/drag-drop-page-builder-plugins-build-website-zero-effort/" rel="ugc">http://www.wpkube.com/drag-drop-page-builder-plugins-build-website-zero-effort/</a>
</div>


<div>
<div class="content wysiwyg-content">
Recently I became aware of several tutorials on how to configure Dreamweaver with WordPress (or vice versa). &nbsp; &nbsp;Has we wondering what that combination will provide?
</div>
</div>


Recently I became aware of several tutorials on how to configure Dreamweaver with WordPress (or vice versa).    Has we wondering what that combination will provide?

Dreamweaver CS6 with WordPress

Adobe Dreamweaver is a web development tool featuring both WYSIWYG and code editors that allow the user to quickly and easily build websites in a wide variety of languages, including ASP, ASP.NET, ColdFusion and PHP. It also offers support for CSS and JavaScript.

Adobe Dreamweaver

WordPress is a free and open-source content management system (CMS) based on PHP and MySQL for creating websites and blogs. Features include a plugin architecture, a template system and strong management, customization and search systems; through its dynamic presentation of content, webmasters have the flexibility to create websites easily.