Fix: Enable editing of Title field via route field #118
+16
−17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d for improved title handling and ensure proper editing in Experience Editor
…lize pageTitle field for improved title handling and editing capabilities in Experience Editor
sc-chathumikaalwis
approved these changes
Sep 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Ensure the Title field rendering uses the route's Title field so that it includes the correct Experience Editor metadata (
chrometype="field") and is editable.Why
Previously, the Title component rendered the field from
contextItem, which did not provide the required metadata. As a result, the Title was not editable in the Experience Editor. Starter templates worked, but new components added to the page were not editable.How
Title.tsxto usepage.layout.sitecore.route?.fields?.pageTitleinstead ofcontextItem.<Text />component now renders with EE metadata.