Prepping for Tomorrow - Creating a Flexible AEM Architecture

Presentation Overview

In this presentation, I explore the importance of architecture in AEM implementations and how to create flexible, scalable architectures that support business growth. I discuss common myths about architecture and why taking time to plan upfront can save significant time and resources later.

Key Topics

Why Architecture Matters: Failing to plan is planning to fail
Myths of Architecture: Common misconceptions about architectural planning
Architecture Goals: Reliability, agility, cost reduction, technical debt retirement, operational excellence, and innovation
Implementation Strategies: Discipline, consistency, creative constraint, repetition, and governance
AEM in the Enterprise: How AEM fits into enterprise architecture
AEM as a Content Service: Positioning AEM at the center, not the corner
AEM as a Hybrid CMS: Content service layer capabilities
Application Types: Choosing the right application strategy
PWA Benefits: How Progressive Web Apps provide the broadest deployment footprint
Component Architecture: How components fit into our architecture
Atomic Design Systems: Framework for component design
UI Frameworks: Comparing Angular, React, and Vue
Component Systems: Web Components, React, and Adobe Granite UI
Component Explorers: Tools for testing and documenting components

Key Insights

Architecture doesn't need to be complicated; it should be just enough but no more
Progressive Web Apps (PWAs) offer the broadest possible deployment footprint, hitting 13 different targets
Companies using PWAs have seen significant improvements:
- Best Western River North: 300% increase in revenue
- Trivago: 150% increase in engagement
- Starbucks: Doubled online orders with a PWA 99.84% smaller than their previous app
Atomic design systems provide a framework for creating reusable components
Component explorers like Storybook help market, document, and test components

Presentation Materials

View Slides on SlideShare