Theme Development Checklist: Field Kit

Online Store 2.0 lets a custom design live as sections and blocks the owner arranges in the theme editor. These checks keep the design yours and the pages theirs.

01Choose the path

Confirm a theme meets your needs before considering headlessHeadless means rebuilding infrastructure and maintaining it, which most stores do not need.
List the page types the merchant must be able to compose and editPages left out of the plan end up hard-coded, and every change needs a developer.
Break the design into reusable sections, such as a promo or logo wallOne-off page layouts cannot be reused or rearranged, which defeats Online Store 2.0.
Decide which content comes from settings and which from metafieldsDeciding late means rebuilding sections once product data has to fill them across the catalog.

02Build sections and blocks

Give each section a schema of editable settings: text, links, alignmentSettings missing from the schema are values only a developer can change.
Add presets so the section can be added to pages from the editorWithout presets, the section exists in code but the merchant cannot place it.
Model repeatable items as blocks with their own settingsHard-coded lists force a developer visit every time a logo or testimonial changes.
Loop over section.blocks in Liquid to render themBlocks the merchant adds or reorders will not appear if the template ignores them.
Keep templates as JSON and section files in version controlPages as data stay editable, while the design stays reviewable and recoverable in code.

03Connect content and apps

Drive product sections from metafields, such as specs or size guidesContent typed into each section must be re-entered for every product and drifts out of date.
Wrap metafield output in conditions so empty values do not renderProducts missing a value otherwise show empty labels or broken layout.
Use app blocks instead of pasting app embeds into theme codeHardcoded embeds are fragile and break when the app or the theme changes.
Test that the merchant can add, remove and reorder sections on each pageIf the editor workflow fails, the theme is custom but not editable, and the point is lost.

How to use this

Review the theme from the merchant's seat in the editor. A good result: every page type is composed from sections, repeatable items are blocks, product data comes from metafields, and routine changes need no developer.

The rest of the kit is one step away.

Leave your email and the full kit opens right here, ready to work through or save as a PDF.

Kept private. Never shared or sold.