SitecoreExperience Edgeis a headless content delivery service that exposes content via GraphQL. For a newly created data template to be available inExperience Edge, it must be explicitly included in theGraphQL content schemaconfiguration. This is done by modifying the Sitecore configuration using apatch fileto include the parent path of the template.
Locate the Parent Path of the Template
Modify the Experience Edge Configuration Using a Patch File
Create a configuration patch file (e.g.,include.ExperienceEdge.config) toadd the template’s parent pathunder thecontentsection.
Example patch file:
Steps to Ensure the Template is Available in Experience Edge:
Publish the Configuration Changes and Content
Ensure thetemplate and itemsare published.
The updated schema should be reflected in theGraphQL endpointof Experience Edge.
Why are the Other Options Incorrect?❌A. Create the template in the configured locations for Experience Edge (Feature, Foundation, Project, User Defined).
While placing templates in the correctHelix architecture layers(Feature, Foundation, Project) is a best practice, it does not automatically make them available in Experience Edge.
❌C. Use the Experience Edge Admin API to add the template to the schema.
TheAdmin API does not control content schema inclusion. Experience Edge follows Sitecore publishing rules, and templates must be included via theconfiguration patch file.
❌D. Create the template anywhere in the /sitecore/templates folder.
Simplycreating a template does not make it available in Experience Edge. It must be explicitly added to theExperience Edge content schema configuration.
Sitecore Experience Edge Configuration– Configuring Content in Experience Edge
Sitecore GraphQL Content Schema Setup– GraphQL Content Schema
Using Sitecore Patch Files– Sitecore Configuration Patching
References for Further Learning:
