Blocks
4 blocks for an event page
An event page has to turn a date into a registration. Four categories, the countdown the catalogue lacks, the timeline and FAQ faults and the real block counts.
Key points
- Countdown is not a category: zero measured blocks, it has to be written.
- Date, place and price belong on the first screen, not in the timeline.
- The CTA repeats after the timeline and after the FAQ.
An event page has to turn a date into a registration, not describe a programme. The catalogue indexes 51 hero blocks, 15 timeline, 24 faq and 27 cta, read on 2026-11-01: four categories for an event page.
The counts come from the public category pages, measured the same day. One category is missing entirely and it is the most requested: countdown has zero blocks, so the countdown gets written by hand or taken elsewhere.
What the page has to do
Whoever looks at an event already has a calendar doubt: whether that date is free. The page should therefore put name, date, city and price on the first screen, and the programme only after that. It must also say what happens if it rains, whether the ticket is refundable and whether early arrival matters: the three questions that generate email, each costing the organiser time.
- Date, city and price visible before any scroll.
- A programme with times and names, not a wall of text.
- A FAQ that covers refund, access and weather.
- A CTA repeated after programme and FAQ, with the same label.
The order of the blocks
| Section | Role on the page | Blocks available |
|---|---|---|
| hero | say what, when and where | 51 |
| timeline | tell the programme of the day | 15 |
| faq | answer price, refund and access | 24 |
| cta | drive to registration | 27 |
Hero, timeline, faq, cta. The CTA at the end is not enough: repeat it right after the timeline, because that is where the visitor decides whether the programme justifies the trip. A countdown, if added, belongs to the hero and not to a section of its own: a dedicated block takes a whole screen for a fact that changes daily.
The blocks to start from
The tables list block, registry, files and category. The 1-file timeline is deliberately bare: times, titles and short descriptions. The 2-file FAQ is an accordion without deep links, so sharing one answer needs a manual scroll. In both cases the block saves layout, not logic.
Hero blocks
| Block | Registry | File | Category |
|---|---|---|---|
| Hero 01 - Agency Hero Section | Shadcn Space | 8 | hero |
| Hero 02 - Real Estate Hero Section | Shadcn Space | 6 | hero |
Timeline blocks
| Block | Registry | File | Category |
|---|---|---|---|
| Company timeline | evilrabbit | 1 | company |
| Glassmorphism Launch Timeline | uitripled | 1 | glassmorphism |
FAQ blocks
| Block | Registry | File | Category |
|---|---|---|---|
| FAQ 01 - Expandable FAQ Section | Shadcn Space | 2 | faq |
| FAQ | flx | 1 | faq |
CTA blocks
| Block | Registry | File | Category |
|---|---|---|---|
| CTA 02 - Video Background CTA | Shadcn Space | 3 | cta |
| CTA 01 - Gradient Call-to-Action Banner | Shadcn Space | 2 | cta |
What breaks in production
The classic fault is the countdown: whoever writes it compares the date with the browser clock and lands an hour off when daylight saving changes, or shows “0 days left” for twelve hours. The second is a timeline with images: each item carries a speaker portrait in a different format and the vertical line stops passing through the centre. The third is a CTA pointing at a form closed after the registration deadline.
- Countdown on local time: an hour wrong at the season change.
- Timeline with misaligned portraits: the line breaks.
- FAQ that cannot be linked: the answer repeats by email.
- CTA live after the deadline: registrations lost in silence.
curl "https://ui.eneawork.it/api/blocks/category/timeline?limit=5"The response lists the timelines with source and files: read it to see how many expect images and how many do not. A timeline without images is easier to maintain when the programme changes, and it almost always changes in the two weeks before the event.
A limit to declare
The countdown category has zero blocks: measured, not estimated. That means the most visible piece of an event page is also the only one with no catalogue entry, and it gets written with care for the time zone. Planning the page on blocks alone means adding half a day of work that appears in no table.
In the catalogue: event hero, components and all blocks. The guides: measured heroes, block economy and accessibility checklist.
Frequently asked questions
Why is there no countdown block in the catalogue?
Because a countdown is logic more than layout: it depends on time zone, registration deadline and language format. Registries publish copyable blocks and that part does not copy, so the category stays empty and the component gets written.
How many items does an event timeline hold?
Five to eight. Beyond that the page becomes a printable programme and the reader stops scrolling before the CTA. With many items, group them by time slot and leave the detail to a separate page.
Does the countdown belong in the hero or its own section?
In the hero, next to the date. A dedicated section takes a screen for a number that changes on its own, and on mobile it pushes the programme and the CTA further down, where nobody arrives.
How do I handle registrations after the closing date?
By replacing the button with a status line and a waiting list. The CTA block does not change shape by itself: you need a date condition and alternative copy, or the form stays open and registrations vanish without notice.
Is an inline form better than a link to the ticketing platform?
The link, when the platform handles payments and refunds. The form only pays off for free events with limited seats, where you collect name and email and manage the list. Two paths on the same page do not work.