Blocks
Six blocks for an agency page
An agency page has to book a call before the visitor opens the portfolio: six block categories, the right order, the faults that arrive from the CMS and the real catalogue counts.
Key points
- Six categories cover the agency page, but the case study goes before the team.
- Pick the hero block by the number of words it holds, not by the screenshot.
- The footer carries the registered address and VAT number: it is not decoration.
An agency page has to book a call before the visitor opens the portfolio. The catalogue indexes 1,556 blocks and the counts below were read from /api/stats on 2026-11-01: six categories cover the minimum path.
The per-category numbers are 51 hero, 53 feature, 24 team, 50 testimonial, 33 contact and 45 footer, measured on the catalogue category pages. No figure is estimated and none is rounded: what you read is what the page lists.
What the page has to do
An agency sells work the client has not seen yet, so the page has to replace the trust that is missing. It has to say on one screen which projects it handles, show two cases with a verifiable result, and leave a way to write without seven fields. It must not tell the story since 2009: it answers one question only, “can you build my project?”.
- On one screen: sector, kind of work and city, not a slogan.
- Two cases with client, problem and a result in figures.
- Team names and roles, because the client buys people.
- A short contact step: email, phone or a three-field form.
The order of the blocks
| Section | Role on the page | Blocks available |
|---|---|---|
| hero | name the sector and the project type | 51 |
| feature | show two cases with numbers | 53 |
| team | show who works on the project | 24 |
| testimonial | confirm with a client voice | 50 |
| contact | cut the friction of the email step | 33 |
| footer | give address, VAT number and legal links | 45 |
Order matters more than the block choice. Hero, feature, team, testimonial, contact, footer: if the visitor meets the form after three carousels, the page is already closed. The concrete case goes above the team, because it convinces before the face; the testimonial goes right after the team, so a client sentence confirms what the visitor has just read.
The blocks to start from
Four tables, one per category, with block, registry and file count. The file count tells how big the block is to install: an 8-file hero brings images, utilities and variants, a 6-file one bends more easily. Pick the block that already ships the mobile variant, not the one with the better screenshot.
Hero blocks
| Block | Registry | Files | Category |
|---|---|---|---|
| Hero 01 - Agency Hero Section | Shadcn Space | 8 | hero |
| Hero 02 - Real Estate Hero Section | Shadcn Space | 6 | hero |
Feature blocks
| Block | Registry | Files | Category |
|---|---|---|---|
| Feature 01 - Feature with Testimonials | Shadcn Space | 3 | feature |
| Feature 02 - Three Columns Feature with Icons | Shadcn Space | 3 | feature |
Team blocks
| Block | Registry | Files | Category |
|---|---|---|---|
| Team 01 - Creative Team Showcase | Shadcn Space | 2 | team |
| Team 02 - Modern Team Grid | Shadcn Space | 2 | team |
Testimonial blocks
| Block | Registry | Files | Category |
|---|---|---|---|
| Testimonial 02 - Testimonial Slider Showcase | Shadcn Space | 5 | testimonial |
| Feature 01 - Feature with Testimonials | Shadcn Space | 3 | feature |
What breaks in production
The usual fault is not the layout: it is the content that arrives from the CMS. The hero block holds three title words and receives twelve. The testimonial slider loads six photos at 400 KB and moves the text on the first paint. The contact form opens a mailto and on iOS shows nothing at all.
- Hero title beyond 90 characters: it wraps above the button and covers the image.
- Testimonial slider without width and height: measurable layout shift.
- Form without an endpoint: the button stays in loading for good.
- Footer with an embedded map: it blocks scrolling on mobile.
curl "https://ui.eneawork.it/api/blocks/category/team?limit=5"The call returns the team blocks with name, source, files and category: it shows how many real variants exist before you commit to a grid. If the response is short, that category does not cover your case and a different registry is the better bet.
A limit to declare
The catalogue has 24 team blocks, but nearly all of them assume square portraits in one format. An agency with mixed vertical photos has to rebuild the grid or crop the images: the block does not solve photo selection, and that stays art direction work.
In the catalogue: team showcase, agency hero and all blocks. The guides: measured heroes, block economy and accessibility checklist.
Frequently asked questions
How many sections does an agency page need?
Six categories are enough when each one carries real content: hero, feature with two cases, team, testimonial, contact and footer. A seventh section makes sense only when you hold an award or a client none of the six can show.
Does the case study go before or after the team?
The case first: the visitor looks for proof of work similar to their own, not faces. The team reassures about who will run the project, so it goes right after the case and before the client sentence that closes the sequence.
How do I choose among the 51 catalogue heroes?
Check how many mobile variants the block ships and how many words the title holds. An 8-file hero usually includes an image, a badge and two variants; a 3-file one fits a long title without touching the grid.
Is a footer needed on an agency page?
Yes, for two practical reasons: in Italy the registered address and VAT number are mandatory, and whoever scrolls to the bottom often looks for the address or phone. A 45-block footer works, provided it ships without an embedded map.
What do I measure after publishing?
The time to the first click on contact and how many forms stop after the first field. If the time goes past 40 seconds, the problem is almost always the section order, not the button label.