What are additional fields (fields) in articles for
CMS articles have a fields column (JSON) for metadata. The system automatically generates SEO tags from them - Open Graph, Twitter Card, and schema.org (JSON-LD).
Edit fields in the Additional fields section at the bottom of the article form.
How fields vs page template works
Article fields are data (JSON keys/values). The Blog page template is HTML with Liquid tags that read this data.
Cascade: the Blog page has fields (e.g. default CTA), the article has fields (e.g. audio_url). The template reads:
-
{{ cta_btn }}- from page fields -
{{ fields.audio_url }}- from article fields -
{{ title }},{{ content }}- from article model columns
SEO fields (automatic)
audio_url
Path to an audio file (mp3). Enter a CMS Assets path or full URL. Generates og:audio and AudioObject in BlogPosting schema.
video_id
YouTube video ID. For https://www.youtube.com/watch?v=dQw4w9WgXcQ enter: dQw4w9WgXcQ. Generates og:video and VideoObject.
Embedding in article content
Fields only generate meta tags. For visible players, add HTML in the Content field:
YouTube embed
<div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden; border-radius: 12px; margin: 2em 0;">
<iframe src="https://www.youtube.com/embed/VIDEO_ID" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border: 0;" allowfullscreen></iframe>
</div>
Audio player
<div style="margin: 2em 0; padding: 1.5em; background: #f8fafc; border-radius: 12px;">
<p style="margin: 0 0 0.5em; font-weight: 600;">Listen to the article</p>
<audio controls style="width: 100%;"><source src="/cms/assets/123/view" type="audio/mpeg"></audio>
</div>
What should NOT be in article fields
Don’t duplicate model columns (title, author, date) or page fields (CTA). Use separate articles per language.
Example
{"audio_url": "/cms/assets/123/view", "video_id": "dQw4w9WgXcQ"}
Most articles will have empty fields ({}) - and that’s OK.