Generate a local, diagnostic Elementor Core Atomic package from a website project, inspect its coverage and required runtime work, and understand why it is not yet an installable or published conversion.
Where: Flowmo AI Assistant → Elementor/CMS tools, from an open website project. — Request an experimental local Atomic export.
Before you start
- Requires the desktop app’s local artifact support and code-download entitlement.
- Choose installed-schema only when the project is connected to a matched WordPress site with the Flowmo Atomic companion; pinned-source is available for offline profile-based research.
- This export is experimental. It does not install, import, publish, or edit WordPress; installReady is always false.
Key ideas
- Two capability profiles: pinned-source compiles against the exporter’s pinned offline contract. installed-schema first reads and verifies the connected site’s Atomic capability profile through the companion. The installed profile improves schema alignment but does not certify that the result is ready to import.
- Editable candidates plus explicit gaps: The local package includes native structure/style candidates, original source, runtime definitions, CSS, dependencies, coverage, source mapping, and diagnostics. Unsupported interactions, runtime mounting, CMS bindings, media remapping, or frontend validation remain explicit required-work gates.
- Local artifact only: The result is saved locally in desktop Downloads with a validation report. It reports experimental:true, installReady:false, changed:false, and deployed:false. It never writes the connected WordPress site or changes the project output type.
- Do not confuse this with the older Elementor output path: The Atomic compiler is a separate experimental exporter; it is not a promise that every f0 page, interaction, CMS binding, or script becomes native Elementor content. Inspect the actual coverage and issues in each generated report.
Steps
- Open the website project to export and confirm that the right source pages and CMS state are selected.
- Choose export_elementor_atomic with capability_profile set to pinned-source for offline exploration or installed-schema for a matched connected site.
- Optionally pass page_ids to restrict rendered documents, or namespace to choose the generated package namespace.
- Review the local artifact paths, coverage, errors, warnings, and requiredRuntimeWork. Do not assume that a generated structure candidate is a finished native widget.
- Keep installReady:false as the release gate: the current tool does not install/import or publish the artifact. Validate changes in a separate nonproduction workflow only when the required runtime and compatibility work is complete.
- For an existing WordPress-target project package, use validate_wordpress_export to create a local ZIP/extracted package and validation report; that tool also does not publish or push content.
Current workflow boundary
For a conventional WordPress output project, validate the existing package locally with validate_wordpress_export. For Atomic experimentation, use export_elementor_atomic, inspect the saved report and requiredRuntimeWork, and treat the artifact as a development handoff—not a release or deployment package.