docs: clarify CMS binding in MCP custom code - #492
Merged
Conversation
Agents were reusing <ycode-inline-variable> in custom code head,
which is not interpolated and breaks per-item JSON-LD. Document
{{FieldName}} for custom code vs inline variables for SEO.
tristan-mouchet
requested review from
liamwalder,
lunenas and
ysamcode
as code owners
August 11, 2026 09:38
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
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.
Summary
Document the correct way to bind CMS fields in page custom code via MCP, so agents stop putting
<ycode-inline-variable>tokens in JSON-LD (which are not interpolated and produce invalid structured data).Changes
{{FieldName}}placeholders for custom code head/body on dynamic pages<ycode-inline-variable>used for SEO title/descriptionupdate_page_settingstool and field descriptionsTest plan
{{FieldName}}incustom_code.head, not<ycode-inline-variable>