A history, a roadmap or a process is a sequence, and a plain list flattens it — every step looks equally far from the one before.
A timeline keeps the order visible: events down a spine, alternating left and right, each with its own date, heading and content.
Before You Start
- Edition: Pro — the Timeline block needs Nexter Blocks Pro.
- Block to enable: Timeline, switched on under Nexter > Blocks in your WordPress dashboard.
Video Tutorial
Steps
- Add the Timeline block to your page.
- Pick a Style and, on style 2, an arrow style.
- Add your events. Each one takes a date, a heading and a description.
- For each event choose which side it sits on, and set its pin icon or image.
- Choose what fills each event’s media area — an image, custom HTML, or a pattern.
Each event has two content settings and they are easy to mix up: Content Type controls the text side, while the media type setting controls what fills the media area — an image, custom HTML, or a pattern.
How It Behaves
| Setting | Measured on a published page |
|---|---|
| Style 1 / Style 2 | Both render the events down a central spine; style 2 adds the arrow styling. Each event’s side is set per event, so you can alternate them or group them. |
| Masonry layout | Switches the timeline to an isotope grid rather than a fixed column — measured, the wrapper gains the masonry layout attributes. |
| Pin Style | Changes the marker on the spine — measured rendering the chosen style class. |
| Media area | Image, Custom HTML/Iframe Code, or a pattern. Images and patterns both render correctly — measured. |
- Each event is its own row in the event list, so events can be reordered without touching their content.
- The button needs its own toggle as well as its text. Measured: setting a URL and label alone rendered no button at all — the event’s Button toggle has to be on too. See the button doc.
- Patterns let an event hold a full block layout rather than a single image — see using a pattern in a timeline.
Limitations
- Custom HTML / Iframe Code is currently rendered as visible text, not as markup. Measured on a published page: an iframe pasted into that field appears on the page as the literal tag rather than an embedded frame. Until this is fixed, embed video and maps with the block made for them, or with a pattern. This is a known bug and has been reported to the development team.
- Do not switch AJAX Base on. Measured on a published page: with AJAX Base enabled the event renders an empty container and the pattern never appears, because the loader script it depends on is never added to the page. Leave it off and the pattern renders normally. This is a known plugin-wide bug and has been reported to the development team.
- The two content settings are separate — changing the media type does not change the text side, and vice versa.
- A timeline is one vertical sequence; it does not branch or nest.
Troubleshooting
My iframe shows as text on the page
That is the known bug described above — measured, the field’s HTML is printed rather than rendered. Use a pattern, or the block built for that media type, until it is fixed.
My pattern event is empty
Switch AJAX Base off for that event. Measured: with it on, the event renders an empty container and the pattern never loads.
My button is not showing
The button needs its own toggle as well as its text. Measured: setting a URL and label alone rendered no button at all — the event’s Button toggle has to be on too.
The events are all on one side
Each event carries its own side setting rather than alternating automatically. Set them one by one if you want them to zig-zag.
