- Implementing Applications for AEM as a Cloud Service
- Using Cloud Manager
- Managing Environments
- Configuring your CI/CD Pipeline
- Deploying your Code
- Understanding your Test Results
- Accessing and Managing Logs
- Understanding Notifications
- Managing SSL Certificates
- Managing Custom Domain Names
- Introduction
- Getting a Custom Domain Name
- Adding a Custom Domain Name
- Adding a TXT Record
- Checking Custom Domain Name Status
- Configuring DNS Settings
- Checking DNS Record Status
- Viewing & Updating & Replacing a Custom Domain Name
- Updating a Custom Domain Name’s SSL Certificate
- Deleting a Custom Domain Name
- Managing IP Allow Lists
- Cloud Manager FAQs
- Managing your Code
- Developing for AEM as a Cloud Service
- AEM Project Structure
- AEM Project Repository Structure Package
- AEM as a Cloud Service SDK
- AEM as a Cloud Service Development Guidelines
- Logging
- Configurations and the Configuration Browser
- AEM Technical Foundations
- API Reference Materials
- Generating Access Tokens for Server Side APIs
- Headful and Headless in AEM
- Full Stack AEM Development
- Getting Started Developing AEM Sites - WKND Tutorial
- Structure of the AEM UI
- Sling Cheatsheet
- Using Sling Adapters
- Using the Sling Resource Merger in AEM as a Cloud Service
- Overlays in AEM as a Cloud Service
- Using Client-Side Libraries
- Page Diff
- Editor Limitations
- Naming Conventions
- Components and Templates
- AEM Tagging Framework
- Building Tagging into AEM Applications
- Search
- Custom Error Pages
- AEM Node Types
- Headless Experience Management
- Headless and AEM
- Headless Developer Journey
- Getting Started Guides
- Content Fragments
- Headless Delivery with Content Fragments and GraphQL
- Working with Content Fragments
- Enable Content Fragment Functionality for your Instance
- Content Fragment Models
- Managing Content Fragments
- Variations - Authoring Fragment Content
- Markdown
- Using Associated Content
- Metadata - Fragment Properties
- Structure Tree
- Preview - JSON Representation
- Delivery API
- Hybrid and SPA AEM Development
- Hybrid and SPA with AEM
- Enabling JSON Export for a Component
- SPA Introduction and Walkthrough
- SPA WKND Tutorial
- Getting Started using React
- Getting Started using Angular
- SPA Deep Dives
- Developing SPAs for AEM
- SPA Editor Overview
- SPA Blueprint
- SPA Page Component
- Dynamic Model to Component Mapping
- Model Routing
- The RemotePage Component
- Editing an External SPA within AEM
- Composite Components in SPAs
- Server Side Rendering
- Enabling JSON Export for a Component
- Launch Integration
- SPA Reference Documents
- Developer Tools
- Personalization
- Configuring and Extending AEM as a Cloud Service
- Deploying to AEM as a Cloud Service
- Author Tier
- Content Delivery Overview
Headless Development for AEM Sites as a Cloud Service
Learn how AEM as a Cloud Service’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.
Overview
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.
Comparing Headful and Headless
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 as a Cloud Service and Headless
AEM as a Cloud Service is a flexible tool for the headless implementation model by offering three powerful services:
- Content Models
- Content Models are structured representation of content.
- These are defined by information architects in the AEM Content Fragment Model editor.
- Content Models serve as a basis for Content Fragments.
- Content Fragments
- Content Fragments are instantiations of content models.
- These are created by content authors using the AEM Content Fragment editor.
- They are stored in AEM Assets and managed in Assets Admin UI.
- Content API for delivery
- The AEM GraphQL API supports Content Fragment delivery.
- The AEM Assets REST API supports Content Fragment CRUD operations.
- Direct content delivery is also possible with the Content Fragment Core Component’s JSON export.
Your First Steps with AEM Headless
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.
| Resource | Description | Type | Audience | Est. Time |
|---|---|---|---|---|
| Headless Developer Journey | For a comprehensive overview of AEM’s headless features from the theory of headless through going live with your first headless project, start here. | Guide | Developers | 1 hour |
| Headless Getting Started Guide | For a short summary of the key AEM headless features, check out this quick start overview. | Quick Start | Developers, Administrators | 20 minutes |
| Getting Started with AEM Headless hands-on tutorial | If you prefer a hands-on approach, this tutorial dives directly into creating a simple headless project. | Tutorial | Developers | 2 hours |
Resources on adobe.com
Resources
Adobe Account
