Muse is not intended to be a code generation hand-off tool for downstream editing. We recommend you do all of your site editing in Muse, rather than exporting the site from Muse and editing the code elsewhere. By staying within Muse, you can continue to use the full functionality of Muse to update your site. As soon as you move to altering the output of Muse, there's no going back (unless you're willing to re-make your changes each time you export from Muse). The HTML code output from Muse is not optimized for manual editing.

The biggest issue i have with Muse at the moment is not being able to edit the HTML inside muse. For example, I have a CMS manger site i use to give CMS to clients. to add this to a site I need to be able to add a class object to each section that will be editable.

Not a problem until i decide i need to do something simple like swap button positions. Then when i export i loose it all and have to type it all in again.

If not an in built HTML editor, then the ability for muse to include and add back any changes to the HTML you make so it is not lost.

Dreamweaver is able to do this and post the edited website back up BUT Muse will detect that the website has changed and have a spaz attack because you didn't use Muse to make that change... even thou you used another Adobe product. This is a major problem with Muse and will limit it's use until Adobe fixes it but the program is still very new and aimed at people learning their way.