I also checked your projectseven site, which, as far as I can tell, is built in your in-house Harmony tool. I see custom data- html attributes everywhere, and inline styles riddling the page code. And a number of presentational ill-named classes. Data attributes are a large part of how the interface is able to do what other interfaces cannot, that is to recall the structure in its entirety and write it back to the UI with the proper options selected so that the user can edit the layout. There are no inline styles ever written in a Harmony structure. If you are seeing any, it is likely you are not understanding their nature, which is likely from another, scripted widget, which is writing to the DOM, and that would therefore not be the markup users would edit. As for ill-named classes, that is a matter of opinion - and dependent on whether you are speaking of a Harmony-generated class name or something we added. While all of our pages employ Harmony to some extent, most of our pages were created manually, years ago, in such a way that made themselves easy to evolve as web standards did - not an easy feat. So, it's hard to say exactly what you are talking about - it seems you re making some assumptions. Tell you what, here is a layout made from scratch with Harmony. Tell me exactly what class names you do not like and perhaps I can explain why we like them, or perhaps we can put your suggestions to good use in a future update. PVII Document Do let me know. We are always eager to learn and improve. EDIT I think I know what you are referring to now. You must have looked at the generated code in a browser's developer tools window. The inline styles are added to the DOM at runtime by a script. Essentially, the values in the data attribute, which relate to UI options, are translated into inline styles. Nothing at all wrong with that. But the important thing is that the Dreamweaver user will never see that in Code View, nor will he need to worry about it. And the script is not just for translating options, it is also used to feed ancient browsers a floated layout. The only "odd" class name I can think of, would be hmy-noscript. And that is a very interesting case as it allows us, as well as users to write styles to "tame" Dreamweaver's Design View. The noscript class is removed at runtime so you'll need to dig a little deeper in Developer Tools to see that 🙂 All in all I really kind of prefer our approach and class names to Bootstrap's…by a very, very wide margin.
... View more