Import a site or convert it from Webflow

If you already have a site, you do not have to start from a blank project. The New project dialog has a row called Or start from an existing site:

• Import a project takes an Astro site from a folder on your Mac.
• Convert from Webflow takes a Webflow code export, the published address, or both.
• Convert a project (other frameworks and tools) is marked Soon.

Import an Astro project

Import is marked Unstable: it works, but it has not yet been tested across many kinds of Astro sites. Check the result after the assistant finishes. The Before import version in History takes you back to the copy as it arrived.

1. Choose New project, then Import a project, and pick the folder that holds your Astro site (the one with package.json and astro.config). Plyed checks that it is an Astro project. If it is not, it says so; use Convert for other kinds of site.
2. Check the name (it comes from the folder) and the place the project will be saved, then choose Import site.

Plyed makes a copy in your projects folder. Your original folder is never changed. The copy leaves out node_modules, build output (dist, .astro, .vercel, .netlify, .output) and the .git history, so the copy starts with fresh history. Links inside the folder are not followed. A site over 50,000 files or 1 GB (without node_modules) is refused.

Then:

1. Trust. An imported site runs its own code, so Plyed asks whether you trust it before it installs or starts anything. Choose Trust and open only for a site you made or know.
2. A saved version. Plyed saves a version called Before import in History. If you do not like what comes next, restoring it puts the site back as it was when you imported it.
3. The assistant adapts the site. A chat opens and the assistant works through your site in order: it checks that it builds, adds Plyed’s rules, moves loose scripts and animation code into modules, reveals into data-animate, puts the text styles and repeated colours on tokens, and checks the pages in the preview. It keeps your content and your page addresses, and asks before removing any dependency. When it is done it tells you what it changed and what it left.

You can watch it, stop it, or ask it to do less. Nothing is published.

Convert a Webflow site

Convert from Webflow is also marked Unstable: it works, but it has not yet been tested across many Webflow sites. Check the converted pages, styles and CMS content before you rely on them.

Webflow has two sources and they complement each other:

• The code export (in Webflow: Export code, a paid workspace feature) has your pages, styles, images and fonts, but not your CMS items.
• The published address lets Plyed capture accessible public pages, including linked CMS item pages. A capture follows links on the same site, up to 12 pages and three link levels, and may stop after five minutes. Robots restrictions and content that needs JavaScript or a login can leave pages or details out. Check which pages were captured and give the assistant any missing content separately.

1. Choose New project, then Convert from Webflow.
2. Choose the .zip or the unzipped folder, paste the published address, or do both. The name comes from what you chose.
3. Choose Convert site.

Plyed makes a new project from the Plain starter, unpacks a zip into the project (.plyed/inbox/webflow-export), and opens a chat. The assistant first asks if the site is yours or if you have the owner’s permission to copy it. It then rebuilds the supplied pages on Plyed’s building blocks: Webflow classes become Tailwind styles and tokens, Webflow interactions become reveals and modules, and CMS collections become content collections with a list page and a page per item. The assistant aims to preserve the captured pages’ addresses and SEO tags. Check the converted result before publishing.

Some things do not come along and are listed in the assistant’s final message: Webflow’s own form handling (you point forms at your own service), interactions it could not reproduce, and anything that needs a login. The first capture of a live site downloads a browser once (about 150 MB).

If something goes wrong

• “This folder is not an Astro project.” Pick the folder that contains package.json, not a parent folder.
• No chat appeared. The chat starts after the project is running. If you did not choose Trust and open, it waits; reopen the project and trust it. You can also ask in a new chat: “Use the plyed-import skill” or “Use the plyed-migrate skill”.
• Restore. For an import, open History and choose Before import.