Elementor Template Kits
Use this skill when creating Elementor template kits, debugging why a kit ZIP
fails to import, or migrating an existing site design into Elementor Pro.
All format contracts in this skill were verified against source:
- Envato
common-repository/template-kit-import → vendor/template-kit-import/inc/
(class-importer.php, class-builder.php, class-builder-elementor.php,
class-required-plugin.php)
- Elementor
elementor/elementor → app/modules/import-export/** (processes,
runners, compatibility/envato.php), core/base/document.php,
includes/template-library/sources/{local,base}.php,
includes/template-library/classes/class-import-images.php,
includes/controls/media.php
Re-verify against those files when a format breaks after a plugin update.
For connecting an NV oOS assistant to a live Elementor MCP server (editing
pages at runtime instead of importing kits), see
design-elementor-mcp-connection — kits are offline imports; MCP Apps are
live tool bridges.
When to use this skill
Trigger when ANY of the following is true:
- Building or exporting an Elementor template kit (for the Envato Template Kit
Import plugin, Elementor's Import Kit tool, or a custom import tool).
- A kit ZIP fails to import, imports nothing, or shows "This kit is in the
newer 'Elementor Kit' format".
- Images in imported templates are broken or replaced with placeholders.
- The task mentions "template kit", "kit zip", "Envato kit", "Elementor kit
import", "manifest_version", or "templates[] manifest".
- Migrating an existing site (React, HTML, another builder) into Elementor Pro.
The three import pipelines — never mix their formats
| Pipeline |
Format key |
Manifest shape |
Template file shape |
| Envato Template Kit Import plugin |
manifest_version + page_builder (NO version key) |
templates[] list with name/type/source/metadata.template_type |
Elementor library JSON {content, page_settings, type, title, version} |
| Elementor native Import Kit tool |
none needed (version: "2.0" written by exporter) |
content.<post_type>.<id> + templates.<id> maps with doc_type |
{content, settings, metadata} |
Custom import tools (e.g. NV oOS import_elementor_template_kit) |
tool-specific |
tool-specific |
bare array of elements stored verbatim as _elementor_data |
Elementor's native import tool contains an Envato compatibility adapter
(compatibility/envato.php, triggered by manifest_version), so a correct
Envato-format ZIP imports through BOTH the Envato plugin and Elementor's own
tool. Prefer the Envato format unless the goal is real page creation with
front-page assignment (native) or verbatim meta injection (custom tool).
Envato kit contract
manifest.json at ZIP root (the plugin scans the extraction root for it):
{
"manifest_version": "1.0.0",
"page_builder": "elementor",
"title": "Kit Name",
"name": "Kit Name",
"templates": [
{
"name": "Home",
"type": "page",
"source": "templates/home.json",
"screenshot": "media/thumb.jpg",
"thumbnail": "",
"metadata": { "template_type": "single-home" }
},
{
"name": "Site Header",
"type": "header",
"source": "templates/site-header.json",
"thumbnail": "",
"elementor_pro_required": true,
"metadata": { "template_type": "section-header", "elementor_pro_required": true }
},
{
"name": "Kit Styles",
"type": "kit",
"source": "templates/global.json",
"thumbnail": "",
"metadata": { "template_type": "global-styles" }
}
],
"required_plugins": [
{ "name": "Elementor", "file": "elementor/elementor.php", "min_version": "3.25.0" },
{ "name": "Elementor Pro", "file": "elementor-pro/elementor-pro.php" }
],
"required_css": [
{ "name": "Design System", "file": "assets/kit.css", "description": "..." }
]
}
Rules:
version key is poison. Importer::install_template_kit_zip_to_db
checks ! empty( $manifest_data['version'] ) AFTER the manifest_version
check and overwrites the builder type to "elementor-kit" — the kit is then
refused with the "newer Elementor Kit" message. Envato manifests must never
contain version.
metadata.template_type values the UI groups on: single-page,
single-home, landing-page, single-post, single-404,
archive-*, section-header, section-footer, section-popup,
section-* (hero/about/faq/contact/cta/...), global-styles.
elementor_pro_required: true goes BOTH at the top level of the manifest
template entry (the UI checks $template['elementor_pro_required']) and in
the file's metadata (the importer checks
$local_json_data['metadata']['elementor_pro_required'] to downgrade the
type to page when Pro is absent).
- The first template's
screenshot becomes the kit-level thumbnail.
required_plugins entries need file (e.g. elementor/elementor.php) and
optional min_version; required_css entries need file (path in ZIP).
global.json (metadata.template_type: "global-styles") carries the kit
site settings in page_settings; the plugin sets _elementor_template_type: kit and elementor_active_kit after importing it.
- ZIP may only contain extensions
json, jpg, png, css, html — the
plugin filters every entry by extension before extracting.
Template files (Envato) are Elementor library JSON — include BOTH
page_settings (Envato plugin path via Source_Local::import_template) and
settings (Elementor native path via Document::import, which reads only
settings), so the same file works in both pipelines:
{
"content": [ ...elements... ],
"page_settings": { "hide_title": "yes" },
"settings": { "hide_title": "yes" },
"version": "0.4",
"title": "Home",
"type": "page",
"metadata": { "template_type": "single-home" }
}
type values: page, header, footer, popup, section, container,
kit (global styles file). Extra keys are ignored by both importers.
Elementor native kit contract
ZIP layout (JSON files ONLY — the extractor is called with
[ 'json', 'xml' ]):
manifest.json
site-settings.json
content/page/<id>.json (one per post, id = manifest key)
templates/<template-id>.json (Theme Builder parts; manifest key = basename)
manifest.json (import side reads title/name for the session, content
and templates maps, plugins):
{
"name": "kit-slug",
"title": "Kit Name",
"description": "...",
"version": "2.0",
"content": {
"page": {
"home": { "title": "Home", "doc_type": "wp-page", "show_on_front": true, "thumbnail": "" },
"about": { "title": "About", "doc_type": "wp-page", "show_on_front": false, "thumbnail": "" }
}
},
"templates": {
"site-header": { "title": "Site Header", "doc_type": "header", "thumbnail": "" },
"site-footer": { "title": "Site Footer", "doc_type": "footer", "thumbnail": "" },
"site-mobile-menu": { "title": "Mobile Menu Popup", "doc_type": "popup", "thumbnail": "" }
},
"plugins": []
}
Rules:
- Every content/template manifest entry needs a
thumbnail key (even empty) —
Document::import() reads $data['import_settings']['thumbnail'] directly
and PHP 8 warns on missing keys.
doc_type: wp-page for WP pages under content.page; header, footer,
popup (Pro) for templates.
- The
templates runner only runs when Utils::has_pro() — header/footer/
popup parts need Elementor Pro.
- Set
plugins: []. The Plugins runner installs/activates every entry from
wp.org — Elementor Pro is NOT hosted there, so listing it produces a failed
install; an empty array skips the runner entirely.
- Do NOT put a
theme object in site-settings.json unless you want the
import to download and SWITCH the active theme. Omit it; recommend Hello
Elementor in docs instead.
site-settings.json (Site_Settings runner requires non-empty settings):
{
"settings": {
"custom_colors": [
{ "_id": "ink", "title": "Ink", "color": "#252522" }
],
"custom_typography": [
{
"_id": "primary",
"title": "Primary",
"typography_typography": "custom",
"typography_font_family": "Manrope",
"typography_font_weight": "400",
"typography_line_height": { "unit": "em", "size": 1.6, "sizes": [] }
}
],
"space_between_widgets": { "column": "24", "row": "0", "isLinked": false, "unit": "px" }
}
}
Kit typography repeaters have NO typography_font_size (size is per-widget);
include family/weight/transform/decoration/style/line-height/letter-spacing/
word-spacing. space_between_widgets must use column/row/isLinked.
Document files (content/** and templates/**) use
{ "content": [...], "settings": {...}, "metadata": {} } — exactly
Document::get_export_data()'s shape. Document::import() reads content
and settings (NOT page_settings), then saves any metadata keys as post
meta.
Images — the #1 kit-breaking issue
Elementor runs on_import on every media control during any import.
Control_Media::on_import → Import_Images::import → wp_safe_remote_get:
- Absolute URLs are downloaded into the Media Library, the attachment id
is set, and the URL is replaced with the local one. This is the intended
flow (how Envato kits work) and needs a publicly reachable URL at import time.
- Relative URLs (
/wp-content/uploads/...) fail wp_http_validate_url →
the image is replaced with Elementor's placeholder. Kit images "break".
Strategy:
- Keep relative URLs in formats stored verbatim (custom tools that write
_elementor_data without on_import processing — those survive).
- For Envato/native formats, make image URLs absolute and point them at a
location that resolves during import — typically the target site itself
after pre-uploading media to the referenced path (e.g.
https://site.com/wp-content/uploads/sascha/x.jpg).
- Parametrize the generator with a
--media-base flag and print a warning
when it is missing.
Media_Mapper (transient elementor_media_mapping + a
media-mapping.json media ZIP) only exists in the Kit Library flow — a
locally uploaded ZIP does NOT get media mapping, so do not rely on it.
Element/document rules
- Flexbox-first:
elType: "container" roots, widgets with widgetType
(heading, text-editor, image, button, icon-list, nav-menu).
Layout in Elementor settings; typography/character in a companion CSS file
under a .kit-name scope class.
- Element
ids must be unique within a file; any string works (c_001).
Source_Local replaces ids on import anyway.
- Page setting
hide_title: "yes" suppresses the theme title.
- The Pro
nav-menu widget needs menu: "" plus a manual WP menu assignment
after import — menu data is site-specific, not template data.
- Popup
page_settings (width/height/position/entrance_animation/
exit_animation/overlay_background_color/prevent_scroll/triggers/timing) ride
along as document settings; the click trigger on a custom selector
(.mobile-menu-toggle) may need re-saving in Popup Settings after import.
elementor_pro_conditions (array of type/name/sub_name/sub_id strings in
file metadata) is understood by the Envato adapter, but instructing users
to set display conditions manually is more reliable.
Packaging and verification
- Write Zips with a dependency-free Node writer (deflate + CRC-32, UTF-8 flag
bit 0x0800, forward-slash names, no directory entries). See
elementor-kit/scripts/lib/zip.mjs in this project for the implementation.
manifest.json must sit at the ZIP root for the Envato plugin.
- Verify with an independent parser before shipping:
python -c "import zipfile; z=zipfile.ZipFile('kit.zip'); print(z.testzip()); print(z.namelist())"
- Validate generated JSON: manifests parse, every
source/content/templates
reference resolves to a file, element ids unique per file, Envato manifest
has manifest_version + page_builder + title and NO version.
This project's tooling
The Sascha Torres kit generator demonstrates all three formats from one set of
page definitions (elementor-kit/scripts/):
generate-kit.mjs — element builders (container, row, heading,
text, image, button, eyebrow, editorialList, numberedList,
section, splitHero, siteHeader, siteFooter, siteMobileMenu),
exported pages map and PAGE_TITLES; writes the custom-tool format
(bare element arrays) + its manifest.
generate-formats.mjs — imports those builders and emits dist/native/,
dist/envato/, dist/plugin/ plus the three ZIPs; --media-base= rewrites
/wp-content/uploads/ URLs to absolute for envato/native; self-validates.
lib/zip.mjs — dependency-free ZIP writer.
validate-kit.mjs — validates the custom-tool format.
Commands:
node elementor-kit/scripts/generate-kit.mjs
node elementor-kit/scripts/validate-kit.mjs
node elementor-kit/scripts/generate-formats.mjs
node elementor-kit/scripts/generate-formats.mjs --media-base=https://your-site.com
Reuse this structure when building kits for other sites: keep page
definitions in one file, generate each format separately, never share a
manifest between formats.
Post-import checklist to hand to the user
- Install the kit CSS (Envato: accept
required_css into the Customizer;
native: copy into Elementor → Site Settings → Custom CSS).
- Upload media to the referenced uploads path BEFORE importing envato/native
zips (see Images above).
- Set header/footer display conditions (Entire Site) in Theme Builder.
- Create the WP menu and assign it in the nav-menu widget.
- Re-save popup trigger + set popup display conditions.
- Swap static contact forms for Elementor Pro Forms (or another form system).
1---2type: Skill3name: design-elementor-template-kits4description: Designs, generates, and packages Elementor template kits that import correctly — Envato Template Kit Import format, Elementor's native Kit format, and raw _elementor_data formats. Use when building/exporting template kits, fixing kit import errors ("newer Elementor Kit" warning, "nothing imports", broken images after import), migrating a site design into Elementor Pro, or packaging zips for any Elementor import pipeline. Covers verified manifest schemas, doc_type/template_type values, image URL sideloading rules, zip packaging constraints, and kit site-settings.5license: Proprietary. See LICENSE.txt6metadata:7 source: https://skillmd.com/skills/nvdigitalsolutions/design-elementor-template-kits8 type: Skill9---1011# Elementor Template Kits1213Use this skill when creating Elementor template kits, debugging why a kit ZIP14fails to import, or migrating an existing site design into Elementor Pro.1516All format contracts in this skill were verified against source:1718- Envato `common-repository/template-kit-import` → `vendor/template-kit-import/inc/`19 (`class-importer.php`, `class-builder.php`, `class-builder-elementor.php`,20 `class-required-plugin.php`)21- Elementor `elementor/elementor` → `app/modules/import-export/**` (processes,22 runners, `compatibility/envato.php`), `core/base/document.php`,23 `includes/template-library/sources/{local,base}.php`,24 `includes/template-library/classes/class-import-images.php`,25 `includes/controls/media.php`2627Re-verify against those files when a format breaks after a plugin update.2829For connecting an NV oOS assistant to a live Elementor MCP server (editing30pages at runtime instead of importing kits), see31`design-elementor-mcp-connection` — kits are offline imports; MCP Apps are32live tool bridges.3334## When to use this skill3536Trigger when ANY of the following is true:3738- Building or exporting an Elementor template kit (for the Envato Template Kit39 Import plugin, Elementor's Import Kit tool, or a custom import tool).40- A kit ZIP fails to import, imports nothing, or shows "This kit is in the41 newer 'Elementor Kit' format".42- Images in imported templates are broken or replaced with placeholders.43- The task mentions "template kit", "kit zip", "Envato kit", "Elementor kit44 import", "manifest_version", or "templates[] manifest".45- Migrating an existing site (React, HTML, another builder) into Elementor Pro.4647## The three import pipelines — never mix their formats4849| Pipeline | Format key | Manifest shape | Template file shape |50|---|---|---|---|51| Envato Template Kit Import plugin | `manifest_version` + `page_builder` (NO `version` key) | `templates[]` list with `name`/`type`/`source`/`metadata.template_type` | Elementor library JSON `{content, page_settings, type, title, version}` |52| Elementor native Import Kit tool | none needed (`version: "2.0"` written by exporter) | `content.<post_type>.<id>` + `templates.<id>` maps with `doc_type` | `{content, settings, metadata}` |53| Custom import tools (e.g. NV oOS `import_elementor_template_kit`) | tool-specific | tool-specific | bare **array** of elements stored verbatim as `_elementor_data` |5455Elementor's native import tool contains an **Envato compatibility adapter**56(`compatibility/envato.php`, triggered by `manifest_version`), so a correct57Envato-format ZIP imports through BOTH the Envato plugin and Elementor's own58tool. Prefer the Envato format unless the goal is real page creation with59front-page assignment (native) or verbatim meta injection (custom tool).6061## Envato kit contract6263`manifest.json` at ZIP root (the plugin scans the extraction root for it):6465```json66{67 "manifest_version": "1.0.0",68 "page_builder": "elementor",69 "title": "Kit Name",70 "name": "Kit Name",71 "templates": [72 {73 "name": "Home",74 "type": "page",75 "source": "templates/home.json",76 "screenshot": "media/thumb.jpg",77 "thumbnail": "",78 "metadata": { "template_type": "single-home" }79 },80 {81 "name": "Site Header",82 "type": "header",83 "source": "templates/site-header.json",84 "thumbnail": "",85 "elementor_pro_required": true,86 "metadata": { "template_type": "section-header", "elementor_pro_required": true }87 },88 {89 "name": "Kit Styles",90 "type": "kit",91 "source": "templates/global.json",92 "thumbnail": "",93 "metadata": { "template_type": "global-styles" }94 }95 ],96 "required_plugins": [97 { "name": "Elementor", "file": "elementor/elementor.php", "min_version": "3.25.0" },98 { "name": "Elementor Pro", "file": "elementor-pro/elementor-pro.php" }99 ],100 "required_css": [101 { "name": "Design System", "file": "assets/kit.css", "description": "..." }102 ]103}104```105106Rules:107108- **`version` key is poison.** `Importer::install_template_kit_zip_to_db`109 checks `! empty( $manifest_data['version'] )` AFTER the `manifest_version`110 check and overwrites the builder type to "elementor-kit" — the kit is then111 refused with the "newer Elementor Kit" message. Envato manifests must never112 contain `version`.113- `metadata.template_type` values the UI groups on: `single-page`,114 `single-home`, `landing-page`, `single-post`, `single-404`,115 `archive-*`, `section-header`, `section-footer`, `section-popup`,116 `section-*` (hero/about/faq/contact/cta/...), `global-styles`.117- `elementor_pro_required: true` goes BOTH at the top level of the manifest118 template entry (the UI checks `$template['elementor_pro_required']`) and in119 the file's `metadata` (the importer checks120 `$local_json_data['metadata']['elementor_pro_required']` to downgrade the121 type to `page` when Pro is absent).122- The first template's `screenshot` becomes the kit-level thumbnail.123- `required_plugins` entries need `file` (e.g. `elementor/elementor.php`) and124 optional `min_version`; `required_css` entries need `file` (path in ZIP).125- `global.json` (`metadata.template_type: "global-styles"`) carries the kit126 site settings in `page_settings`; the plugin sets `_elementor_template_type:127 kit` and `elementor_active_kit` after importing it.128- ZIP may only contain extensions `json`, `jpg`, `png`, `css`, `html` — the129 plugin filters every entry by extension before extracting.130131Template files (Envato) are Elementor library JSON — include BOTH132`page_settings` (Envato plugin path via `Source_Local::import_template`) and133`settings` (Elementor native path via `Document::import`, which reads only134`settings`), so the same file works in both pipelines:135136```json137{138 "content": [ ...elements... ],139 "page_settings": { "hide_title": "yes" },140 "settings": { "hide_title": "yes" },141 "version": "0.4",142 "title": "Home",143 "type": "page",144 "metadata": { "template_type": "single-home" }145}146```147148`type` values: `page`, `header`, `footer`, `popup`, `section`, `container`,149`kit` (global styles file). Extra keys are ignored by both importers.150151## Elementor native kit contract152153ZIP layout (JSON files ONLY — the extractor is called with154`[ 'json', 'xml' ]`):155156```157manifest.json158site-settings.json159content/page/<id>.json (one per post, id = manifest key)160templates/<template-id>.json (Theme Builder parts; manifest key = basename)161```162163`manifest.json` (import side reads `title`/`name` for the session, `content`164and `templates` maps, `plugins`):165166```json167{168 "name": "kit-slug",169 "title": "Kit Name",170 "description": "...",171 "version": "2.0",172 "content": {173 "page": {174 "home": { "title": "Home", "doc_type": "wp-page", "show_on_front": true, "thumbnail": "" },175 "about": { "title": "About", "doc_type": "wp-page", "show_on_front": false, "thumbnail": "" }176 }177 },178 "templates": {179 "site-header": { "title": "Site Header", "doc_type": "header", "thumbnail": "" },180 "site-footer": { "title": "Site Footer", "doc_type": "footer", "thumbnail": "" },181 "site-mobile-menu": { "title": "Mobile Menu Popup", "doc_type": "popup", "thumbnail": "" }182 },183 "plugins": []184}185```186187Rules:188189- Every content/template manifest entry needs a `thumbnail` key (even empty) —190 `Document::import()` reads `$data['import_settings']['thumbnail']` directly191 and PHP 8 warns on missing keys.192- `doc_type`: `wp-page` for WP pages under `content.page`; `header`, `footer`,193 `popup` (Pro) for `templates`.194- The `templates` runner only runs when `Utils::has_pro()` — header/footer/195 popup parts need Elementor Pro.196- Set `plugins: []`. The Plugins runner installs/activates every entry from197 wp.org — Elementor Pro is NOT hosted there, so listing it produces a failed198 install; an empty array skips the runner entirely.199- Do NOT put a `theme` object in `site-settings.json` unless you want the200 import to download and SWITCH the active theme. Omit it; recommend Hello201 Elementor in docs instead.202203`site-settings.json` (Site_Settings runner requires non-empty `settings`):204205```json206{207 "settings": {208 "custom_colors": [209 { "_id": "ink", "title": "Ink", "color": "#252522" }210 ],211 "custom_typography": [212 {213 "_id": "primary",214 "title": "Primary",215 "typography_typography": "custom",216 "typography_font_family": "Manrope",217 "typography_font_weight": "400",218 "typography_line_height": { "unit": "em", "size": 1.6, "sizes": [] }219 }220 ],221 "space_between_widgets": { "column": "24", "row": "0", "isLinked": false, "unit": "px" }222 }223}224```225226Kit typography repeaters have NO `typography_font_size` (size is per-widget);227include family/weight/transform/decoration/style/line-height/letter-spacing/228word-spacing. `space_between_widgets` must use `column`/`row`/`isLinked`.229230Document files (`content/**` and `templates/**`) use231`{ "content": [...], "settings": {...}, "metadata": {} }` — exactly232`Document::get_export_data()`'s shape. `Document::import()` reads `content`233and `settings` (NOT `page_settings`), then saves any `metadata` keys as post234meta.235236## Images — the #1 kit-breaking issue237238Elementor runs `on_import` on every media control during any import.239`Control_Media::on_import` → `Import_Images::import` → `wp_safe_remote_get`:240241- **Absolute URLs** are downloaded into the Media Library, the attachment id242 is set, and the URL is replaced with the local one. This is the intended243 flow (how Envato kits work) and needs a publicly reachable URL at import time.244- **Relative URLs** (`/wp-content/uploads/...`) fail `wp_http_validate_url` →245 the image is replaced with Elementor's placeholder. Kit images "break".246247Strategy:2482491. Keep relative URLs in formats stored verbatim (custom tools that write250 `_elementor_data` without `on_import` processing — those survive).2512. For Envato/native formats, make image URLs absolute and point them at a252 location that resolves during import — typically the target site itself253 after pre-uploading media to the referenced path (e.g.254 `https://site.com/wp-content/uploads/sascha/x.jpg`).2553. Parametrize the generator with a `--media-base` flag and print a warning256 when it is missing.2574. `Media_Mapper` (transient `elementor_media_mapping` + a258 `media-mapping.json` media ZIP) only exists in the Kit Library flow — a259 locally uploaded ZIP does NOT get media mapping, so do not rely on it.260261## Element/document rules262263- Flexbox-first: `elType: "container"` roots, widgets with `widgetType`264 (`heading`, `text-editor`, `image`, `button`, `icon-list`, `nav-menu`).265 Layout in Elementor settings; typography/character in a companion CSS file266 under a `.kit-name` scope class.267- Element `id`s must be unique within a file; any string works (`c_001`).268 `Source_Local` replaces ids on import anyway.269- Page setting `hide_title: "yes"` suppresses the theme title.270- The Pro `nav-menu` widget needs `menu: ""` plus a manual WP menu assignment271 after import — menu data is site-specific, not template data.272- Popup `page_settings` (width/height/position/entrance_animation/273 exit_animation/overlay_background_color/prevent_scroll/triggers/timing) ride274 along as document settings; the click trigger on a custom selector275 (`.mobile-menu-toggle`) may need re-saving in Popup Settings after import.276- `elementor_pro_conditions` (array of `type/name/sub_name/sub_id` strings in277 file `metadata`) is understood by the Envato adapter, but instructing users278 to set display conditions manually is more reliable.279280## Packaging and verification281282- Write Zips with a dependency-free Node writer (deflate + CRC-32, UTF-8 flag283 bit 0x0800, forward-slash names, no directory entries). See284 `elementor-kit/scripts/lib/zip.mjs` in this project for the implementation.285- `manifest.json` must sit at the ZIP root for the Envato plugin.286- Verify with an independent parser before shipping:287 `python -c "import zipfile; z=zipfile.ZipFile('kit.zip'); print(z.testzip()); print(z.namelist())"`288- Validate generated JSON: manifests parse, every `source`/`content`/`templates`289 reference resolves to a file, element ids unique per file, Envato manifest290 has `manifest_version` + `page_builder` + `title` and NO `version`.291292## This project's tooling293294The Sascha Torres kit generator demonstrates all three formats from one set of295page definitions (`elementor-kit/scripts/`):296297- `generate-kit.mjs` — element builders (`container`, `row`, `heading`,298 `text`, `image`, `button`, `eyebrow`, `editorialList`, `numberedList`,299 `section`, `splitHero`, `siteHeader`, `siteFooter`, `siteMobileMenu`),300 exported `pages` map and `PAGE_TITLES`; writes the custom-tool format301 (bare element arrays) + its manifest.302- `generate-formats.mjs` — imports those builders and emits `dist/native/`,303 `dist/envato/`, `dist/plugin/` plus the three ZIPs; `--media-base=` rewrites304 `/wp-content/uploads/` URLs to absolute for envato/native; self-validates.305- `lib/zip.mjs` — dependency-free ZIP writer.306- `validate-kit.mjs` — validates the custom-tool format.307308Commands:309310```bash311node elementor-kit/scripts/generate-kit.mjs312node elementor-kit/scripts/validate-kit.mjs313node elementor-kit/scripts/generate-formats.mjs314node elementor-kit/scripts/generate-formats.mjs --media-base=https://your-site.com315```316317Reuse this structure when building kits for other sites: keep page318definitions in one file, generate each format separately, never share a319manifest between formats.320321## Post-import checklist to hand to the user3223231. Install the kit CSS (Envato: accept `required_css` into the Customizer;324 native: copy into Elementor → Site Settings → Custom CSS).3252. Upload media to the referenced uploads path BEFORE importing envato/native326 zips (see Images above).3273. Set header/footer display conditions (Entire Site) in Theme Builder.3284. Create the WP menu and assign it in the nav-menu widget.3295. Re-save popup trigger + set popup display conditions.3306. Swap static contact forms for Elementor Pro Forms (or another form system).