Building a dynamic SPA website with Angular
summary
Concrete solution for using a CMS to drive an Angular single page app while keeping AOT compilation and server rendering: fetch per-URL JSON routes in a resolver, map template names to real components via a component factory resolver, create components dynamically and register them in entryComponents, use a state transfer service to serialize server-rendered data to the client, and add a link-intercept host listener for CMS rich text. Result: working repo, initial paint drops ~0.5s → ~0.25s and bundle from ~4MB → ~200KB.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:06Bootstrapping multiple applications
- 4:08Initial data
- 6:07Single Page Application
- 8:50Two issues with that approach
- 10:29Get the data in a resolve
- 13:30The problem cascades
- 13:46Then came rc4
- 14:05The theory
- 23:23The idea
