Skip to content
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.

Sign up for GitHub

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

Jump to bottom

doc: propose revising the downloads page #598

Merged
merged 1 commit into from May 4, 2024
Merged

doc: propose revising the downloads page #598

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/version-management/proposal-revise-downloads-page.md
View file
Open in desktop
@@ -0,0 +1,13 @@
# Proposal: Revise Downloads Page

As part of achieving the second [goal](./goals.md):

> Install Node.js and a package manager for a local development environment.

Our view is that the optimal way to install Node.js and bootstrap components like a package manager is through one or more external tools.

As an initial step towards this, we should revise the Node.js download page, https://nodejs.org/en/download, so that the primary download instructions suggest installation via one or more tools that provide for managing the versions of the Node.js runtime and of a package manager.

The current primary download method, a link to an installer, would still be an option available in one of the download page’s tabs; but it would no longer be the default method. This is because the installer link is only appropriate for certain target users, such as those who use Node.js for running scripts, and not for our primary target user group of application developers. Our default recommendation should be targeting our default set of users, and therefore it should recommend installing via one or more tools that make it easy to manage the runtime and package manager per project.

We should do this revision now, without predicating it on any changes to the Node.js distribution or on creating new tools. Once the page is rewritten, hopefully it should be apparent where any distribution changes or new tools might provide for an improved developer experience, and we can pursue ideas in those directions.