Page Builder
Sections, columns and nested containers with twenty-five widgets, set per screen size, drawn as plain HTML and CSS with no script. Layouts are edited with plain forms or through the API, and pages built with Elementor or Divi are converted by its importers.
Not open yet No card
Description
Sections, columns and nested containers with twenty-five widgets, set per screen size, drawn as plain HTML and CSS with no script. Layouts are edited with plain forms or through the API, and pages built with Elementor or Divi are converted by its importers.
What it does
- Sections, columns with a width per screen size, and containers nested up to eight deep
- Spacing, background colour, picture and gradient, alignment, width and widest width, a border on one side, heading styles per level inside text, text size and visibility set per screen size: wide, tablet and phone
- Twenty-five widgets, all complete without scripts: heading, text, image, button, icon, icon box, image box, spacer, divider, video, icon list, accordion, tabs, testimonial, team member, counter, progress bar, price table, gallery, social icons, call to action, form, newsletter sign-up, latest posts and HTML
- An editing screen made of plain forms: add, fill in, reorder by position number, copy, move and remove
- An API for reading and writing whole layouts, so an agent can build a page in one request
- An importer for pages built with Elementor, with a check-first report that names everything it could not carry
- An importer for pages built with Divi (the Divi theme or the Divi Builder plugin): sections, rows with Divi's own column widths and gutters, specialty and fullwidth sections, inner rows, and its common modules, with a check-first report that names everything it could not carry; a Divi contact form is made in the Contact Forms module when that module is active
- A footer built in Divi's Theme Builder comes across as a layout and is shown in the theme's footer by the “Page Builder footer” part, which the owner places like any other part; any layout can be shown there
- Pictures in imported layouts move with the site: once Core's migration has brought the old site's files over (Migrate, Pictures and files), each picture in a layout is swapped for the copy here, whichever of the two is run first
- Words inside a layout are found by the site's search, on the page that shows the layout
- A Shortcode widget holding a Contact Form 7 shortcode becomes a Form widget showing that form, once the Contact Forms module has imported it, in either order
- Coming from the Hello Elementor theme: use any theme built from the theme kit together with this module. Hello Elementor draws nothing of its own (Elementor draws the pages), so there is no theme design to bring over: import the Elementor pages here, then set the header, footer, palette and fonts in the kit theme's Customize screen. Each imported page is set to full width with its title hidden as it was, and a page that used Elementor's blank Canvas template also hides the site header and footer.
- Drag and drop, and editing on the page itself: the editing screen is plain forms, and a change is seen on the page after saving. A live visual editor needs a script-driven editor, which this module does not ship. Not built yet.
- Animations, motion effects, sticky and absolute positioning, shape dividers, masks, video and slideshow backgrounds: none. Gradients are drawn from a Divi import; an Elementor gradient keeps its first colour. The importer names each one it meets. Not built yet.
- Custom CSS and custom class names per element: a layout can never carry a style rule, only checked values. Not built yet.
- Site parts built with Elementor Pro's theme builder or Divi's Theme Builder (headers, footers, single-post and archive templates, pop-ups): set the header and footer in the theme; the Popups module makes pop-ups. Not built yet.
- Carousels, sliders and lightboxes: an image carousel becomes a grid, a slider's slides are shown one under another, and a gallery picture opens as the full-size file. Not built yet.
- Counting up in the Counter: the number is shown at once. Not built yet.
- Icons: 37 built-in line icons, not an icon font. Social links show a short text mark, not the networks' logos. Not built yet.
- Fonts loaded from elsewhere: a font is matched to the closest built-in family of the same kind, made of fonts already on visitors' devices. Not built yet.
- Global colours and fonts changing a whole site from one place inside the module: imported globals follow the theme's palette and fonts instead, which are changed under Customize. Not built yet.
- A panel inside the page editor: Core's editor has no place for a module to add to, so a layout is edited on this module's own screen, one link away from its page. Not built yet.
- Edge-to-edge sections on a theme not built from the theme kit: there a layout is as wide as the theme's content column. Not built yet.
- The Form widget building forms itself: it shows a form made in the Contact Forms module, by its number. An imported Elementor form arrives as a note of its fields, to rebuild there. Not built yet.
- Divi presets, hover settings and dynamic content other than the page title: the import names each one it meets. Not built yet.
Stands in for
Elementor, Elementor Pro, Divi Builder.
These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From Elementor
- Comes across: Every page and post built with Elementor in a WordPress export, and pages saved as templates: sections, columns and nested sections; flexbox containers nested inside each other; column and container widths per screen size; padding, margin, background colour and picture with its veil, border, corner radius, shadow, least height, text alignment and hidden-on-screen-size settings. These widgets convert: heading, text editor, image, button, icon box, image box, spacer, divider, video, icon list, accordion, toggle, tabs, testimonial, counter, progress bar, basic gallery, image carousel (as a grid), social icons, HTML, menu anchor, and from Elementor Pro the call to action, gallery and form (as a note of its fields). Elementor's four built-in global colours follow the theme's palette and its global fonts the theme's fonts; custom global colours keep their own value. A widget with no equal here keeps its words and links as plain content and is named in the report.
- Does not: Animations, motion effects, positioning, shape dividers, gradients (the first colour is kept), custom CSS and class names, video backgrounds, uploaded SVG icons, fonts loaded from elsewhere, reversed order in containers, and theme-builder templates such as headers, footers and pop-ups. Pictures keep the old site's address until uploaded here. Forms must be rebuilt in Contact Forms. Scripts, frames and styles inside Text and HTML widgets are removed. Not yet verified against a live export: the fixture is synthetic and some settings are read on a best guess, each named in the import report (column gap sizes; flexbox container direction, alignment, gap, wrap and padding defaults; stacking on phones).
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Divi
- Comes across: Every page and post built with Divi 4 in a WordPress export (or through the WordPress login connection), Divi Library layouts, sections and rows, and layouts exported from the Divi Builder (.json) with the presets and global colours they carry: regular, specialty and fullwidth sections, rows with every column structure and Divi's gutter widths, inner rows, row width and widest width; padding and margin per screen size, background colour, picture and gradient, border, rounded corners, shadow, text colour and alignment, hidden-on-screen settings and module anchors. These modules convert: text, image, button, blurb (as an icon box or image box), call to action, divider, code (scripts removed), video, gallery, slider, fullwidth header, fullwidth image, testimonial, team member, accordion, toggle, tabs, number and circle counters, bar counters, price tables, social follow, contact form (made in Contact Forms when it is active, otherwise kept as a note of its fields), email opt-in (as a newsletter sign-up), map (as its addresses), blog (as latest posts), icon, and the post title. Global modules come in as they stood. A module from Divi or an add-on with no equal here keeps its words and links as plain content and is named in the report with its maker.
- Does not: Animations, hover and sticky settings, transforms and scroll effects, parallax, video backgrounds, shape dividers, presets, custom CSS and class names, link and list styles set inside a Text module, presets when the file does not hold them (a WordPress export does not), dynamic content other than the page title, fonts loaded from elsewhere (matched to the closest built-in family), and Divi's icon font beyond the common icons. Theme Builder templates, Divi Pixel pop-ups and portfolio projects are named, not converted. Menu, sidebar, search, login, shop and portfolio modules show nothing in a page. Pictures keep the old site's address until brought over. Scripts and frames inside Code and Text modules are removed. Not yet verified against a live export: the fixture is synthetic, and Divi's default spacing is drawn at its own published defaults, which the import report names as a best guess.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
No importer yet for: Beaver Builder, WPBakery Page Builder.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
1.3.0 November 19, 2026
Page Builder 1.3.0: Divi pages come across closer to how they looked. Headings inside a Text module keep their own font, weight, size per screen, line spacing and colour per level; a border on one side, a price table's coloured heading and a counter's number size and colour are carried; a HubSpot form put in with a Code module is held by a Form widget that says it is being moved. Divi presets and global colours are applied when the file holds them, and a layout exported from the Divi Builder (.json) can be imported on its own. A footer built in Divi's Theme Builder becomes a layout shown in the theme's footer by the new Page Builder footer part. Saving a box or widget on the editing screen now keeps the values it has no control for.
1.2.0 November 19, 2026
Page Builder 1.2.0: pages built with Divi now come across with their layouts. Its Divi importer (Migrate → Divi, the site's WordPress export) reads each page's Divi shortcodes: regular, specialty and fullwidth sections, rows with every column structure at Divi's own column widths and gutters, inner rows, Divi Library layouts and global modules, and the common modules: text, image, button, blurb, call to action, divider, code, video, gallery, sliders and the fullwidth header, testimonial, team member, accordion, toggle, tabs, counters, price tables, social follow, contact form, email opt-in, map, blog and icon. Spacing per screen size, backgrounds with gradients, borders, colours, fonts and alignment are carried. Anything not carried is named once in the import report, never left as shortcode on the page. Five new widgets: Icon, Price table, Team member, Latest posts and Newsletter sign-up; any box or widget may now have a gradient background, a widest width and a place when narrower than its column.
1.1.1 November 18, 2026
Page Builder 1.1.1: its importers that read a WordPress export now name the WordPress plugins they import from, so a site connected through Migrate → “Connect your WordPress” is offered them only when the old site uses one of those plugins. Nothing else changed. Needs Core 0.1.40.
1.1.0 November 17, 2026
Page Builder 1.1.0 (needs Core 0.1.29): pictures in imported layouts are swapped for the copies Core brings over from the old site, whichever is run first; words inside a layout are found by the site's search; and a Shortcode widget holding a Contact Form 7 shortcode becomes a Form widget once that form has been imported.
1.0.1 November 17, 2026
Page Builder 1.0.1: two Tabs widgets holding the same words on one page shared one set of choices, so one of them showed no tab; the same went for two accordions set to open one item at a time. Each widget now has its own. On a phone the list of layouts in the admin was wider than the screen; it now fits. The "Delete layout" button was red words on a red button; it can now be read.
1.0.0 November 17, 2026
Page Builder 1.0.0: replaces Elementor. Sections, columns and nested containers with widths, spacing, alignment and visibility per screen size, and twenty widgets, all drawn as plain HTML and CSS with no script. Layouts are edited with plain forms or written whole through the API. An importer converts pages built with Elementor from a WordPress export, including nested sections, flexbox containers, and global colours and fonts, and names everything it could not carry. Coming from the Hello Elementor theme: use any theme built from the theme kit with this module. The importer's test files are synthetic; it is not yet verified against a live export.
Get Page Builder when WebHD opens
One form on the home page: your WordPress address, then your email.
No card Takes a minute No fake scan