Use a section when the content has a section

By Gyata Tabiri · Revised October 30, 2026

I want page structure to clarify the content, not add markup for its own sake. A section earns its place when it identifies a meaningful topic that someone might need to understand or find.

Look for a topic

A service area, a chapter of an article, or a substantial part of a guide may form a section. A heading usually helps explain the subject. If the wrapper exists only to set a background or control spacing, a neutral container may be appropriate.

Distinguish independent content

An article can describe a piece that makes sense as its own composition, such as an insight or a case study. A section groups part of a broader topic. These decisions depend on the content; the visual shape of a card does not settle them.

Keep landmarks useful

Adding many named regions can make navigation more demanding. Use names and relationships where they make a meaningful part of the page easier to find. Inspect the accessibility tree rather than assuming every section becomes the same kind of landmark.

Explain the choice through the page

Consider a case study with context, contribution, and outcome. Those topics may warrant headings and grouping. A spacer between them does not. The structure should help someone follow the account and help the next developer preserve it when the layout changes.

The point for a team is an explainable document. The next person should be able to change the visual arrangement without losing the relationship between the content and its headings.

Project studies · Discuss a role or project

Reference: HTML section definition.