Dynamic sources
Definition
Dynamic sources connect a section setting to a metafield or another store object instead of a typed-in value. The binding is made in the theme editor and stored in the template, so one section can serve every product or collection while the content comes from the record. The setting's own value stays behind it as the fallback.
Documented at shopify.dev, dynamic sources.
How We've Used It
This is the difference between a section per collection and a section for all of them. A collection hero whose heading, body copy and two images are bound to that collection's metafields turns a launch into a merchandising task, filling four fields on the record, rather than a theme deploy. We use the same binding for a headline override where the real title should remain above it as an eyebrow. Two rules keep it safe: every bound value is escaped before it renders, because a metafield holds authored content and can hold markup, and the section still has to look finished when the fields are empty.
Builds Using It
One further gated build uses it; its page follows.
Related Entities
- Liquid section schema and settings — the settings a source binds to.
- JSON templates — where the binding is stored.
- Liquid snippets — the shared renderers reading those values.