The built-in style-1 through style-4 card designs cover common layouts, but a blog might need its own distinctive card design.
Dynamic Listing’s Custom style lets you design that card as an ordinary Elementor template, then reuses it as every post’s card – no code required.
For the full settings tour of the Dynamic Listing widget, see Dynamic Listing Widget Settings Overview.
Requirement – This widget is a part of The Plus Addons for Elementor Pro, make sure it’s installed & activated to enjoy all its powers.
Before You Start
- Prerequisite: Elementor (free) installed and active.
- Edition: Dynamic Listing is a Pro widget – it needs The Plus Addons for Elementor Pro installed and its license activated. It will not appear in the free plugin.
- Widget to enable: go to The Plus Addons > Widgets, search for Dynamic Listing and turn its toggle on.
Steps
- Add the Dynamic Listing widget, with Post Type set to
post. - Under Content Layout, set Style to Custom.

Choose (or create) the card template in Select a template, which opens in the normal Elementor editor – place the post’s title, excerpt, featured image and any other fields as Dynamic Tags anywhere in the design, exactly like building a page.

Turning on Multiple Loops exposes up to four more template slots (Loop Template 2-5) and a Template Order option (default, reverse or random) to cycle between several card designs across the listing instead of repeating just one.
Settings Overview
| Setting | What it does | Default |
|---|---|---|
| Style | style-1 to style-4, Custom, or Smart Loop Builder. | style-1 |
| Select a template | The Elementor template used as the card (Style = Custom). | (none) |
| Multiple Loops | Cycles between several templates instead of one. | Off |
Related Docs
- How to Create Elementor Custom Post Type Loop Skin?
- How to Create a Custom Post Type Loop Skin in Elementor Using Smart Loop Builder?
Not verified
So you know exactly what has and has not been checked:
- The Template Order = random option’s actual shuffle behavior across a full page load/reload cycle was not repeatedly sampled to confirm randomness.






