Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #598 from nodejs/proposal-revise-downloads-page
doc: propose revising the downloads page
- Loading branch information
Showing
1 changed file
with
13 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. |