Dissecting the architectural process for creating reusable Angular components
summary
Argues that spending 30 minutes upfront to analyze a design yields a single Angular component that replaces multiple ad hoc modals; demonstrates consolidating four modal variants (popover, persistent modal, small modal, input-taking modal) into one reusable modal covering four variants that handles open/close, sizes and input. References Angular ecosystem libraries like Material and Kendo UI and an open-source component library used as a template. Results are lean, maintainable and reduce duplicated CSS and bugs.
AI-written summary · about
chapters (5)
- 0:00Reusable Angular components
- 1:08Architectural thinking in coding
- 4:24Analyzing and consolidating components
- 12:48Career impact of architectural thinking
- 15:40Closing remarks
related talks
49mComponent-Based Modular Development
28mFrom Scratch to Screen: The Art of Component Design in Angular
19mCreating Beautiful Experiences Fast with Angular Material
29mBuilding an Angular component Library
31mAngular Material or Bootstrap? Stop asking the question!
20mEngineering Scalable Angular Components
49mBuilding Better Components - A Journey to a More Resilient Frontend
51mBuilding Better Components — A Journey to a More Resilient Frontend