Skip to content

Add guide for migrating from Netlify to Workers #22504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: production
Choose a base branch
from

Conversation

thomas-desmond
Copy link
Contributor

Summary

A guide for migrating applications from Netlify to Workers. Follows the exact same flow as the Vercel guide with only the "Find your build command and build directory" section being different.

Documentation checklist

Copy link
Contributor

hyperlint-ai bot commented May 16, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Added a comprehensive guide for migrating applications from Netlify to Cloudflare Workers, aligning with existing migration documentation for Vercel.

  • Introduced a new tutorial for migrating from Netlify to Workers.
  • Outlined steps for finding build commands and directories in Netlify.
  • Provided configuration examples for wrangler files for different application types.
  • Included instructions for connecting a new Worker and adding a custom domain.

Added Files

  • src/content/docs/workers/static-assets/migration-guides/netlify-to-workers.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product:workers Related to Workers product size/s
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants