OK, I am getting awestruck by the power, beauty, simplicity of angularjs as I am reading.
I am like 0.1% into the docs, and I find myself thinking these questions.
1) Does using angular js mean that designers, who are only responsible for marking up a good looking HTML, should be aware of angular and the entire design pattern surrounding it?
2) Since the entire markup architecture is supposed to come from a good understanding and pre-decided angular-ness, can a designer, in real world web applications successfully design a brand-new/existing page, without having to get into the big-paradigm-shift that angular entails?
3) Has somebody had the experience of working with a designer, who does not know about angular and the associated awesome-ness, but still manage to deliver above-excellent web pages?
4) If the answer to 3 is yes, how much work does fall on to the client-side/full-stack/whatever developer to make the rendered pure HTML ng-ish ?
5) All of this coming from the fact that life has been pretty simple with jquery till date.
I am all pro for adapting to ng but I want to listen to people who have been on similar path, which admittedly, is rebellious to the conventional style of designer-developer independence.
My experience so far is that Angular makes it easier for designers. They can still create static mock ups, but they can also easily add interactivity with directives like ng-click, ng-hide etc without having to write a single line of Javascript. You'd obviously still want to go over that template and move some logic to the controller later, but your designer can prototype behaviour without having to understand the DOM, jQuery, live events, etc.
Another great thing is that since your HTML is now declarative, your designer can see by reading the code which element has logic attached. In the olden days of pure jQuery, the designer would move some elements around and silently kill your code since your CSS selectors no longer match any elements.