Skip to content

sanity-migration: point Webflow reference at the Sanity Learn migration guide - #60

Draft
claude[bot] wants to merge 3 commits into
mainfrom
webflow-migration-learn-guide
Draft

sanity-migration: point Webflow reference at the Sanity Learn migration guide#60
claude[bot] wants to merge 3 commits into
mainfrom
webflow-migration-learn-guide

Conversation

@claude

@claude claude Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Requested by Knut Melvær · Slack thread

Before: The Webflow migration reference duplicated a long body of platform guidance, and the first commit on this branch added a "Start Here" block telling the agent to fetch the Sanity Learn course URL — making a network fetch a required step.

After: A self-contained, distilled guide informed by the Sanity Learn Webflow → Sanity course. It is followable with no network — the course URL is kept only as a source/further-reading citation near the top — and it matches the format of the other platform references (contentful.md, wordpress.md): the same terse, imperative H2 skeleton (What to Determine FirstExtraction PathsMapping to SanityTransformation NotesImport OrderStatic Page and Page Builder WorkflowCutoverGotchasValidation Checklist).

Genuinely useful course specifics are folded in (distilled to bullets): the Webflow Data API as the preferred path with ID-to-ID reference joins, the three Webflow CDN domains, the Assets-API blind spot, the two-pass _weak-placeholder import, deterministic type-id IDs, _key-on-every-array-item, htmlToBlocks() rich-text conversion, DOM-API static-page extraction, page classification (stacked / split / CMS-driven / custom), the eight Webflow content-modeling anti-patterns, forms-as-full-replacement, vercel.json redirects, and DNS/404 cutover steps. All agent-specific guidance is retained: reference-ID lookup maps, leaf-collections-first ordering, CSV normalization, the CDN asset sweep across CSV/rich text/HTML/CSS/OG, the component-inventory-before-HTML step, the section-pattern analysis prompt, redirect/URL-map cutover, "don't reorganize a live Webflow CMS to ease export", and the validation checklist.

How

  • Replaced skills/sanity-migration/references/webflow.md with a distilled, self-contained reference (~149 lines), dropping the required "fetch this URL" block and folding its intent (read the guidance, align on decisions, plan into MIGRATION.md) into a brief lead-in.
  • Read the course markdown in full plus the sibling references to calibrate house style; kept the file frontmatter-free and matched the sibling H2 skeleton.
  • One factual shift from the course: framed the Webflow Data API as the primary extraction path (its item-ID references are cleaner than CSV joins) with CSV as the fallback, and clarified that Sanity validates references on write, so import uses _weak placeholders resolved in a second pass — the leaf-first ordering is retained alongside it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EwCiGS4nB5F1Benh3jYTun

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Webflow → Sanity migration reference to be self-contained and aligned with the repo’s migration-reference format, removing any requirement to fetch external content during execution.

Changes:

  • Adds a concise lead-in and expands the Webflow migration guidance with more specific extraction, modeling, and import sequencing notes.
  • Standardizes the section structure to match the other platform migration references (audit → extraction → mapping → transform → import → cutover → gotchas → validation).
  • Incorporates Webflow-specific operational details (Data API usage, CDN domains, two-pass _weak reference resolution, cutover checklist).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread skills/sanity-migration/references/webflow.md Outdated
Comment on lines +29 to +30
- **Site structure via API:** `GET /sites/{id}/collections` (field types, reference targets), `/pages` (slugs + SEO metadata — this is your URL inventory, no sitemap XML needed), `/components` (component definitions), `/forms` (field schemas), and `/custom_code` (script inventory; Business plan or higher). Save each response as JSON and inspect before modeling.
- **Static pages (DOM API):** `GET /v2/pages/{page_id}/dom` returns only editable content nodes — `text`, `image`, and `component-instance` (each with a `propertyOverrides` array of the content set per instance). It carries no layout context; pair it with the HTML export, which is the only source of section structure.
…PI notation

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EwCiGS4nB5F1Benh3jYTun
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants