dembrandt/dembrandt-skills/layout-paradigms-and-consistency

Layout Paradigms and Consistency

A layout is not a neutral container you pour content into. The layout paradigm you choose is part of the argument about how the content should be read, compared, and acted on. Two products showing the same data can communicate completely different things depending on whether that data is a feed, a table, or a board.

This skill operates at the macro scale of consistency. It sits above [[component-family-consistency]] (the meso scale — buttons and inputs sharing one DNA) and above token-level consistency like [[button-states]], [[status-colors-and-errors]], and [[modular-scale-typography]] (the micro scale). Consistency is not one rule — it is the same discipline applied at three altitudes.

Consistency operates at three scales

A product can have perfect tokens and a coherent component family and still feel broken — because every screen is laid out differently and the user re-orients on every navigation. Macro consistency is what makes a product feel like one application.

Layout is downstream — it serves something upstream

A layout paradigm is never the starting point. It is a consequence of decisions made earlier, and a means to ends defined elsewhere. Choosing a layout in isolation — "let's use a dashboard because dashboards look impressive" — is the most common way layouts go wrong.

It flows down from information architecture. The data model and structure ([[information-architecture]]) largely determine the candidate paradigms. Entities that move through states want a board; records compared on shared fields want a table; a hierarchy of containers and items wants master–detail. If the IA says "tasks belong to projects and have a status," the layout has already half-decided itself. Get the IA right first, then read the paradigm off it.

It serves the brand and the story. The same content can be laid out to feel calm or urgent, premium or utilitarian, editorial or operational. Layout is one of the loudest carriers of brand tone ([[brand-visual-language]]) and of the narrative you want the user to experience ([[motion-and-storytelling]]). A spacious single-focus layout tells a different story than a dense dashboard of the same data. Ask: what should the user feel here, and what are we trying to say? — then pick the paradigm that says it.

It serves the user experience. Ultimately the test is the user's task and context: what are they trying to do, how often, on what device, under what pressure ([[ui-density]], [[responsive-paradigms]]). The paradigm that best serves the task wins, even when a flashier one is available.

So the order is: IA and brand intent first → derive the paradigm that supports them → then apply consistency. Part 1 is how you derive it; Part 2 is how you keep it.

Part 1 — Choose the paradigm that fits the content

Start from the nature of the content and the primary task, not from a default grid. Ask: what relationship between items matters most here? The answer points to a paradigm.

The paradigm interacts with other layout skills: it must group coherently ([[gestalt-ui-organisation]]), establish one clear emphasis ([[visual-emphasis-and-hierarchy]]), reflect the data model and naming ([[information-architecture]]), and adapt — not merely shrink — across breakpoints ([[responsive-paradigms]]). Where a real-world metaphor reinforces the paradigm (a board feels like cards on a wall), lean on it ([[real-world-metaphors]]).

A view can offer more than one paradigm. A collection of records is legitimately a table and a gallery and a board, chosen by the user per task — see [[data-display-and-selection]]. The point is that each option is a deliberate fit, not an accident.

The narrative long-scroll — the product narrative framework

Marketing and landing pages are the one paradigm where sequence is the argument. Every other paradigm arranges content the user already wants; this one earns each scroll from someone who has committed to nothing. Judge a landing page by how it carries a stranger through these beats — not by whether the sections look good in isolation.

The beats are the same everywhere — B2B and B2C, software and physical goods, a global manufacturer and a local shop. What changes is their weight and their evidence. An industrial or spare-parts buyer wants proof, specification, fit and availability, and will read further to get it; a fashion or consumer page carries the hook in the imagery itself and reaches the CTA in far less scrolling; an internal tool's page can skip persuasion but still owes the visitor what this is, why it exists, how to start. Decide which beats carry the load for this audience before deciding what the page looks like.

The hook is a question, not a summary. A good hero states one value and leaves the visitor thinking "I want to see how this works." It gets that from size and air, not decoration ([[visual-emphasis-and-hierarchy]]). If the short headline is not explanatory enough alone, add a smaller supporting line under it rather than lengthening the headline. Pair it with the product actually running — screenshot, video, or live demo, never a mockup of behaviour the product does not have ([[authentic-product-representation]]).

Value propositions are benefits, not features. "AI dashboard" and "14 mm hardened steel" are nouns; "the numbers that matter at a glance" and "survives a season of gravel roads" are what the visitor gets. A line that could sit unchanged on a competitor's page is not a value proposition.

Every claim carries proof. The bolder the claim, the harder the evidence. What counts as hard evidence is set by the field, not by fashion — a test report and a fitment guarantee do the work a customer logo does elsewhere. Unproven superlatives cost credibility on the claims that are true.

Stakes come from consequence, not pressure. State what standing still costs. Manufactured scarcity — fake countdowns, invented "3 spots left" — spends the trust the rest of the page just built.

The CTA names the action. "Learn more" describes nothing. "Start free", "Check fitment", "Request a quote", "Find your size" tell the visitor what happens next, and hand off to a flow that delivers exactly that ([[user-flows-and-guided-paths]]).

The question chain

The narrative works because it answers the visitor's questions in the order they arise:

What is this? → Is it for me? → Why is it better? → Can I trust it? → How does it work? → How much effort is this? → What do I do next?

This is the sharpest test here. Walk the page top to bottom and mark where each answer lands. If the visitor has to hunt or scroll back, the narrative is broken however good the sections look. Answering early is a defect too — pricing above the fold answers "how much effort?" to someone still asking "what is this?".

What the strongest pages share

The best pages in every sector — a developer platform, a machine-tool supplier, a clothing label, a regional garage — converge on the same discipline:

• One message per viewport — each section answers exactly one question in the chain.
• No more copy than the beat needs — persuasion sections stay short and carried by whitespace, while specification and proof sections are allowed the detail a serious buyer came for.
• Real product imagery and video over abstract illustration or stock photography.
• Benefit to proof, fast — claims do not stack up unsupported.
• The CTA repeats down the page, so the visitor can act the moment they are convinced.
• One visual rhythm — section spacing, type scale, and imagery treatment repeat ([[modular-scale-typography]], [[brand-visual-language]]).
• Restrained motion that supports the sequence instead of competing with it ([[motion-and-storytelling]]).