Download your publication as ZIP
A publication set up with Maglr is hosted by default on the servers of the Maglr platform. During construction, you upload the various assets and merge them into an interactive project. With an annual license it is possible to download and host these publications yourself. For this we offer different export options, depending on how you want to use the publication.
If you run an annual Maglr license, you will see the option to download the project in the project settings. Export to ZIP is only possible for projects of the type Publication or Micro content.
Note: this function is only available for users with a 1) annual Business license, 2) Pro or 3) Enterprise license.
During the publishing process, the pages designed in the editors are converted to web pages (HTML / JS). These are bundled in a folder with the appropriately reduced images, sound clips or videos.
We can offer these bundled files in different versions:
A version of the project that can be used without a web server. This means that the files can be started locally. Think of a folder on your desktop, USB stick, dropbox folder or intranet share. Opening the index.html file starts the publication, after which the pages can be browsed.
Works locally without a web server
No dynamic loading
Simple URLs with IDs
If you have access to a web server, we offer a version of the project which you can upload to your own FTP environment. Pages are loaded dynamically and the URLs are translated to the correct page based on a URL rewrite configuration. Using this technique, you use the same URLs as specified in Maglr. For each page within the publication, a separate static HTML page is prepared.
When SEO is important, render pages including all meta data
URLs with the structure /project/page.html
Subpages can be accessed directly from the above URL
Analytics or GTM also published in code
The most extensive version contains pre-rendering and the same URL structure as the online version, including URL forwards. Suppose you update a project and change the URL of a page, this export remembers all URLs and know to forward any old links, which may have been indexed in Google, to the new pages.
This variant only runs on web servers that support a .htaccess configuration. This part is necessary for the URL rewrites.
Same URLs to the online version /project/page-name
Possible to navigate directly with URL to subpage
History of older URLs with redirect to new page
Sitemap.xml for search engines
Robots.txt for search engines
For customers using our Maglr Enterprise license we offer an implementation where it's possible to directly publish changes through our dashboard to your own (local) webserver. Click here for more information about this option.
If you run an annual Maglr license, you will see the option to download the project in the project settings. Export to ZIP is only possible for projects of the type Publication or Micro content.
Note: this function is only available for users with a 1) annual Business license, 2) Pro or 3) Enterprise license.
During the publishing process, the pages designed in the editors are converted to web pages (HTML / JS). These are bundled in a folder with the appropriately reduced images, sound clips or videos.
ZIP export options
We can offer these bundled files in different versions:
Local use
A version of the project that can be used without a web server. This means that the files can be started locally. Think of a folder on your desktop, USB stick, dropbox folder or intranet share. Opening the index.html file starts the publication, after which the pages can be browsed.
Works locally without a web server
No dynamic loading
Simple URLs with IDs
Server usage (including pre-rendering)
If you have access to a web server, we offer a version of the project which you can upload to your own FTP environment. Pages are loaded dynamically and the URLs are translated to the correct page based on a URL rewrite configuration. Using this technique, you use the same URLs as specified in Maglr. For each page within the publication, a separate static HTML page is prepared.
When SEO is important, render pages including all meta data
URLs with the structure /project/page.html
Subpages can be accessed directly from the above URL
Analytics or GTM also published in code
Server usage (pre-rendering and extended URLs)
The most extensive version contains pre-rendering and the same URL structure as the online version, including URL forwards. Suppose you update a project and change the URL of a page, this export remembers all URLs and know to forward any old links, which may have been indexed in Google, to the new pages.
This variant only runs on web servers that support a .htaccess configuration. This part is necessary for the URL rewrites.
Same URLs to the online version /project/page-name
Possible to navigate directly with URL to subpage
History of older URLs with redirect to new page
Sitemap.xml for search engines
Robots.txt for search engines
Sync directly to FTP
For customers using our Maglr Enterprise license we offer an implementation where it's possible to directly publish changes through our dashboard to your own (local) webserver. Click here for more information about this option.
Updated on: 08/02/2023