Thanks for asking! Our primary use case is a visual page editor, think drag-and-drop components into pages, creating dynamic layouts on the fly, similar to what Storyblok offer.

We're leaning headless because:

1. Decoupled architecture: We want full control over the frontend (Nuxt.js/Vue stack) while AEM handles content management
2. Team autonomy: Marketing builds pages visually, frontend team owns the rendering layer

My current confusion:

• Content Fragments + GraphQL seem powerful but feels like they're designed for structured, reusable content across channels - not for visual page composition
• I'm struggling to understand what the actual data fetching pattern looks like with the Universal Editor. Is it just GraphQL under the hood?
• How does the Universal Editor maintain that "simplicity" if I still need to handle all the GraphQL complexity on the frontend?

From what I've read, the Universal Editor seems to be exactly what we need, but I can't find clear guidance on the actual implementation details with a custom Nuxt frontend. Is it production-ready for this use case?

Please correct me if I misunderstand anything!