Exports and wiki packs, in the code

Exports are photographs

An HTML or PDF export, and every page of an exported website, is captured rather than rebuilt: the app asks the pdf service’s browser to open the page as a reader would and save what it shows. So an export looks exactly like the page, live content included, and a new kind of block needs no export code of its own.

The browser signs in with a render token: made for that export, valid for fifteen minutes, and good only for the one page (or the one space, for a website) being exported. It carries the exporter’s permissions, or none at all for a public website, which is why a website exported as the public sees it cannot contain anything private.

Wiki packs are the documents

A wiki pack is the opposite: not a picture of the space but the space itself, as readable JSON files in a zip, with every version, comment, label, template and attachment, so another Tesria can read it back. See Wiki packs.

• A format number, checked first. Adding an optional field leaves it alone; changing what a field means raises it. A pack from a newer format is refused with a message naming the Tesria that made it.

• Older packs are upgraded before they are read, one format at a time, the way a database is migrated. A pack made by Tesria 0.5 or later imports into every later version, and the tests import one made by each release that changed the format.

• Untrusted until proven otherwise. A pack is an upload from somewhere else, so its size, its number of files and every file name are checked before anything in it is used, and imported pages are rebuilt from their content rather than trusted.