convez.ai
Skill
fast-forward-innovation

website-migration

fast-forward-innovation/website-migration

Ver no GitHub
InicialPluginScore · de 0 a 100

Set of claude skills and configuration to aid in website migration projects. This is an experimental project.

Instalação

$npx convez-ai fast-forward-innovation/website-migration

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
37%
Último commit
há 5 meses
Versão
—
Issues abertas
0
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

website-migration

A Claude Code plugin that drives a website migration end-to-end. It moves content and assets off a legacy CMS — Drupal, WordPress, or HubSpot — and onto a Next.js site (the only target today; a WordPress target is planned).

The plugin ships 8 skills that form a pipeline. Each skill reads the prior phases' outputs from a shared migration/ folder in the target project, does its work, writes its own artifacts back, and updates a single migration/manifest.json state file. That manifest is the contract spine: it lets each phase run independently and hand off cleanly to the next.

Pipeline

migration-plan ─▶ migration-discovery ─▶ migration-architecture ─┐
                                                                 ▼
            migration-summary ◀─ migration-test ◀─ migration-full (export ─▶ import)
                                                          │
                                              (or run migration-export / migration-import directly)
SkillPhaseWhat it does
migration-planplanCaptures source/architecture/access, code access, and hosting (Pantheon + base domain); scaffolds migration/ + manifest.json + plan.md.
migration-discoverydiscoveryInventories the old site (API/export and source code) → discovery/inventory.json + report.md.
migration-architecturearchitectureDesigns the new Next.js site, picks the content layer, reuses an existing headless frontend → architecture.md.
migration-exportexportExtracts + normalizes content/assets → export/content/*.json + export/assets/.
migration-importimportWrites normalized content into the Next.js site → import-report.md + mapping.
migration-fullexport + importRuns export then import in sequence, stopping on first failure.
migration-testtestParity, redirect, asset-integrity, link, and build checks → test/test-report.md.
migration-summarysummaryAggregates everything into a human-readable summary.md.

Install from GitHub

This repo is both the plugin and its marketplace catalog (.claude-plugin/plugin.json + .claude-plugin/marketplace.json), so no public listing or registry is involved — teammates install straight from this repo.

One-time, to publish to the existing fast-forward-innovation/website-migration repo:

cd /path/to/this/repo
git init && git add . && git commit -m "website-migration plugin"
git remote add origin https://github.com/fast-forward-innovation/website-migration.git
git branch -M main
git push -u origin main

Each teammate then runs, in any project:

/plugin marketplace add fast-forward-innovation/website-migration
/plugin install website-migration@fastforward

(fastforward is the marketplace name from .claude-plugin/marketplace.json — change it there if you want a different label after the @.)

Auto-enable for a whole team

To have everyone on a project get the plugin automatically, commit this to that project's .claude/settings.json. When teammates trust the folder, Claude Code prompts to add the marketplace and enable the plugin:

{
  "extraKnownMarketplaces": {
    "fastforward": {
      "source": { "source": "github", "repo": "fast-forward-innovation/website-migration" }
    }
  },
  "enabledPlugins": {
    "website-migration@fastforward": true
  }
}

Pin a version by setting "version" in plugin.json and bumping it per release; otherwise each pushed commit is treated as a new version. Update an installed copy with /plugin marketplace update.

Usage

Invoke the skills in order from the target project directory (the Next.js repo you're migrating into). Start with:

/migration-plan

Then follow the recommended sequence in migration/plan.md. Any skill can be run standalone as long as its prerequisite phases are marked done in the manifest — each skill checks this and refuses clearly if a prerequisite is missing.

Source access

migration-plan captures how we can reach the old site. Methods combine freely.

Content access (mix as needed per source):

  • Live API / credentials — WordPress REST + WPGraphQL, Drupal JSON:API, HubSpot CMS + CRM API.
  • DB dump / native export — SQL dump, Drupal migrate, WordPress WXR (eXtended RSS), HubSpot export.

Source-code access (optional, but a high-value discovery input). The plan records whether the old site is coupled (the CMS renders pages via a theme) or headless (a decoupled frontend app consumes the CMS over an API), and captures code per role:

  • cms — backend content-type/field definitions, custom modules/plugins (+ theme/templates if coupled).
  • frontend — the decoupled frontend app (headless only) and its framework (Next, Gatsby, Nuxt, Vue, …). Often maps almost directly onto the new Next.js components.

Each role can be a local folder or a git repo (cloned to migration/_input/source-code/<role> using your existing git credentials). migration-discovery scans whatever is present and records each finding's provenance (api / export / cms-code / frontend-code).

Credentials are read from environment variables and only referenced by name in the manifest — secrets and tokens are never written to the plugin or to the migration/ folder.

Hosting the new site

The default host is Pantheon. migration-plan prompts for the host provider and the production base domain, and can provision sites with Terminus:

  • The Next.js app is hosted as a Pantheon Front-End Site.
  • A headless CMS backend (WordPress/Drupal) can also run on Pantheon when the architecture picks that content layer.
  • migration-import deploys to the Front-End Site and promotes dev → test (promotion to live is confirmed first).

Infrastructure-creating actions (terminus site:create, domain:add, env:deploy ... live) require explicit confirmation; recording hosting config in the manifest is the safe default. The Terminus machine token is read from an env var (name in the manifest, value never stored).

Reference material

Shared, source-agnostic reference docs live in references/:

  • references/manifest-schema.md — the migration/manifest.json contract (source, code access, hosting, phases).
  • references/normalized-content.md — the canonical intermediate content schema.
  • references/sources/{drupal,wordpress,hubspot}.md — per-platform extraction notes.
  • references/targets/nextjs.md — Next.js routing, rendering, images, redirects, content layers.
  • references/targets/pantheon.md — Pantheon + Terminus: auth, provisioning, domains, deploy.

Testing

Structural tests (deterministic) and a behavioral eval (model-in-the-loop, against an offline WordPress WXR fixture) live in tests/. See tests/README.md. CI runs the structural suite on every push/PR; the behavioral job runs when an ANTHROPIC_API_KEY secret is set.

Ver o original no GitHub

Bom para

Relacionados