--- name: vizen-transfer description: Move a FINISHED site or template — an HTML/CSS/JS folder, a static React/Vite export, a Figma/Webflow/Tilda export — into a Vizen shop through a personal token as it is: folder = level-3 widget in real page DOM, one command per folder, scripts and position:fixed work, no rebuild, no Shadow DOM. Layout folder, header/footer, pages, product/category templates, live-data re-binding, the check. Invoke when the task says transfer, migrate, "we already have a site", or hands you a folder, ZIP or repo. --- # Transfer a finished site You are **moving, not designing**. The owner's site defines the look; your job is to make it appear in the shop as it is, re-bind the data the shop owns (menu, prices, cart, forms) and prove the result with screenshots. No redesign, no cutting into sections, no path rewriting, no improvements nobody asked for. ## 1. Is this your path? | You have | Go | |---|---| | a folder, ZIP, repo or export that already renders in a browser | **here** | | nothing yet — a page to build from scratch | `vizen-start` and its three questions | | a question about vz- keys, partial releases, images inside one widget | `vizen-own-markup` | | groups, bindings, system pages (cart, account…), sticky | `vizen-chrome` | | goods, categories, filters | `vizen-catalog` | | "200 and nothing changed" | `vizen-troubleshoot` | The full contract — what the platform does to your file, the copy · remap · drop table, framework notes — is `GET /docs/transfer`. Read it once, before step 2. ## 2. What the platform gives you (measured, not promised) - **Folder = widget.** A level-3 html document is a folder: `index.html` at the root, css/js/assets in subfolders, relative paths from the root. A release uploads it; files are served from `/_html/{doc}/{rid}/…` with the same nesting. - **Real page DOM.** No Shadow DOM, no iframe, no sanitiser: `