How Are Teams Structuring Content Fragment Models for AI-Driven Experiences in AEM Cloud?

Curious how enterprise AEM Cloud teams are evolving Content Fragment modeling strategies as AI-driven personalization and multi-channel delivery become more common.

Historically, many content models were designed primarily around page rendering and headless delivery needs. But with increasing AI-assisted content generation and dynamic experience orchestration, the modeling requirements seem to be changing rapidly.

Interested in perspectives around:

• reusable fragment design
• metadata strategy
• AI-friendly taxonomy structures
• personalization scalability
• GraphQL performance considerations
• and governance for large content ecosystems

Would love to hear how teams are preparing their content architecture for more AI-driven experience delivery models.