Course Structure

At the risk of sounding like a broken record, let me repeat myself.

But underlying all the chaos is a simple structure and a clear set of rules. If you have a good grasp of this, you will be able to see through the inherent complexities of migration.

The goal of this course is just to give you a mental model of the underlying structure and rules of migration, a mental model which you can use to think about your own migration process for your own application.

A person without a plan is a person planning to fail.

In this section, I will teach you my strategy, the strategy that I advocate when migrating an AngularJS application. It is generic, applicable to any of your AngularJS migration projects and one that I have used with great success.

Of course, there is no steadfast rule that says you have to follow my plan, but it is what I recommend you follow and it will be the method that I will teach in this course.

The meat of this course is going to be a real case study. We are going to take a real-world application, break it down and migrate it from AngularJS to Angular using our plan. In fact, if you have followed my other courses you might already be familiar with this. It is the very same contacts application that we built-in my old AngularJS course.

Based on my experience delivering AngularJS to Angular migration workshops, one thing I can guarantee you is that there will be problems. Fear not, the troubleshooting section will discuss some of the more common issues that seem to always pop up during a migration project. Hopefully, some of it might be useful for you as well.

The strategy that I will discuss here is not mandated by the Angular team but it is something that I have presented and talked about at many conferences, including the Angular connect conference in London. It is a catch-all, bulletproof migration strategy that could work for you.

If everything fails and you are looking at a complete rewrite of your AngularJS application, this might just be what you are looking for.