migrate
/migrate
Przenosi stronę Webflow do Astro z Sanity jako CMS, Cloudflare Pages, formularzami na D1 i dokumentem przekazania.
- Autor
- Horlladjosh ↗
- Repozytorium
- webflow-astro ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 41
- Skrypty
- 24
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 24 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: assets/scripts/convert-webflow.py, assets/scripts/lists.py, assets/scripts/vendor.py, assets/scripts/wire-cms.py, assets/site/astro.config.mjs, assets/site/functions/admin/_middleware.js, assets/site/functions/admin/delete.js, assets/site/functions/admin/index.js, assets/site/functions/admin/login.js, assets/site/functions/admin/logout.js, assets/site/functions/api/forms.js, assets/site/integratio
Co robi i kiedy
Przenosi stronę Webflow do Astro z Sanity jako CMS, Cloudflare Pages, formularzami na D1 i dokumentem przekazania.
Wyzwalacze z opisu
Oryginalny opis (EN)
Migrate a Webflow site (export zip) to Astro with Sanity as the CMS, Cloudflare Pages hosting, a D1-backed forms backend with a password-protected /admin, GitHub, custom domains, and a handover document. Use when the user has downloaded or exported a Webflow project and wants to move it off Webflow to code, says "migrate this Webflow site", runs /webflow-astro:migrate, or asks to redo the webflow-astro account setup.
Jak działa
- Ground rules
- Steps
Podgląd SKILL.md
---
name: migrate
description: Migrate a Webflow site (export zip) to Astro with Sanity as the CMS, Cloudflare Pages hosting, a D1-backed forms backend with a password-protected /admin, GitHub, custom domains, and a handover document. Use when the user has downloaded or exported a Webflow project and wants to move it off Webflow to code, says "migrate this Webflow site", runs /webflow-astro:migrate, or asks to redo the webflow-astro account setup.
---
# Webflow → Astro + Sanity + Cloudflare migration
Output: the same site (markup, classes and `data-w-id` animations intact) as Astro pages, CMS
collections in Sanity, forms stored in Cloudflare D1 with an `/admin` inbox, code on GitHub,
hosting on Cloudflare Pages that rebuilds when content is published, the user's domains pointed
at it, and a plain-language handover document.
`$SKILL` = the folder this SKILL.md is in (the skill's base directory, shown when it loads).
Read `references/setup.md` for step 0, `references/content-and-conversion.md` before step 3 and
`references/cloudflare.md` before step 9. `examples/blog/` is a small worked example of every
custom piece (schemas, import, list component, detail page).
## Ground rules
- **Stop and ask at the checkpoints marked ✋.** These are the user's decisions or actions.
Don't guess, and don't work around them.
- If a connector or CLI is logged in but can't see the site, project, org or account you need,
**ask the user to reconnect it to the right account** before trying any workaround.
- Never choose passwords, never handle secrets for the user, and never edit DNS. The user does
those. Create a GitHub repo only after the user confirms its name and visibility.
- Never write tokens, keys or passwords into files, memory, the settings file or the handover.
- Keep the old Webflow site untouched until the user cancels it. It's the rollback.
- Give short progress updates; this is a long job.
## Steps
### 0. Accounts (first run sets up, later runs only check)
Follow `references/setup.md`. In short:
- Read `~/.config/webflow-astro/config.json`.
- **File missing (first run):** check GitHub (`gh`), Cloudflare (`wrangler`), Sanity (CLI) and
the Webflow connector. ✋ For anything not logged in, give the user the one command to run or
the connector to connect, and wait. Then ✋ ask once which GitHub owner, Cloudflare account and
Sanity organization to use, and where to keep projects and handover documents. Save the
answers (names and IDs only).
- **File present (later runs):** run the quick checks silently. If they pass, say "Accounts OK"
in one line and go on. Only ask about the one that failed.
- If the user asks to change accounts or redo setup, run the first-run flow again.
### 1. Set up the project folder
- The export is usually the newest `<name>.webflow.zip` in `~/Downloads`. Confirm the name in
one line.
- Create `<projectsDir>/<slug>-site/` (`projectsDir` from the settings file), extract into
`webflow-export/` with **`bsdtar -xf`** (emoji file names break `unzip`), and `git init -b main`.
- **Move the session into the project folder before anything else.**
- In the Claude desktop app (a `change_directory` tool exists): call it with the new folder,
then end the turn with one line: "Project folder ready at <path> and the session is moving
there. Say go and I'll ask the setup questions." Do nothing else in that turn; the move only
takes effect when the turn ends, and work done in the same turn stays attached to the old
folder (memories get saved under the wrong project). Next turn, run `pwd` to confirm, and
call `change_directory` again if it didn't stick.
- In the terminal (no such tool): ask the user to exit and run `cd <path> && claude`, then
say "continue the webflow migration".
### 2. ✋ Ask up front (one AskUserQuestion with these questions)
1. **GitHub repo.** "Paste an empty repo to push to, or tell me a name and whether it should be
private, and I'll create it under <githubOwner>." Check a pasted repo is empty, and mention if
it's public.
2. **Which domain(s)** the site will live on, and which is the main address for Google. Check
where those hosts point today (`dig`, `curl -I`): Webflow (`cdn.webflow.com`) or something
else. Often only some hosts are on Webflow (e.g. a subdomain) and `www` is a different app.
3. **CMS source.** Check the Webflow connector can see this site. If it can't, ask the user to
sign in again via `/mcp` → webflow and tick this site (`references/setup.md` → A site that's
not on the list), or to send CSV exports. Scrape only if they explicitly say so.
4. Anything to leave out (old/test pages) or keep as-is.
The default stack is Astro + Sanity + Cloudflare (Pages + D1). If the site has no CMS, skip Sanity;
if it has no Webflow-backed forms, skip D1 and /admin.
### 3. Inventory the export
Pages (published or not), CMS lists per page (`assets/scripts/lists.py`), forms (and where each
posts), third-party scripts, site-wide custom code. Details: `references/content-and-conversion.md`.
### 4. Scaffold and convert
- Copy `$SKILL/assets/site/*` into the project (`gitignore.txt` → `.gitignore`,
`node-version.txt` → `.node-version`) and fill every `{{PLACEHOLDER}}` (grep for `{{`).
- Copy `webflow-export/{css,js,images,videos,fonts}` into `public/`. Drop files over 25 MiB that
no page uses (Cloudflare's limit), and note them for the handover.
- `npm install`.
- Write `migration.config.json` (pages map, siteHeadEnd, siteFootEnd) at the project root, then:
```bash
python3 -I $SKILL/assets/scripts/vendor.py webflow-export public/vendor migration.config.json
python3 -I $SKILL/assets/scripts/convert-webflow.py webflow-export src/pages migration.config.json
```
Copy the scripts into the project's `scripts/` folder so the repo can re-run them.
- Fill `src/layouts/Base.astro` with the site-wide head/footer code (see the reference).
- Fix CDN references the export missed (`"local"` in the config) and rerun. Build with `npx astro build`.
### 5. Sanity (if the site has CMS collections)
- Create the project **in the Sanity organization from the settings file** (see
`references/setup.md` → Creating a Sanity project), CORS `http://localhost:3333`. Don't keep any
returned tokens.
- Studio: copy `$SKILL/assets/studio/*` to `studio/`, write schemas (one type per collection,
drag-orderable), `npm install` + `lexorank` (exact version), `npx sanity schemas deploy`.
- Get the content (connector API > CSV > scrape), write `studio/migrations/webflow/content.json`
+ `import.ts` (fixed ids, createOrReplace; see `examples/blog/import.ts`), run it, and verify
counts with an anonymous query.
- `npx sanity deploy -y` → hosted Studio.
### 6. Wire CMS lists and detail pages
Components in `src/components/` that reproduce each list's Webflow markup; `src/lib/sanity.ts`
getters; `wire-cms.py` with `"cms"` in the config swaps them in. Detail pages via `[slug].astro`.
### 7. Forms + /admin (if any form posted to Webflow)
Adapt `FormHandler.astro`, `functions/api/forms.js` and `functions/admin/index.js` to the
site's forms. `npx wrangler d1 create <slug>-db` → id into `wrangler.toml` →
`npm run db:migrate:local` and `--remote`. Test locally with `wrangler pages dev` (see the
verifying section of the reference).
### 8. Verify, commit, push
- Text diff every page against the live Webflow page; spot-check visually.
- Write the project `README.md` (structure, what lives where, differences from Webflow, local
dev, hosting). Commit.
- Push `main` to the repo from step 2 (create it with `gh repo create` first if the user asked).
### 9. Cloudflare Pages (`references/cloudflare.md`)
- Create the git-connected Pages project via API with the D1 binding, trigger the first build,
and watch it. Check every page on `<project>.pages.dev`.
- Deploy hook + Sanity webhook (rebuild on publish); test by firing the hook.
- ✋ **Ask the user to set the admin password** in their terminal:
`npx wrangler pages secret put ADMIN_PASSWORD --project-name <project>`. Then redeploy
(secrets apply to new deployments only) and confirm `/admin/login` works. Tell them how to
change it later.
### 10. Domains
- Set `site` in `astro.config.mjs` to the main address; add `public/robots.txt` (Disallow
/admin, Sitemap line). Push.
- Add the custom domain(s) to the Pages project via API **before** DNS changes.
- ✋ **Tell the user exactly which DNS records to change** (host, current value, new value) and
that the domain stays where it is (no transfer needed for subdomains). They make the change.
- When they say done: check DNS (local, 1.1.1.1, authoritative), domain status in Pages,
HTTPS cert, every page, canonical, robots, sitemap, `/api/forms` and `/admin` on each host.
A Webflow 404 page after the switch = the hostname isn't on the Pages project yet.
### 11. Handover document
Write `<handoverDir>/<Site-Name>-Handover.md` following `references/handover.md` (if earlier
handovers exist there, read the newest first and match it). Blank login fields; verified facts only.
### 12. Wrap up
- Save/update a project memory (repo, Sanity project id, Pages project, D1, domains, pending items).
- Tell the user what's left: test any external forms (newsletter, checkout) themselves, keep
Webflow for a few weeks then cancel, optional email alerts for form submissions.
Pliki w paczce (41)
- SKILL.md 9 KB
- assets/scripts/convert-webflow.py 6 KB
- assets/scripts/lists.py 1 KB
- assets/scripts/vendor.py 3 KB
- assets/scripts/wire-cms.py 1 KB
- assets/site/astro.config.mjs 1 KB
- assets/site/gitignore.txt 1 KB
- assets/site/node-version.txt 1 KB
- assets/site/package.json 1 KB
- assets/site/wrangler.toml 1 KB
- assets/site/functions/admin/_middleware.js 1 KB
- assets/site/functions/admin/delete.js 1 KB
- assets/site/functions/admin/index.js 3 KB
- assets/site/functions/admin/login.js 2 KB
- assets/site/functions/admin/logout.js 1 KB
- assets/site/functions/api/forms.js 1 KB
- assets/site/integrations/webflow-whitespace.mjs 3 KB
- assets/site/lib/admin-session.js 3 KB
- assets/site/lib/admin-ui.js 3 KB
- assets/site/migrations/0001_init.sql 1 KB
- assets/site/src/components/FormHandler.astro 4 KB
- assets/site/src/layouts/Base.astro 3 KB
- assets/site/src/lib/sanity.ts 3 KB
- assets/studio/package.json 1 KB
- assets/studio/sanity.cli.ts 1 KB
- assets/studio/sanity.config.ts 1 KB
- assets/studio/tsconfig.json 1 KB
- examples/blog/PostList.astro 1 KB
- examples/blog/README.md 1 KB
- examples/blog/import.ts 2 KB
- examples/blog/post-detail-page.astro 2 KB
- examples/blog/sanity-getters.ts 1 KB
- examples/blog/sanity.config.ts 1 KB
- examples/blog/scrape-extract.py 2 KB
- examples/blog/schemaTypes/index.ts 1 KB
- examples/blog/schemaTypes/post.ts 2 KB
- examples/blog/schemaTypes/testimonial.ts 1 KB
- references/cloudflare.md 6 KB
- references/content-and-conversion.md 6 KB
- references/handover.md 2 KB
- references/setup.md 7 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Horlladjosh/webflow-astro | 100 | MIT |
| marcel-bich/marcel-bich-claude-marketplace | 100 | MIT |
| abatyuk/okf | 100 | MIT |
| markusleben/ha-nova | 100 | MIT |
| toss/es-toolkit | 100 | MIT |
| rvdbreemen/adr-kit | 100 | MIT |
| asgeirtj/system_prompts_leaks | 100 | CC0-1.0 |
| madappgang/magus | 100 | MIT |
| bennypowers/cem | 100 | GPL-3.0 |
Migawka bazy z 13.11.2026 · wersja paczki 8f67a18d93b6 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100webflow
Pomaga pracować z Webflow i Data API v2: tokeny, elementy CMS, publikowanie, webhooki z weryfikacją podpisu oraz serwer MCP do aktualizacji treści ze skryptów. - 100webflow-migration-deep-dive
Migruje treści zewnętrzne lub między witrynami do Webflow CMS z mapowaniem schematu, partiami etapowymi, uzgadnianiem i kontrolowaną publikacją, na przykład z WordPress, CSV, JSON lub z Webflow do Webflow. - 100webflow-core-workflow-b
Planuje operacje Webflow Data API poza główną pętlą elementów CMS, obejmując strony, komponenty, formularze, ecommerce, zasoby i własny kod, wraz z przeglądem zakresów uprawnień endpointów. - 90webflow-mcp:site-audit
Audytuje witrynę Webflow: strony, kolekcje CMS, ocenę kondycji i wnioski do działania, przydatne przy analizie struktury i planowaniu migracji. - 81webflow-mcp:cms-best-practices
Doradza w architekturze CMS Webflow: projektowanie kolekcji, relacji i struktury treści. - 100webflow-webhooks
Odbiera i weryfikuje webhooki Webflow, w tym weryfikację podpisu i zdarzenia form_submission, site_publish, ecomm_new_order oraz zmiany elementów kolekcji.