GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: reorganize README.md by joyeecheung · Pull Request #60490 · nodejs/node

Conversation

@joyeecheung

@joyeecheung joyeecheung commented Oct 29, 2025

Copy link
Copy Markdown
Member

The README previously mixes information of different levels of details e.g. some are just links, some include detailed instructions and commands.
This reorganizes README.md to make it more like a map of links. The release information are moved into a dedicated document. Only the releaser list remains in the README.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to Node.js documentation. label Oct 29, 2025
@joyeecheung
joyeecheung force-pushed the reorg-readme branch from e3266ab to a4719b6 Compare October 29, 2025 17:48
aduh95
aduh95 reviewed Oct 29, 2025
View reviewed changes
Comment thread README.md Resolved

Uh oh!

There was an error while loading. Please reload this page.
@joyeecheung
joyeecheung force-pushed the reorg-readme branch 4 times, most recently from 0d732e1 to 13e5c5d Compare November 1, 2025 09:28
@joyeecheung
doc: reorganize README.md
d1fe412 
The README previously mixes information of different levels of
details e.g. some are just links, some include detailed instructions
and commands.
This reorganizes README.md to make it more like a map of links.
The release information are moved into a dedicated document. Only
the releaser list remains in the README.
@joyeecheung
joyeecheung force-pushed the reorg-readme branch from 13e5c5d to d1fe412 Compare November 1, 2025 09:31
aduh95
aduh95 reviewed Nov 1, 2025
View reviewed changes
Comment thread RELEASE.md
@@ -0,0 +1,69 @@
# Node.js Releases

<!-- TODO(joyeecheung): merge it into Release#readme? -->

@aduh95 aduh95 Nov 1, 2025

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this belongs to the root level – but yeah indeed it's worth considering whether it makes sense to keep it in this repo. FWIW I've suggested putting it on the website in nodejs/nodejs.org#7942.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@joyeecheung joyeecheung mentioned this pull request Nov 2, 2025
Let's document how to verify a Node.js downloads on the website nodejs/nodejs.org#7942
Open
avivkeller
avivkeller approved these changes Jan 3, 2026
View reviewed changes
@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

This pull request has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@github-actions github-actions Bot added the stale Issues and PRs marked stale due to inactivity and scheduled for automatic closure. label Jul 28, 2026
@github-actions

github-actions Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

This pull request has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@github-actions github-actions Bot closed this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aduh95 aduh95 aduh95 left review comments
@avivkeller avivkeller avivkeller approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

doc Issues and PRs related to Node.js documentation. stale Issues and PRs marked stale due to inactivity and scheduled for automatic closure.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

4 participants

@joyeecheung @aduh95 @avivkeller @nodejs-github-bot
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.