Start with the page job
Describe the customer task before naming a component. A product page might need to explain fit and care details; a collection page might need a campaign introduction; a landing page might need a focused path to one product group. The task tells you whether the content should repeat across many pages or exist only once.
Then write down who will update it after launch. If a marketing team needs to swap a campaign image or change a short heading, that is different from a developer-maintained layout rule. Shopify sections are theme components that can be arranged in templates, so a clear editing need is a useful reason to make something configurable.
Separate reusable structure from one-off content
A section is usually the right starting point when the same layout will appear in more than one place or when a merchant needs to rearrange it in the theme editor. Think of a product information panel, an image-and-text feature, or a collection introduction with a consistent structure. Reuse does not mean every section needs every possible option; it means the layout has a stable job.
Keep one-off campaign copy out of a generic component when it will not be reused. A single temporary announcement may belong in an existing announcement or text section rather than a new custom section. Ask whether another page will genuinely need the same structure before turning a small content change into a larger build.
Use blocks for repeatable items
Blocks work well when a section contains several items with the same kind of information, such as feature points, FAQs, logos, slides or steps. They let the merchant add, remove or reorder items without changing the surrounding layout. Shopify notes that sections are made of blocks with specific functions, and that available blocks depend on the section design.
Decide the limits deliberately. A three-step process may need a small maximum so the layout stays readable, while a FAQ may need more room. Define what each block needs to contain and what happens when it is empty. This avoids a section that technically accepts many blocks but becomes difficult to scan on a phone.
Choose settings with care
Settings should expose decisions a store team is likely to make, not every CSS value a developer can imagine. Useful examples include a heading, image, call to action, text alignment or a sensible spacing choice. Start with the content and layout choices that actually change between uses, then keep the rest consistent so the section remains recognisable.
For dynamic product or collection information, confirm whether the theme supports compatible dynamic sources before hard-coding content. Shopify documents that compatible sections and blocks can display dynamic information. Test the editing flow with a real product or collection so the merchant can see where the data comes from and when a manual override is appropriate.
Decide when a template is needed
Use a different template when the page needs a meaningfully different structure, not just a different heading or image. For example, a long-form editorial landing page may need a different sequence of sections from a standard product or collection page. Shopify’s theme editor lets merchants select and customize templates for different page types, so the template choice should reflect a stable page purpose.
Before building a new template, compare it with the closest existing one. If the change is only one optional section, an existing template plus a well-scoped section may be simpler to maintain. If the customer journey, content order and conversion goal all change, a separate template can make the differences clearer for both the store team and future developers.
Run a merchant and mobile check
Before treating the work as complete, test two paths: editing the content in the theme editor and viewing the finished page on a phone. The editor test catches confusing settings, missing default content and block limits; the mobile test catches crowded headings, awkward image crops and calls to action that fall too far down the page.
Keep the handover concrete. Note which template uses the section, which blocks are available, what each setting controls and what should not be changed without design review. A short walkthrough makes future updates less dependent on the original build team. If you are planning a more involved theme change, map the customer task and the merchant editing task before deciding the build scope.