Feature Lifecycle
Simplicity and productivity guide everything we do. To stay lean and fast, we’ve redefined our approach—focusing only on features that customers actively use.
What does this look like?
Edge Delivery Services follows a feature lifecycle, not a traditional roadmap. When our existing features don’t meet a business need, we collaborate with customers to develop a solution. If it gains traction across multiple customers, we productize it and monitor usage. When a feature is no longer actively used, we replace it with a better solution.
Feature Lifecycle Components:
- Map of Interest – A collection of business needs that cannot yet be met with our existing features.
- Adobe-led Implementation – Solutions developed in collaboration with customers to address a Map of Interest need.
- Product Feature – A fully productized feature, proven in real-world usage, and available as part of the product offering.
- Deprecation – Features no longer in use across our customer base are removed in favor of better alternatives.
This approach ensures Edge Delivery Services remains agile, customer-driven, and optimized for real-world needs.
https://www.aem.live/docs/featurelifecycle.svg
Map of Interest
Through active collaboration and discussion with customers, our Map of Interest is populated. It represents a list of needs that are under consideration for solution development in partnership with a customer team.
- “Bring your own Git” support for Bitbucket, Gitlab, GitHub Enterprise
- Reviews and snapshots
- "Bring your own Git" support for Azure DevOps
- Server-side logic to render pages: Using AEM’s runtime as app server
- Dynamic pages: SSI or any dynamic includes technique
- User management: Using AEM as IdP
- Authentication: Using AEM for secure content
- Content permissions: AEM as secure extranet
AEM authoring items of interest
When using AEM authoring as your content source for your Edge Delivery Services project, most Sites features are available. For example, nearly any action available in the Sites console is applicable to Edge Delivery Services.
However, some features of the Sites console which either are not yet available for Edge Delivery Services with AEM authoring as a content source or are only partially available. For this reason, such features may be presented differently than their Sites counterparts or there may be alternative solutions for the use case. If your project requires one of the following features, please review the alternatives suggested below and reach out to Adobe to work together to understand your use case.
Available
Partially available
Early-access technology
Recently added features now available for customer use. These are features that still may undergo significant changes, require higher-than-usual levels of support, or are not widely adopted yet.
Experimentation is the practice of making your site more effective by changing content or functionality, comparing the results with the prior version, and picking the improvements that have measurable effects.
Adobe Experience Manager Assets Sidekick Plugin
With the Experience Manager Assets Sidekick plugin, you can use assets from your Experience Manager Assets repository while authoring documents in Microsoft Word or Google Docs.
Configuring Adobe Target Integration
This article will walk you through the steps of setting up an integration with Adobe Target so you can personalize your pages via the Adobe Target Visual Experience Composer (VEC).
Getting Started – DA Developer Tutorial
Document Authoring (DA) is an alternative to SharePoint or Google Drive that provides a document-based authoring interface focused on the AEM Document model (Blocks, Sections, etc.). It provides an SDK, APIs, and built-in Adobe technologies.
Configuring Adobe Experience Cloud Integration
This article will walk you through the steps of setting up an integration with the Adobe Marketing Technology stack. The stack combines Adobe Experience Platform WebSDK, Adobe Analytics, Adobe Target or Adobe Journey Optimizer, Adobe Client Data Layer and Adobe Experience Platform Tags.
Web Components are a collection of web standards that allow the creation and use of reusable, modular functionality in web sites and web apps.
A new feature to support the concept of publishing a set of content (dozens or hundreds of pages) usually for a launch of an initiative or event.
Deprecations
Features that have been removed from the product based on lack of usage. See Deprecation and end-of-service for features slated for removal
Questions or Ideas?
Please contact the community via Discord.