Design the Drupal content model before the page layout

A page design shows one arrangement of content. A content model explains what that content means, who owns it, and where it can appear. In Drupal, making those decisions early helps prevent a site from becoming a collection of visually attractive pages that are difficult to edit or reuse.

Distinguish reusable information from presentation

A service title, description, and consultation link are information. A particular background colour or two-column arrangement is presentation. Model stable concepts as fields and content types. Use components for sections that editors need to arrange, while keeping design rules in the theme. Avoid asking editors to paste complete HTML layouts into rich-text fields.

Give each component a clear job

A hero introduces the page and its primary action. A service card explains one capability and links to detail. A process step describes one part of an engagement. Narrow responsibilities make components easier to document, test, and combine. Limit nesting and optional fields when they make the editing interface harder to understand.

Test the model with difficult content

Populate the design with a long title, a short description, a missing optional image, and translated text where relevant. Ask an editor to build a page without developer assistance. Watch for ambiguous field labels and repeated manual work. Adjust the model before the same problem is copied across dozens of pages.

A practical next step

Choose three representative pages and list the information they share. Build one small set of components, populate all three pages, and review both the rendered experience and the editorial form with the people who will maintain them.