Native core, visual editing
How JM Builder works
A visual editing layer for pages, posts, and the Site Editor, built on Gutenberg blocks. The layouts you build are stored as native block markup and template imports bring a whole site across.
Native block engine
Every layout component is stored as Gutenberg markup
Visual editing
The Elementor-familiar interface
Edit pages, posts, and the Site Editor through a visual interface inside the WordPress admin. The controls are built for people who prefer a visual workflow over raw block settings.
Layouts that persist
Native markup keeps layouts in place
Every component is saved as standard Gutenberg block markup in the database. If JM Builder is deactivated, the layout, styling, and content remain intact because they never depended on a proprietary format.
Front-end footprint
A small, documented public footprint
The public site uses native blocks. The plugin adds one inline footer script that toggles the scrolled class on the html element. When no other plugin has printed them, it also adds the document title, an excerpt-based meta description, and social sharing tags.
Tools → Import Template
Mirror a source site from a JM Template Exporter ZIP
01
Export the source site
Create a ZIP with JM Template Exporter. It packages the theme or child theme, templates, header and footer, navigations, colors and styles, content, and media.
02
Upload under Tools → Import Template
Open Tools → Import Template in WordPress and upload the ZIP. The import mirrors the source site’s structure, styling, and content into this installation.
03
Review what came across
Check the theme, templates, navigation, styles, content, and media. Plugins are excluded from the import, so install and activate any plugins the source site relied on.