The theme question that decides if you need a developer

Here is a test for any Shopify theme you are about to pay for.

Ask the developer: "Can I add a second testimonial to this page myself, without you?"

If the answer is no, or "just send it to me and I will add it", the theme was built with sections where it should have used blocks. You now have a website you have to phone someone to update, and you will be paying for that mistake every month for years.

This is what that difference is, in terms that matter to whoever owns the store.

Sections and blocks, without the jargon

A section is a band across your page. Your hero. A featured collection. A testimonials area. You add it, remove it, and drag it up or down in the theme editor.

A block is a repeatable item inside a section. One testimonial inside the testimonials area. One FAQ inside the FAQ list. One logo inside a logo bar.

The rule is simple: if you will ever want more than one of something, it must be a block.

Three testimonials should be one testimonials section containing three testimonial blocks. Not three separate sections. Not one section with nine text fields called "Testimonial 1 name", "Testimonial 1 quote", "Testimonial 1 role", and so on.

Why it matters to you and not just the developer

That "nine fields" version is extremely common in cheap theme work, and it fails in four specific ways.

You cannot add a fourth. The fields were hardcoded at three. A fourth testimonial is a developer request, a quote, and a wait.

You cannot reorder them. Moving the second above the first means cutting and pasting text between fields.

You cannot remove one cleanly. Delete the text and you often get an empty card, because nothing was built to handle absence.

Your admin becomes unusable. Nine fields for three testimonials is manageable. Ten team members at four fields each is forty fields in one long scrolling panel, and whoever maintains it starts to hate the site.

With blocks, all four of those are drag, click, done. By you, in the theme editor, in a minute.

The one real constraint

Shopify allows a maximum of 50 blocks per section. That is the only hard limit in this decision and it very rarely binds. Fifty testimonials in one section is more testimonials than any page should have.

If you genuinely need hundreds of repeating items, that is not a blocks problem. That is a metaobject problem, which is a different structure entirely and worth asking about.

How to tell what you have

You do not need to read code. Open your theme editor and look at a repeating area on your page, testimonials, FAQs, a logo bar, feature cards.

Built with blocks: you see a list of individual items in the sidebar, each one clickable, with an "Add" button underneath and a drag handle on each.

Built badly: you see one long panel of numbered fields. "Feature 1 title", "Feature 1 text", "Feature 2 title". No add button.

If it is the second, ask your developer to convert it. On an existing theme this is usually a few hours per section, and it is one of the highest-value small jobs available, because it converts a recurring cost into a one-off one.

What to specify before a build starts

If you are commissioning a theme, put this in the brief. It costs nothing at the start and it is the difference between owning your site and renting access to it.

Ask for these, by name:

Every repeating element as blocks. Testimonials, FAQs, features, team, logos, steps, tabs, badges. All of them.

Sensible defaults. A new block should look right the moment you add it, not force you to fill in six fields before the page stops looking broken.

Graceful emptiness. If you remove all the blocks from a section, the section should disappear, not leave a blank band with a heading over nothing.

Presets. So you can drop a preconfigured version of a section onto a new page rather than rebuilding it each time.

And then test it before you sign off. Go into the theme editor and try to add a fourth testimonial. If you can, the job was done properly.

The commercial argument

A theme built with blocks is a theme your team can run.

A theme built without them is a theme where every content change is a support ticket. At a modest hourly rate and one change a fortnight, that is a few thousand pounds a year to do things the theme editor should let you do in a minute. Over the life of a theme it is comfortably more than the build cost.

It also slows you down in ways that do not appear on an invoice. Campaigns launch late. Copy that should be tested does not get tested. Seasonal content stays up past the season, because changing it requires someone else's calendar.

Developers who build this way are not always cutting corners. Hardcoding fields is genuinely faster to write than building a proper block schema. It is faster for them, once, and slower for you, forever.

---

Every theme we build uses blocks for repeating content, with defaults, empty states, and presets, so your team can run the site without us. We hand over the full source code on launch, clean and commented, with no licensing.

Not sure what your current theme is? Book a free 30 minute call and we will look at it with you, or see how we build themes.