Building a dynamic SPA website with Angular
summary
A concrete recipe for CMS-driven SPAs using Angular: use a single catch-all route that resolves JSON page templates, then create runtime components via ComponentFactoryResolver instead of large ngIf templates; mark dynamic pieces in NgModule as entryComponents so AOT keeps them. Shows server rendering with Angular Universal and the Universal cache pattern to serialize state, reports final bundles under ~200KB with AOT, links to a GitHub repo with live code and examples.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:30Dynamic content challenges
- 3:24Architecture experiments
- 7:07Dynamic routing strategies
- 11:31Component rendering
- 14:44Dynamic component factories
- 18:50Optimization and AOT
- 21:00Server-side rendering
