Template syntax appears in visitor-readable content
ShipReady found a supported template-variable pattern in readable page content, or an ERB-style expression in non-code markup.
Why it matters
A template token shown to a visitor can indicate that intended page content was not substituted before publishing.
How ShipReady detects it
What it inspects
ShipReady reads already-fetched page HTML, removes scripts and code-like elements from readable text, and checks a maintained set of template syntaxes. ERB-style expressions are separately checked in non-code markup.
What triggers a finding
The rule triggers for one or more supported template tokens on a route that is not classified as documentation or content intended to quote such artifacts.
What the evidence shows
A supported template syntax was present in page content inspected by ShipReady.
Limits of this check
ShipReady does not execute a template engine, determine why substitution failed, inspect client-side rendering, or establish that every page has the same problem.
How to fix it
Trace the displayed token to its template or component
Find the token in the page source, confirm the intended value is supplied, and remove it only after the correct content is rendered.
How to verify the change
Inspect the deployed page
Review the served content after deployment and search for the affected syntax in user-facing templates.
Expected: The intended value is displayed instead of the supported template token.