Export and publishing model

What export includes

• page structure and navigation
• styles and interaction scripts
• embedded images and document assets
• reading interface behavior needed for the final reading experience

Why the single-file format matters

A single HTML output is easier to upload to static hosting, attach to a release package, or share directly without dependency on an extra asset directory.

It also reduces the number of deployment steps when the published version must stay synchronized with a specific release or product build.

Common hosting patterns

• upload the file to static hosting or object storage
• publish it under a support or docs subdomain
• bundle it with software releases or downloadable archives
• send it directly when the recipient needs an offline-capable copy

Operational notes

If you publish multiple versions, keep a versioned naming convention and a stable public index page.

When teams need a public documentation hub, link the latest export from a visible route like this online help section.