Static exports

Overview

Sometimes, you’ll come across that one client who still wants to host the translations themselves, without depending on any external service. For these cases, we created the ability to export pre-rendered HTMLs or two-column text files with the sources and targets.

Used this way, the proxy and all its capabilities are out of the picture permanently. You can use this for offboarding clients, or as a last resort for delivery (though we really do recommend using the proxy or JavaScript variants).

How it works

When one of these options are selected, the proxy can either dump the project dictionary to a simple text files, from which translations can be copy-pasted to the original CMS, like in ye olden days, or pre-render the translated pages into a ZIP file for rehosting.

When HTML exports are chosen, the proxy will only be able to preprocess pages that are in the current project, and may not include resources (like CSS or JS files), though these will still be referenced from the original domain. The export is then zipped up into an archive for easy download, and can be re-expanded on the original webserver for hosting.

Drawbacks

Static exports are, as the name implies, static - after creating one, they will never ever change nor update. Therefore, these are unsuitable for maintaining an active website that’s being updated with new content. Their main purpose is to provide an avenue to offboard clients or appease content owners who want to maintain full control of the translations, to an even greater degree than what JavaScript permits, and prefer hosting the pages themselves.