The export converts your saved design into an installable Joomla package. It is launched from your account dashboard, not from the command palette within the editor.
What you will learn
- Properly exit the editor and launch the export from your account.
- Understand the contents of the outer installation ZIP archive.
- Identify bundled versus non-bundled components.
- Prepare the target server environment for installation.
What the export builds
The downloaded file is a Joomla package—an archive capable of installing multiple related extensions in a single operation. Internally, the ZIP contains the main site template itself along with only those Template Architect modules actually utilized by the design. These include the Logo and Slideshow modules; standard Joomla and third-party Phoca Cart modules are not bundled.
The template includes the manifest file, Web Asset Manager file, primary layouts, stylesheets, JavaScript, language files, module chrome, supported overrides, Bootstrap Icons, and safe media placeholders.
Downloading the package
- Wait for the editor to confirm automatic saving and perform a final Preview check.
- Return to your account dashboard listing your custom templates.
- Select the download action next to the target template.
- Wait while the server builds the package archive. Each successful export automatically increments the template version number.
- Save the pkg_….zip file to a secure local directory. Do not extract the outer ZIP archive prior to standard installation via Joomla's Upload Package File interface.
- Document the export version and target testing website where the package will be deployed.
What is intentionally excluded from the ZIP
The export archive does not include local photographs, Pixabay imagery, or other sample design media. These are substituted with bundled placeholder graphics. It also contains no live articles, products, menu items, or component data. Google Fonts are referenced as remote network dependencies rather than bundled local font assets.
The installer script requires PHP 8.2 or higher on the destination server. While the package declares a Joomla manifest version of 6+, deployment on a specific Joomla 5 instance must be tested on a staging copy and cannot be assumed automatically guaranteed.
The ZIP is not complete site content
You are installing layout structures, module positions, and managed module foundations. Final media assets, navigation menus, articles, products, and module assignments must be completed on the target site.
How to handle the file
Keep the outer pkg ZIP intact. Its filename and internal manifest assist Joomla in recognizing the package and its sub-components. Manually re-archiving, renaming internal directories, or attempting to install individual sub-ZIP files directly can bypass required installation sequences and managed module setup routines.
Always archive previous working exports. While newer versions can be uploaded over existing installations, rolling back to an earlier state is safest when restored from a target site backup.