Export

Route/authoring/slate/export PreviewSlate previewslate

Export Site — "Build and download site · N pages" — packages the portal as a static ZIP: "The ZIP is built and downloaded locally from the current catalog." Without a scope: "Choose a project and version to build and export its generated portal."

Deployment target

ZIP Bundle — "Self-contained static files, no runtime required. Suitable for partner packages and air-gapped environments." — is the target available today. GitHub Pages, Amazon S3 and CDN Push are listed and disabled: "Hosted deploy targets arrive with Slate 9.3."

Options

All on by default: the Try-it-live console, the Full-text search index (assets/search-index.js), Include all code language tabs (curl, Python, JavaScript, Go, Java) and Minify HTML/CSS/JS. The API base URL field sets the address the try-it console and samples point at; blank means https://api.example.com.

Build & Download ZIP shows the estimated build time and output, then downloads <slug>.zip, which includes build-manifest.json and a robots.txt that follows the site's indexing setting.

Access control and a ZIP

The page reads the site's access policy and, when the site is gated, says so: "A downloaded ZIP is a folder of files: it carries the robots.txt chosen here, but nothing in a static archive can refuse a request, so whoever hosts it owns the gate." The gate is enforced only on the hosted site.

Empty states: "No pages yet. Document paths in the catalog to build an exportable site." and the catalog error. The export uses the default theme and the options last for the session.