Start here
What you change first
- The claim. It is the pattern.
- The proof paragraph. Put a number in it.
- The images. Click each cell and choose your file.
- The count. Four
core/groupcells in the rail. - The labels. "Why they come back" and "The evidence" head the two halves.
The signature moment
The evidence is ruled and the argument is not
There is exactly one rule in this pattern and it is drawn around the logos. The claim, the proof paragraph and the footnote have no border, no plate and no ground of their own; they are bare type on the band. The marks sit inside a rail closed on all four sides with a hairline between each one.
Theme handoff
What comes from where
From your theme
- Palette.
- Every rule.
- Typeface.
- Spacing scale.
Set by this pattern
- 62 / 38.
- A held measure.
- The type ramp.
- Four marks, one per row.
Full pattern notes
Why it works, and how it is built
Open a topic for the complete design reasoning, editing guidance and implementation notes.
Design rationaleComposition, intent and nearest alternatives
Overview
A full-bleed social-proof band that makes an argument. The wide side carries a tracked eyebrow, a display-size claim and a short proof paragraph on a held measure; the narrow side carries four client logos stacked in a closed rail. Core blocks only, and the image blocks include demonstration logos. Choose Replace to select your own marks.
It is the third answer in the logos section and it does a different job from the other two. logo-bar and its plaque display set names. logo-cells tables ten files. This one asserts something and then shows the marks that back it up, so it belongs on an about page or above a contact section rather than as a quiet strip under a hero.
The signature moment: the evidence is ruled and the argument is not
There is exactly one rule in this pattern and it is drawn around the logos. The claim, the proof paragraph and the footnote have no border, no plate and no ground of their own; they are bare type on the band. The marks sit inside a rail closed on all four sides with a hairline between each one.
That single asymmetry is what makes the section argue. A ruled box reads as a record, a citation, a list of references, and putting one next to unruled prose makes the prose read as a statement and the box read as its footnote. Reverse it, or rule both halves, and the band collapses back into two columns of stuff. Density contrast does the rest: one side is airy and set at three different sizes, the other is a regular stack of identical cells.
The scale collision is deliberate too. The claim runs at up to 54px and the labels either side of it at 15px, with nothing in between except the reading paragraph. There is no mid-sized subheading anywhere, which is what keeps the sentence loud in a section that is otherwise very quiet.
Make it yoursVariations and the edits to make first
What you change first
- The claim. It is the pattern. Make it a sentence somebody could disagree with; a claim that says "trusted by leading brands" gives the rail nothing to be evidence for.
- The proof paragraph. Put a number in it. The paragraph is the only place in the logos section where a specific fact fits, which is the whole reason this pattern exists.
- The images. Click each cell and choose your file. Use SVG or a transparent PNG; a logo on its own white rectangle will show that rectangle against your band, and no setting here can fix it.
- The count. Four
core/groupcells in the rail. Add a fifth by duplicating one, and give it the same top hairline the others have; the first cell is the only one without, because the rail's own top border draws that line. Beyond six the rail outgrows the argument and you wantlogo-cellsinstead. - The labels. "Why they come back" and "The evidence" head the two halves. Delete both for a plainer band; delete only one and the row loses its alignment at the top.
The variation
Masthead takes the claim out of its column and runs it across a 46rem measure at the top of the band, then puts the rail and the proof paragraph in the row beneath it, marks on the left. The base makes the marks the counterweight to the headline; the masthead makes the headline the title of the whole band and sets the marks level with the reading, so the section opens louder and argues more quietly. Same palette, same promise, different structure.
Theme behaviourInheritance, fixed decisions and contrast
What it inherits from your theme
- Palette. The ground is your
baseand every piece of type is yourcontrast, each a fallback chain ending on a colour WordPress itself guarantees. No accent anywhere: an accent's brightness varies by theme and this band is type, hairlines and other people's logos. - Every rule. The rail is drawn in
currentColor, so it is the same colour as the text beside it in whatever colour your theme sets, cannot resolve to nothing, and follows the band if you invert it. - Typeface. The pattern states no font family. The claim takes your theme's face, which is the thing worth looking at first: a display serif and a grotesque want slightly different tracking at this size.
- Spacing scale. The band's padding and the gaps between the three parts of the argument use the core spacing presets.
What it decides for itself
- 62 / 38. The argument takes the wide side and the marks the narrow one, which is the ratio that lets the claim break into two or three lines while the rail stays narrow enough to read as a column rather than as a second panel.
- A held measure. The proof paragraph and its footnote sit in a nested constrained group at
34rem, not the full 62% column, so the reading line stays around 65 characters. The claim is deliberately not held: a display line wants the whole column. - The type ramp. Eyebrow and footnote at
clamp(0.875rem, 1vw, 0.9375rem), the reading paragraph atclamp(max(1rem, 16px), 1.15vw, 1.1875rem)at 1.6 line-height, the claim atclamp(2.125rem, 4.2vw, 3.375rem)at 1.05 with negative tracking. - Four marks, one per row. Four is what balances a three-line claim plus a four-line paragraph. It is a column, not a grid: a second mark per row turns the rail back into the table that
logo-cellsalready is.
Contrast
Everything readable in the band is your contrast on your base, the highest contrast pair every stock block theme guarantees. The eyebrows, the footnote and the paragraph are small text held to the 4.5:1 body threshold; the claim is genuinely large text, above 34px at every width, so it would pass at 3:1, but it is on the same pair and is measured at the body threshold anyway. The rail is currentColor, so it carries the text's own ratio. No type sits on an image anywhere: the cells hold marks and nothing else.
Technical notesBlock mechanics, responsive behaviour and constraints
How a mark of any proportion fits the cell
Real logo files arrive at wildly different proportions: a square monogram, a long horizontal wordmark, a tall stacked lockup. So each image block sets width: 100%, a fixed height of 3.5rem, and scale: contain, which WordPress serialises as object-fit: contain; width: 100%; height: 3.5rem on the <img>.
The box is fixed, so all four marks occupy the same 56px band of height and read as one set. The mark is never cropped: contain scales the whole file until it fits inside that box and leaves the remainder empty, so a tall lockup shrinks on height and a wide wordmark shrinks on width, and nothing is cut off or stretched.
This is the opposite of the crop rule used everywhere else in the catalogue. A photograph uses scale: cover, because it may be cropped and must fill its frame. A logo may not be cropped and must not fill its frame: the space around a mark is part of the mark. The one thing to watch is a file with a lot of built-in transparent padding, which will look smaller than its neighbours because contain fits the file and not the ink inside it. Trim the file rather than raising the height on one cell.
At 390
Below 782px WordPress stacks the two columns, so the argument reads first and the rail follows it full width. The marks are still contained in fixed cells, so they get wider and stay the same height, which is the correct behaviour for a logo and the reason the cells are not set as a proportion.
The Styled look
olive-and-mustard turns the band into "As featured in" for a restaurant or a venue. It states deep olive #2f3321, cream #f1e8d2 type and rules, and mustard #e0b44a (6.7:1 on the olive) for the eyebrow, the heavy top rule of the rail and the line under each title. The rail holds four fictional publication titles set as type, each in its own treatment of the two stacks (italic, tracked capitals, bold, spaced capitals), so there are no logo files to source. The claim is an italic Didot stack (Bodoni MT, then Georgia) over Helvetica. The ruled rail is still the only ruled thing on the band.
Included images
The copied markup includes demonstration brand logos. The public image URLs keep the examples visible after pasting. Select an image or cover and choose Replace to use your own Media Library files. See image credits for the sources and licenses. Pasting an image URL does not import a Media Library attachment.
Questions
Logo claim: common questions
Does Logo claim need a plugin?
No. It is built only from core WordPress blocks (column, columns, group, heading, image and paragraph), so it pastes into the block editor with nothing to install.
Will Logo claim match my theme?
Choose by variation. Claim and rail and Masthead take your theme’s palette; Olive and mustard brings its own colours.
How many variations does Logo claim have?
3: Claim and rail, Masthead and Olive and mustard. Each is its own markup; choose one in the toolbar above the preview before you copy.
Can I use my own images?
Yes. Sample images stay in the copied blocks. Replace them in WordPress; pasting does not upload them to your Media Library.
Is Logo claim free?
It is included with a subscription, with every Core Pattern and variation. 62 Core Patterns are free to copy without one.
The markup
Core block markup and nothing else. Copy it, then paste it straight into the block editor: WordPress reads the delimiters and rebuilds the blocks.
Fetching the markup…Variation: Masthead
Fetching the markup…Variation: Olive and mustard
Fetching the markup…