ng new {app-name} i. Sections of NgModule 1. imports -> different from TS/JS imports 2. declarations 3. providers 2. Create top level pages: 1. ng g component … 3. Create page routes -> {talk about child routes} 1. import Router module and call forRoot method 2. define paths without leading/trailing slash 3. empty path is default 4. you can redirect within path definition, pathMatch is necessary 5. multiple route params 6. The order of the routes in the configuration matters and this is by design. The router uses a first- match wins strategy when matching routes, so more specific routes should be placed above less specific routes 7. for routerLink “route” would resolve to a child route and “/route” resolves to base 8. routerLinkActive lets you supply css class to style with 9. child routes won’t work unless <router-outlet> is configured in the host template