FvRE v3.1 — Per-builder mapper results

The v3.1 converter now knows about Elementor, Bricks, Divi, Gutenberg, and Spectra (Ultimate Addons for Gutenberg). Each builder has its own block primitives — different class prefixes, different widget names. The mapper extracts the widget type from the rendered HTML and converts it to an FVS block.

Builders supported (v3.1)

Builder	Block prefixes	Count
Elementor	.elementor-widget-{name}, data-widget_type	42 widgets
+ Essential Addons	.eael-{name}	39 widgets
+ Premium Addons	.premium-addon-{name}	33 widgets
Bricks	.brxe-{name}	37 elements
Divi	.et_pb_{name}	51 modules
Gutenberg (core)	.wp-block-{name}	49 blocks
+ Spectra/UAGB	.wp-block-uagb-{name}, .uagb-{name}	49 blocks

Total: 300+ widget types across 5 builders + 2 addons.

Test results — real sites

Site	Builder	Total blocks	High-confidence	% high
WPAstra.com	Astra + Spectra (UAGB)	414	170	41%
ElegantThemes.com	WordPress + Extra	76	0	0%

WPAstra breakdown (170 high-confidence blocks)

Source widget	Count	→ FVS block
wp-block-uagb-container	80	rich-text/container
wp-block-uagb-info-box	20	card-grid/info
wp-block-uagb-image	20	image/single
wp-block-button	14	button/single
wp-block-uagb-advanced-heading	9	rich-text/text-heading
wp-block-uagb-counter__title	7	rich-text/counter
wp-block-uagb-buttons	6	button/group
wp-block-uagb-slider-child	5	carousel/item
wp-block-uagb-tabs-child	4	tabs/tabbed
wp-block-uagb-image-gallery	3	image-gallery/grid

ElegantThemes breakdown (0 high-confidence, all role-based)

The scanner misidentified this as Squarespace (it's actually WordPress + Extra). The Extra theme is registered in the theme classifier but the converter doesn't know what to do with it — it falls back to role-based mapping for all blocks. Future: add an "extra" / "divi" / "elegant-themes" mapper.

How the mapper decides which builder to use

1. Look at the recipe's classification.theme.builder_guess (most accurate)
2. If the theme is a Gutenberg-native theme (Blocksy, GeneratePress, Astra, Flatsome, Hello-Elementor), prefer Gutenberg mapper (because the page may not use Elementor even if it's installed)
3. Fall back to theme_guess (Gutenberg for known Gutenberg themes)

Why the high-confidence count varies

Two main reasons a block doesn't get high-confidence mapping:

1. The class prefix isn't in our mapper. The DOM has a class we don't know about. We fall back to the role-based guess (confidence 0.5).
2. The block is rendered as plain HTML without builder-specific classes. Many "background image" or "spacer" elements are just <div> with no widget class. The scanner sees a div, the mapper says "rich-text".

What v3.1 can do now (per-builder mappers)

• ✅ Elementor → FVS (42 widgets)
• ✅ Elementor + Essential Addons → FVS (39 widgets)
• ✅ Elementor + Premium Addons → FVS (33 widgets)
• ✅ Bricks → FVS (37 elements)
• ✅ Divi → FVS (51 modules)
• ✅ Gutenberg (core) → FVS (49 blocks)
• ✅ Spectra / UAGB → FVS (49 blocks)
• ⏳ Flatsome, Avada, Oxygen, Beaver Builder, WPBakery — not yet

What's next

1. Map the remaining common builders (Oxygen, Beaver Builder, WPBakery, Flatsome, Avada)
2. Wire the per-builder mappers into v3.2 CMS (so the editor knows what block type to render)
3. Build the multi-site dashboard (v3.3)

← back to v3 design · ← back to index