# Xyvenra Cloud static-site ZIP import

Xyvenra Cloud by Ouroboros can import the **built output** of a small static site from a ZIP file. It does not install dependencies or run a build. Put `index.html` at the ZIP root or inside one project folder. A site can contain up to 10 HTML pages linked from that entry page.

## Limits and supported files

- ZIP upload: at most 12 MB compressed, 100 entries, and 8 MB expanded.
- Result: one self-contained Cloud document holding up to 10 linked HTML pages, at most 180,000 UTF-8 bytes in total.
- Relative CSS stylesheets and nested CSS `@import` files are inlined; local `url(...)` assets are embedded.
- Relative classic JavaScript files (`<script src>` without `type="module"`) are inlined.
- Referenced local image, font, audio, video, and other static resources are embedded as data URLs.
- Local links between included HTML pages switch pages inside the same sandboxed document. They use a reserved `#xyvenra-page=` hash route; they do not become separate server paths. Normal in-page anchor links such as `#contact` keep working after switching pages, and links such as `about.html#team` switch pages and scroll to the matching section.
- Missing referenced CSS, script, or supported asset files, path traversal, unsupported compression, encrypted archives, and oversized pages are rejected before the imported HTML is offered to the editor.

This is a static-site import, not a general deployment build. JavaScript module bundles, server-rendered routes, server code, build steps, and dynamic relative fetches are not supported. Local page links that do not resolve to an included HTML page are changed to `#`; external links remain links. A build that depends on unsupported features needs to be simplified or bundled as a self-contained classic-script site first.

## Import and publish

1. Sign in and open Xyvenra Cloud.
2. Choose **Import static site ZIP**. The browser reads and transforms the file locally; nothing is published by importing.
3. Review the HTML and safe preview. Create your private site if needed.
4. Save the page, then choose Publish when you are ready to make it public.

Pages run inside an opaque-origin sandbox. Each account can create up to three sites and each site keeps up to five prior saved versions. The Cloud static-site ZIP importer does not create build logs, custom domains, or server functions.

## Review a saved version before restoring

In **Saved versions**, choose **Preview** to load that prior page in its own sandboxed frame. Review it before choosing **Restore**; the restore action replaces the current saved page (and keeps the replaced state in history). Version previews are owner-only, fetched on demand, and are not public share links. They use the same restrictive browser policy as the regular preview, so network requests, external assets, embedded frames, and third-party widgets remain unavailable.

## Responsive preview sizes

Use the **Preview size** selector below the editor to view the current HTML at full width, desktop (1280 × 800), tablet (768 × 1024), or phone (390 × 844) dimensions. This is a fixed iframe viewport for reviewing responsive layouts, not device emulation; it does not reproduce mobile browser chrome, touch behavior, or operating-system differences. The preview remains sandboxed and blocks network access in every size.

## Export a Cloud site

Choose **Download HTML** in the page editor to download the current editor contents as a standalone `.html` file. The download includes unsaved editor changes. Imported or compiled local assets are embedded, and linked pages are included by the static-site compiler. Multi-page imports remain a single HTML file with hash-based page navigation. Cloud stores no framework source, build scripts, server code, or external service credentials to export. Test the downloaded file on the target host before switching traffic.