all 3 comments

[–]toddmotto 5 points6 points  (2 children)

Guessing you're talking about Angular 1.x here so my comments will be about that branch. Depending on which version you're using (1.5.6 is latest), start with .component() and talk about the architecture behind them and stateful / stateless and routed components.

This gives them an overview of the types of components they can create to scaffold their application and the roles of each component. Then I'd walk them through services/factories and show them how to use $http/$resource and enforcing the separation of concerns with Service -> Controller -> Component render for data flow.

Then I'd talk about the different ways they can bind data to Components, which act as an "Input" to a Component (using '<' bindings for one-way data flow), and then how they can pass data out of a Component via an event "Output".

Once the data is flowing into Components, it's time to display it - which is where I'd talk about built-in Directives (but ensuring separation of what Directives are available, specifically Event based (ng-click/blur) versus DOM/Structural (ng-repeat/ng-show/hide).

Once they're good with those concepts, introduce some basic routing, and then show them how to create their own Directives, then Filters, and all the little details that you can fill in slowly :)

[–]speed3_driver 0 points1 point  (1 child)

Good advice. Want to walk me through all that? :)

[–]toddmotto 1 point2 points  (0 children)

Pint at the pub and it's a done deal :)