Where does EDS content actually come from – AEM instance or edge network?

[mancillaign]

A conceptual question I’d like to clarify about Edge Delivery Services:

When EDS delivers a page, is there any AEM instance directly serving that content, or is it always the edge network?

I ask because I’m trying to understand if it’s possible to have a hybrid approach, mixing AEM page properties with EDS delivery.

For example:

• In classic AEM Sites, you could override /libs/core/wcm/components/page/v1/page to add page-level properties (title, metadata, etc.).

• With EDS, there’s also /libs/core/franklin/components/page/v1/page.

The question is:

• Can we actually override or extend these properties so they appear in the live EDS site?

• Or are these purely for preview inside AEM Author, and not part of what the EDS runtime ever serves?

Would love to hear from anyone who has tried customizing page-level data or mixing JCR properties with EDS delivery.

[arunpatidar]

Hi @mancillaign 

The Authored content stored in AEM but when you publish then instead of going to AEM publish, content markdown files are generated and push to content bus(AWS S3 bucket)
You can add page properties which will be added to meta tag

[Saravanan_Dharmaraj]

@mancillaign Hope you looked at this  https://www.aem.live/docs/bulk-metadata !

[Shiv_Prakash_Patel · Accepted solution]

Hi @mancillaign ,

• With Universal Editor, authored content is created and stored inside the AEM repository (JCR).
• With document-based authoring, content source files (such as Markdown or spreadsheets) are stored externally in platforms like Google Drive, OneDrive, or SharePoint.
• After publishing, regardless of the authoring method, content is processed, built into static files, and pushed to the content bus (often AWS S3). The live EDS site is always served from the edge network/CDN using these static files.
• The live site never serves content dynamically from AEM or the external drive—everything visible to end users is from the pre-built, static files.
• To update or control page properties/metadata, you must set them in your source documents (drive files for document-based, or within AEM for Universal Editor). Runtime overrides from the AEM JCR are not possible for live EDS delivery.

[Shashi_Mulugu]

@mancillaign content and its semantic html comes from AEM author instance.

While we can technically customize aem franklin components , Adobe is discouraging the idea to avoid unnecessary complications in future while using other integrated features such as Universal Editor,  AEM Sites Optimizer 

https://adapt.to/2024/presentations/adaptto-2024-lightning-talk-not-implementing-custom-aem-componen...