Nextjs Migration Map

Recommended Working Order

1. Inventory the current page or script being migrated.
2. Read references/page-migration-matrix.md to map the current file to a target route, rendering mode, and owning modules.
3. Read ../nextjs-rendering-strategy/SKILL.md when the surface is public and freshness/SEO are relevant.
4. Read ../nextjs-foundation/SKILL.md and ../nextjs-architecture-patterns/SKILL.md before introducing new route/module boundaries.
5. Read an area-specific sibling skill for the actual implementation details.
6. Read ../nextjs-testing-and-quality/SKILL.md before claiming a migration slice is complete.

Current-to-Target Mapping Rules

• *.html public pages -> src/app/**/page.tsx or metadata/static asset equivalents.
• list/detail pages that currently depend on query parameters should usually migrate toward semantic App Router segments such as [slug] or [id].
• admin/*.html -> protected src/app/admin/** routes with server-owned auth and mutation boundaries.
• css/style.css -> global styles, tokens, and shared component styling layers.
• js/script.js -> shared UI behaviors split between server-rendered structure and small client components/hooks where interactivity is required.
• js/admin.js -> admin feature modules, server actions, route handlers, and domain use-cases instead of one browser-owned orchestration file.
• js/data.js -> seed/static content module or a dedicated content/data source depending on whether consultant data stays code-owned.
• js/supabase-config.js -> environment-safe wrappers and server-side data access boundaries where possible.

Rollout Heuristics

• Migrate stable corporate pages first to establish layout, navigation, metadata, and design primitives.
• Migrate editorial and recruiting surfaces next with ISR and on-demand revalidation patterns.
• Migrate admin and privileged mutations after the public read paths are stable.
• Do not keep privileged write flows browser-only in the target architecture if the server can own them.

Reference Map

• Read references/page-migration-matrix.md for the concrete current-page to target-route mapping.
• Read ../nextjs-rendering-strategy/references/corporate-site-page-map.md for default rendering choices.
• Read ../nextjs-foundation/references/folder-layout.md for target folder placement.