Congratulations! You've finished a small, introductory book on Angular. This book was short on purpose. My intention when writing it was to apply the Pareto principle to Angular, with the idea being that roughly 80% of Angular's benefits can be reached through something like 20% of the complexity-weighted area of its API. Another way to express this approach would have been with a title like AngularJS: The Good Parts. On that note, I think it fitting to send you on the rest of your Angular journey with the following excerpt from Douglas Crockford's classic JavaScript: The Good Parts:

Every feature adds pages to the manual, increasing training costs. Features that offer value to a minority of users impose a cost on all users. So, in designing products and programming languages, we want to get the core features—the good parts—right because that is where we create most of the value.

Angular currently has a lot of features. I hope that this book gets you on the right footing with Angular, making it possible to make the most of Angular's phenomenal value offering without getting lost in the weeds. Remember always that the most important thing in web development is actually developing. Learning about Angular or any other tool is only a means to an end. That end is to build the things that make the web a better place. Go now, get behind the steering wheel and pedals of Angular, and drive.

Where to go next

Of course, every real-world Angular project must navigate concerns that are beyond the scope of an introductory text. Thus, I hope the following list of topics and resources may provide some direction.

It goes without saying that this list is incomplete. Feel free to contact me with any suggestions.

I hope you have been enjoying Angular Basics.
You can join the mailing list to hear about updates to the book.
Please also let me know what you liked and what I can improve.
And please share the word using the social buttons below!