docs: add "How to adopt Deno" guide for incremental team adoption#3383
Draft
bartlomieju wants to merge 1 commit into
Draft
docs: add "How to adopt Deno" guide for incremental team adoption#3383bartlomieju wants to merge 1 commit into
bartlomieju wants to merge 1 commit into
Conversation
Repurpose the top-level /runtime/migrate/ page as a phased, low-risk adoption path (tooling -> CI -> package manager -> pilot -> runtime) and move the Node.js migration mechanics to a sibling page. Retarget inbound 'Migrate from Node.js' links to the moved page and rename the sidebar group to 'Adopting Deno'.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The migration docs covered the technical, single-project path to Deno, but
nothing addressed introducing Deno to a team without full buy-in: which
low-risk surface to start with, how to show value before touching the app
runtime, and how to argue that each step is reversible.
This repurposes the top-level /runtime/migrate/ page as "How to adopt Deno,"
a phased path ordered from lowest to highest risk (tooling with deno fmt and
deno lint, then a CI check alongside Node, then Deno as a package manager,
then piloting a project, then switching the runtime), with a short section
framing why each step is safe to try. The existing Node.js migration
mechanics move to a sibling page, runtime/migrate/migrate_from_node/, which
keeps its title and oldUrl redirects. Inbound "Migrate from Node.js" links
are retargeted to the moved page, and the sidebar group is renamed from
"Migrating from Node" to "Adopting Deno."
Opening as a draft. One open question: external links to /runtime/migrate/
now land on the adoption overview rather than the Node guide. That is by
design, but the adoption page could instead live at a fresh URL if we would
rather preserve the old destination exactly.