Angular ❤️ CMS
summary
Shows a working pattern to run Angular apps from any CMS: CMS serves a JSON page model fetched by a resolver on a single wildcard route, code uses componentFactoryResolver with a static ref list and entryComponents to instantiate page templates, overrides the router reuse strategy (return false) to enable real page-transition animations, adds a link-intercept directive to handle innerHTML links, and uses Angular Universal plus the state-transfer cache and a no-SSR directive for selective server rendering. The solution is implemented, small AOT bundles and SSR caching both work.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 1:09Angular in dynamic CMS environments
- 6:51Angular Elements for flexible components
- 8:16Single-page app with page transitions
- 13:16Dynamic routing with CMS data
- 15:53Component factory resolver solution
- 18:46Custom router reuse strategy
- 20:09Handling rich text in Angular
- 23:43Server-side rendering with Angular Universal
- 27:16Caching strategies for SSR
- 30:10Conclusion and Q&A
related talks
31mAngular + CMS = ❤️
26mBuilding a dynamic SPA website with Angular
32mBuilding a dynamic SPA website with Angular
28mReal-life Angular Architecture Lessons
31mAngular Universal in the Real World
26mServer Side Rendering with Angular Universal
13mModern Angular deployment with Google Cloud
20mSven van Straalen