I've been working on a screencast series that should get you up to speed on AngularJS pretty quickly; I've got 3 parts so far:

* Part 1: Intro to Angular JS (50 minutes) [1]

* Part 2: End to End with Angular JS (52 minutes) [2]

* Part 3: Security with Angular JS (30 minutes) [3]

[1] - http://www.youtube.com/watch?v=8ILQOFAgaXE

[2] - http://www.youtube.com/watch?v=hqAyiqUs93c

[3] - http://www.youtube.com/watch?v=18ifoT-Id54

Great tutorial, I finally understand how Angular fits together.

I've been meaning to look further into AngularJS, and it looks like this is the weekend to do it.

End-to-end sounds interesting! Thanks for creating this. I'll watch these tonight!

I've been playing with Angular for a lil bit. The things that frustrate me as a learner are:

1) Lack of good end-to-end examples.

2) Situations where things just don't work, and give no feedback as to what went wrong. Am I just using Angular JS incorrectly or does this happen to everyone?

While learning Angular, it pays to really understand how the $scope works, when $watch'es are fired, and when you need to explicitly call an $apply, etc. What are some examples where things just don't work? While I was learning angular, a lot of times I had assumed things were available in scope when they were not. Some built-in directives like ng-repeat will create local copies of scope so I would try to change a variable directly expecting the parent to pick it up but it won't. Now my issues are simply misuse of the APIs. Eventually you will "get" the way angular works and instinctively know how to write with it.

Thx for the kind words of encouragement. There is something elegant about angular and I'm going to keep slogging on. I think you're spot on about mechanisms .. I don't grok how angular does its magic and I think that is a big problem for me. Any suggestion on how one goes about learning Angular internals sans looking at the source code?

I used Angular for two hackathons so far and didn't keep track of what didn't work. It was just a matter of ... let me try something a different way ... and poof ... it worked. Not very scientific I'm afraid.

Install Batarang for debugging scope issues. Don't be afraid of looking at the source, it's a great way to learn. Write some directives and then look at the ones provided by angular - and realise they're not cryptic.

Re showing when things don't work. That's the best part of the egghead videos; showing things broken.

I forget sometimes how much you learn from doing it wrong before doing it right.

The end to end video covers building a single page app with angular backed by mysql and laravel 4. It should give you some practical examples to work from, and all the source code for all videos is included on github too.

I would watch them if they focused on a single topic and were from 5 - 10 mins

You would probably like John Lindquists screencasts at http://www.egghead.io then; I took a more comprehensive approach to try and show how all the pieces of angular fit together.

These are the best videos in the list, hands down.

Thanks a lot for sharing this! Is there a way I can subscribe to updates about new episodes?

I'll add those later today. Thanks!

I submitted a PR on github with those and one more link on Authentication with Angular :)

Great tutorial, thorough.

Please, please, please don't forget about the Angular UI and their ui-router!!

The first project I was working on had several complex nested views and this little piece of software made my life sooooo much easier. I wasted so much time trying to find a resource about how to handle nested views. Hopefully this will save someone else some time in the future.

Angular UI Router: https://github.com/angular-ui/ui-router

+! for router, couldn't live without it. We use it here: http://brandid.github.io/parse-angular-demo/

Odd the book isn't on the list, perhaps because it's not quite finished: http://www.packtpub.com/angularjs-web-application-developmen...

I thought I did link to that book. I'll check again after lunch. I am reading that book now and it is excellent so far.

Edit: The link to that book is there :)

Jeff, thanks! I was in analysis paralysis over how to handle some new functionality & this pushed me over the edge toward trying angularJS. So far, so good...

BTW, I bought the two cheapest ebooks in your list. Hope you got a piece! The 'Recipes' one has been the most handy so far.

Matt...glad you found it helpful. I haven't purchased the Recipes book yet, but I might after seeing your feedback.

I've purchased the AngularJS Oreilly book (good, not great...it just didn't feel like a well-organized book to me) and the Packt book (Web Application Development with AngularJS)..the Packt book is excellent. At least for the first 5 chapters I've read. Oh, and I have no "referral" params for any of those books.

I'm personally really excited about getting to work with Angular. It has been a lot of fun so far, and its amazing how much you can do with a small amount of code.

So I was finally freeing up sometime to learn some frontend dev. Was going to focus on bootstrap. But would angular be better?

I'm trying to build up a toolset to rapidly build admin sections for services I work on which don't typically have users in the traditional sense.

I don't think the two are at all mutually exclusive--in fact, they play very nicely together (see [1]). Bootstrap is mainly a library to help with layout stuff, while AngularJS provides a way to structure the logic and bind it to the DOM. They're completely different libraries, so learn whichever is more applicable to what you're doing (or better yet, learn both).

[1]: http://angular-ui.github.io/bootstrap

They serve different purposes: Bootstrap is (mostly) a CSS framework for quickly laying out pages etc, while AngularJS is a Javascript framework for developing front-end application logic. They can be used together pretty effectively for rapid development.

Oops. I meant to say Backbone not Bootstrap!! It was Backbone on my todo list, but Angular seems to be getting all the attention now.

Bootstrap= css + some javascript widgets

Angularjs = a very opinionated MVVM framework for web client applications ( think gmail , google reader , ... )

Very good resource!

I wrote a couple of AngularJS posts myself, hopefully you think they are worth adding: http://www.grobmeier.de/all-posts-from-this-blog

I'll check them out later today. Thanks!

This is a really helpful and comprehensive list. Thank you! I've used knockout (and knockback) in the past to refactor a realtime backbone app, but I'm definitely going to give angular's tyres a kick for my next app.

A few more that might not be on that list: http://pineapple.io/resources/tagged/angular-js

Thanks..I'll browse through that list this weekend to see if I need to add any of those.

Does anyone have any great resources they can recommend regarding SEO and Angular? I have read a lot of conflicting things so far.

"AngularJS For .Net Developers"

I don't get that. Is HTML different in Microsoft world?

For some definition of "different". See http://msdn.microsoft.com/en-us/library/ms537512%28VS.85%29.... for example.

Conditional comments have nothing to do with .NET devleopment.

In the same way that you would expect "AngularJS for Node Developers" to include information on running your app using a Node.js backend, this has information on using a .NET backend.

Who cares what the backed is, as long as you are getting data using xhr, angular js and HTML is same.

Presumably someone who works with a particular framework, whether that's Django, Ruby on Rails, or ASP.NET MVC, would like to know how to properly use AngularJS with those frameworks without throwing out the benefits those frameworks provide. I'm assuming you have enough web development experience to understand that not every backend is just a dumb REST endpoint.

if you think devs working on these framework don't understand client side javascript/HTML framework on its own and need to be explained for their particular framework, may be they outta be not writing code at all.

Also, another thing that bothers me about MS is that they hide so much real HTML/javascript from devs with visual basic like facade called webforms that MS devs don't get into a new platform unless they see a document like "Angular js for .net" title.

Webforms hasn't been Microsoft's first-class web development platform for a while. We are a .NET shop and most teams excusively use MVC for all our new web development, which exposes HTML/JS at a very unobstructed level.

Microsoft is moving even further in that direction with Web API, which does largely transform ASP.NET into a "dumb" REST endpoint completely separate from the HTML/JS clientside.

Good to know

AngularJS, the one island of stability in a NSA world!