Justin,
I understand your reasoning, but don't forget that Siteassist has a much more dangerous Achilles heal if it comes to breaking designs: Page types!
It is much more likely that a user changes by mistake a page type and looses all his contents of a page than changing the DIV ID's "topnavigation; content; footer". I cannot really think of a reason that would make me change those ID's and I would describe myself as a CSS literate.
What I am proposing is actually to change the whole concept how you integrate sculptor and menuwriter in siteassist. At the moment they work like addons, while IMO they should be plugins and one should not have to leave siteassist in order to change sculptor or menu design parameters.
Basically for users who have all 3 programs installed siteassist should include the option to change the associated sculptor or menu design on the fly. Essentially sculptor would read, when started from within siteassist, the design file from the directory:
..\Adobe\Dreamweaver 9\Configuration\Shared\WebAssist\SiteAssistPro\sculptor\
instead of reading it from :
...\Adobe\Dreamweaver 9\Configuration\Shared\WebAssist\CSSSculptor\
That way you separate a siteassist/sculptor design from standalone sculptor designs and you could even assign parameters that would protect certain ID's like topnavigation etc. from being changed.
There should be also an option to be able to change CSS manually in the site related css fles and have the settings remain sticky.
Another thing that is missing is a seperate "mystiles.css" for the homepage. You could for example include and import by default a "myhomestyles.css" into the index.html of the site.
Last but not least, a feature dearly needed would be the option to create multy-language sites with cloned menu structures in language defining subfolders and common image, spry, java etc. deposits in the top level folder. Right now I cannot think of any way to create a multiple language site with site assist.
Regards
Berthold
