As a non-coding designer, I'd rather design and hand off or collaborate with a Dreamwear person who can do the html coding and maintenance. My interest is in what the viewer sees and how they use it, not necessarily know how to create code. Most of us know how to drive a car, but few know how to build one. Rather than let Muse become a "whipping post" and the bane of all Dreamweaver coders, perhaps Adobe might entertain the idea of making Muse files Dreamweaver friendly. They certainly have accomplished this in other areas ala Creative Suite. Business Catalyst is just their answer solutiion, but for many clients, isn't the way they conduct their business.

So  in the meantime, it would great if people who are Dreamweaver evangelists provide some insight about figuring out how best to make things work. I mean it's you folks that are working under the hood. And, I respect that.

Thanks,

David

No matter how onerous or horrible Muse is, my comment was to find a workable path. I mean it's easy enough to find reasons not to. That's the easy part. The hardwork or maybe not, are reasons to make it work.

You have to understand I am not talking about code, you need to take that up with Adobe, not the MU user. I'm just trying to find a workable path to solving a need no matter how distasteful you may find it.

MU is what Adobe is.

Thanks filip.scridon- I am sure most of you skilled Dreamweaver people are just that, highly skilled. I do have a modicum of expertise at multiple levels in the global process and mating resources. Part of the challenge is to match skill and willingness to slog through the "bloat" to fulfill client expectations. They don't pay for "no" answers. There are several things I've learned, MU is challenging (a pain) even for skilled DW users, MU has low level DW functionality, and that I have to carefully screen DW user skills before hiring them. I really appreciate all of the responses as it has been helpful and insightful.

So if any Adobe Customer Experience Specialists are monitoring these boards, what say you about this conflict between MU and DW while playing in the same sandbox?

So far the only adequate workaround that I have in place is to design Muse pages that link to more complex pages (i.e. forms connected to PHP). When you export to HTML from your Muse project it will build an "assets" folder and populate it with whatever HTML files you have linked to. You have to copy external CSS and other resources (images) associated with your linked HTML file to the asset folder yourself, but that is a minor inconvenience considering the speed that Muse allows in building your 'front end'.