Is 'we need a non-commerce content experience wrapped around the store' (editorial, brand storytelling) a legitimate headless trigger, or can a theme handle that too?
Short answer
An editorial layer is not a headless trigger on its own. A Shopify theme template holds up to 25 sections and 1,250 blocks (Shopify Help Center, October 2026), and Shopify's metaobjects give it structured content. Shopify's February 2026 guide to headless content management systems sets the headless bar at "multi-channel content reuse", so one website rarely clears it.
- Sections per template
- Up to 25The theme designer sets which sections and blocks each template accepts (Shopify Help Center, October 2026).Source: Shopify Help Center (Sections and blocks)
- Blocks per template
- Up to 1,250 across all sectionsBlocks that support nesting go up to eight levels deep, in themes built on theme blocks such as Horizon (Shopify Help Center and changelog, October 2026).Sources: Shopify Help Center (Sections and blocks); Shopify changelog (Horizon: 10 new free themes by Shopify)
- Metaobject entries one page loads
- 1,000 unique entries of one typeA definition stores up to 1,000,000 entries, but one Liquid page render loads at most 1,000 of a type and 250 per paginated page (Shopify developer docs, October 2026).Source: Shopify developer docs (Metaobject limits)
- Shopify's headless content bar
- Multi-channel content reuseShopify's February 2026 guide says themes "often deliver more value" for teams focused on speed, simplicity and storefront performance (Shopify, October 2026).Source: Shopify Enterprise blog (Headless CMS for Shopify: How It Works)
Deploi’s call
Not on its own: an editorial requirement justifies a headless content management system (CMS), and a headless CMS does not require a headless storefront. We say that even though Headless CMS is one of the six services Deploi sells. The project we would rather ship is a content model behind a Shopify Liquid theme, because it is the cheaper one.
WaitStay on the theme's blog and metaobjects while
- One storefront publishes the content and a few editors run it, the profile Deploi's headless CMS record scores WAIT on metaobjects, Shopify's built-in structured content entries (October 2026).
- You publish a post or two a month, the cadence Deploi's editorial hub record scores WAIT (October 2026).
- The complaint is that the blog looks bad, which is a theme fix.
BuildPut a headless CMS behind your Liquid theme when
- You run a weekly or faster editorial program with several authors, which the editorial hub record scores BUILD with the CMS rendered into your theme (Deploi decision record, October 2026).
- Editors need approval steps: metaobjects have "no review workflow" (Deploi's headless CMS record, October 2026), and neither Shopify nor Adobe ships a content approval chain.
- The same content must render outside the website, in an app, a newsletter or on retail screens, the profile Deploi's headless CMS record scores BUY for Sanity, Contentful or Storyblok (October 2026).
Basis: Should You Build or Buy Your Blog and Editorial Hub on Shopify?, our Build vs. Buy decision record, scored BUILD.
Is a headless CMS the same decision as a headless storefront?
No. A headless content management system (CMS) and a headless storefront are separate decisions, and in Deploi's judgment most editorial briefs need only the first. That split decides the editorial exception to headless as a deliberate minority path on Shopify.
A headless CMS keeps content in a system built for editors, with its own model, workflow and roles, and delivers it through an application programming interface (API). A headless storefront means your own application renders the pages instead of Shopify's Online Store. A Liquid theme, built in Shopify's template language, can render content from a headless CMS or from Shopify itself, so choosing a CMS does not force a new storefront. Shopify's metaobjects, its built-in structured content entries, are readable "in themes using Liquid and through the Storefront API" (Shopify Help Center, October 2026). Deploi's editorial hub record scores a headless CMS rendered into the existing theme BUILD (October 2026).
Shopify's own guide draws the same line: "Shopify themes use an integrated CMS that connects content, design, and commerce in one system," while "headless makes sense when multi-channel content reuse is a core requirement" (Shopify, October 2026).
How much editorial layout can a Shopify theme hold?
A Shopify theme holds more editorial layout than most programs use: up to 25 sections and 1,250 blocks per template (Shopify Help Center, October 2026). Horizon, Shopify's free theme collection launched on 21 May 2025, is built on theme blocks (Shopify changelog, October 2026). Shopify defines theme blocks as blocks "defined within your theme" that "can have dynamic functionality, such as nesting" (Shopify Help Center).
| Capability | Published limit or behavior |
|---|---|
| Sections per template | Up to 25 |
| Blocks per template, across all sections | Up to 1,250 |
| Nesting for blocks that support it | Up to eight levels, in themes built on theme blocks |
| Structured content | Metaobjects, readable in Liquid and the Storefront application programming interface (API) |
| Which blocks each section accepts | Set by the theme designer |
A long-form article with pull quotes, inline product modules, a gallery, a video and a shoppable footer sits well inside those limits. So does a campaign hub of six landing pages, each with its own layout. In Deploi's judgment, layout alone is rarely the reason to leave the theme, because it is the part these limits already cover.
Which editorial needs genuinely strain a theme?
Three editorial needs genuinely strain a Shopify theme, and none of them requires a headless storefront.
- Editorial workflow. Shopify lets you publish a blog post immediately or schedule it (Shopify Help Center, October 2026), but approval steps are missing, as the content staging comparison with Adobe Commerce shows. That gap is the usual reason brands buy a content management system (CMS), and a headless CMS with a Liquid front end closes it.
- Content reused outside the website. Once one article renders in a newsletter, an app and on retail screens, an application programming interface (API) content model earns its cost, because that is the "multi-channel content reuse" Shopify names (Shopify, October 2026).
- Very large archives. Metaobjects store up to 1,000,000 entries per definition, but one Liquid page render loads at most 1,000 unique entries of a type, and 250 per paginated page (Shopify developer docs, October 2026). Thousands of articles with faceted browsing strain that model.
So all three argue for a headless CMS, not for a headless storefront.
In what order should you solve an editorial brief?
Deploi solves an editorial brief in five steps, because the content model decides the cost and the rendering layer comes last.
- Write down the five editorial capabilities you are missing, in editors' language, not architecture language.
- Check each against theme blocks and metaobjects, Shopify's structured content entries; most layout items resolve there.
- Whatever remains is usually workflow, so price a headless content management system (CMS) that feeds your Liquid theme, the storefront Shopify renders from its template language.
- Bring the storefront into scope only if the content must render outside the website.
- If you reach step four, you have a multi-surface problem, which is the legitimate headless case.
When should you not decouple the storefront for content?
Do not decouple the storefront for content when a theme fix would settle the brief, when nobody has chosen the content model, or when one person does all the publishing.
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- The category treats "content-led brand experience" as a headless trigger, which conveniently makes the largest possible version of the project the correct one. Shopify's own guidance sets the bar at multi-channel content reuse, and a brand publishing to one website does not clear it.
- Our judgment
- In our judgment, when we take the "we need editorial" brief apart, the items sort into layout and workflow, and layout is nearly always solvable in the theme. Workflow is the real gap and it is the one that never appears in the original brief, because the people who feel it are editors and the people writing the brief are usually not.
- What this page adds
- The parent asks whether headless is still a minority path on Shopify. This page tests the editorial exception: it gives the published limits a theme has to outgrow (25 sections, 1,250 blocks, eight nesting levels, 1,000 metaobject entries per page render) and separates a headless CMS from a headless storefront, which turns most editorial briefs into a content project rather than an architecture project.
Decision records behind this answer
When this answer changes
- Shopify raises the 25-section or 1,250-block template limits, or the 1,000-entry metaobject limit per page render.
- Shopify adds approval steps or editorial roles to blog posts or metaobjects.
- Shopify revises its February 2026 guidance that headless makes sense when multi-channel content reuse is a core requirement.
- Deploi's headless CMS record moves its one-storefront verdict off WAIT.
Related questions
This follows from Is the honest 2026 recommendation still 'headless is a deliberate minority path,' or has that shifted as Hydrogen has matured?
- Is a design-system-heavy enterprise brand (the profile Shopify itself points to for headless) actually different from a typical mid-market brand considering Hydrogen?
A design-system-heavy enterprise brand differs from a mid-market one in payroll and front ends, not in its design system.
- Is Adobe Commerce's page-builder/content-staging workflow genuinely more mature than Shopify Plus's theme-editing tools for a large marketing team?
Adobe Commerce is more mature on content staging, not page building.
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Shopify Help Center, Sections and blocks
- Shopify Enterprise blog, Headless CMS for Shopify: How It Works
- Shopify Help Center, Metaobjects
- Shopify developer docs, Metaobject limits
- Shopify changelog, Horizon: 10 new free themes by Shopify
- Shopify Help Center, Writing blog posts
- Deploi Build vs. Buy, Should You Build or Buy a Headless CMS for Shopify Content?
- Deploi Build vs. Buy, Should You Build or Buy Your Blog and Editorial Hub on Shopify?