Learn how AEM 6.5’s powerful headless capabilities like Content Models, Content Fragments, and the GraphQL API work together to enable you to manage your experiences centrally and serve them across channels.
Headless implementation is increasingly becoming important for delivering experiences to your audience is, wherever they are and regardless of channel.
Headless implementation forgoes page and component management as is traditional in full stack and hybrid solutions and focuses on the creation of channel-neutral, reusable fragments of content and their cross-channel delivery. It is a modern and dynamic development pattern for implementing web experiences.
This document focuses on the full headless implementation model of AEM. However headful versus headless need not be a binary choice in AEM. Headless features can be used to manage and deliver your content to a variety of endpoints while also enabling your content authors to edit single page applications. All in AEM.
See the document Headful and Headless in AEM for more information.
AEM 6.5 is a flexible tool for the headless implementation model by offering three powerful services:
There are a number of resources available for your to get started with AEM’s headless features. They are intended for different use cases, but all give a solid overview of AEM’s headless features.
|Headless Developer Journey||For users new to AEM and headless technologies, start here for a comprehensive introduction to AEM and its headless features from the theory of headless through going live with your first headless project.||Guide||Developers new to AEM and headless||1 hour|
|Headless Getting Started Guide||For experienced AEM users who need a short summary of the key AEM headless features, check out this quick start overview.||Quick Start||Developers, Administrators with AEM experience||20 minutes|
|Getting Started with AEM Headless hands-on tutorial||If you prefer a hands-on approach and are familiar with AEM, this tutorial dives directly into creating a simple headless project.||Tutorial||Developers||2 hours|