Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Commit 0972d13

Browse files
ovflowdovflowd
authored
feat(pages): removed deprecated pages, added new pages, updated existing ones (#2742)
1 parent 20843c6 commit 0972d13

134 files changed

Lines changed: 1497 additions & 1675 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.gitignore‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,6 @@ coverage
1616
.history
1717
yarn.lock
1818
.idea/
19+
20+
# Firebase
21+
firebase-debug.log

‎CONTRIBUTING.md‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,8 +92,6 @@ In the case of an objection being raised in a pull request by another collaborat
9292
* A Pull Request must be opened on the @nodejs/nodejs.dev README file adding the new collaborator to the list (note the order of names)
9393
* The Pull Request must be approved by at least two members of @nodejs/nodejs.dev, @nodejs/website, or @nodejs/website-redesign
9494
* Pull Request must remain open for 72 hours without any objections
95-
* Once the requirements are met and approved, the pull request can be merged and a member of @nodejs/community-committee will add the new member to the [@nodejs/nodejs-dev team](https://github.com/orgs/nodejs/teams/nodejs-dev)
96-
9795

9896
## 🐛 Debugging Failing Checks
9997

‎README.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -197,7 +197,6 @@ participated in that process.
197197
[Query issues for "Meeting"][]
198198

199199
[code of conduct]: https://github.com/nodejs/admin/blob/main/CODE_OF_CONDUCT.md
200-
[community committee]: https://github.com/nodejs/community-committee
201200
[contributing guidelines]: ./CONTRIBUTING.md
202201
[figma design]: https://www.figma.com/file/lOxAGGg5KXb6nwie7zXkz6/NJ---Design-System?node-id=22%3A6086
203202
[meeting notes]: ./meetings

‎content/about/about.en.md‎

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ scalable network applications. In the following "hello world" example, many
1111
connections can be handled concurrently. Upon each connection, the callback is
1212
fired, but if there is no work to be done, Node.js will sleep.
1313

14-
```js
14+
```javascript
1515
const http = require('http');
1616

1717
const hostname = '127.0.0.1';
@@ -32,21 +32,22 @@ This is in contrast to today's more common concurrency model, in which OS thread
3232
are employed. Thread-based networking is relatively inefficient and very
3333
difficult to use. Furthermore, users of Node.js are free from worries of
3434
dead-locking the process, since there are no locks. Almost no function in
35-
Node.js directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.js.
35+
Node.js directly performs I/O, so the process never blocks except when the I/O is performed using
36+
synchronous methods of Node.js standard library. Because nothing blocks, scalable systems are very
37+
reasonable to develop in Node.js.
3638

3739
If some of this language is unfamiliar, there is a full article on
3840
[Blocking vs. Non-Blocking][].
3941

40-
***
42+
---
4143

4244
Node.js is similar in design to, and influenced by, systems like Ruby's
4345
[Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit
44-
further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems, there is always a blocking call to start the
45-
event-loop.
46+
further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems,
47+
there is always a blocking call to start the event-loop.
4648
Typically, behavior is defined through callbacks at the beginning of a script, and
47-
at the end a server is started through a blocking call like
48-
`EventMachine::run()`. In Node.js, there is no such start-the-event-loop call.
49-
Node.js simply enters the event loop after executing the input script. Node.js
49+
at the end a server is started through a blocking call like `EventMachine::run()`.
50+
In Node.js, there is no such start-the-event-loop call. Node.js simply enters the event loop after executing the input script. Node.js
5051
exits the event loop when there are no more callbacks to perform. This behavior
5152
is like browser JavaScript — the event loop is hidden from the user.
5253

@@ -61,9 +62,9 @@ communicate with. Built upon that same interface is the [`cluster`][] module,
6162
which allows you to share sockets between processes to enable load balancing
6263
over your cores.
6364

64-
[Blocking vs. Non-Blocking]: https://nodejs.org/en/docs/guides/blocking-vs-non-blocking/
65+
[Blocking vs. Non-Blocking]: /learn/overview-of-blocking-vs-non-blocking/
66+
[`child_process.fork()`]: /api/child_process/
67+
[`cluster`]: https://nodejs.org/api/cluster.html
68+
[event loop]: /learn/the-nodejs-event-loop/
6569
[Event Machine]: https://github.com/eventmachine/eventmachine
6670
[Twisted]: https://twistedmatrix.com/trac/
67-
[`child_process.fork()`]: https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options
68-
[`cluster`]: https://nodejs.org/api/cluster.html
69-
[event loop]: https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/

‎content/about/governance.en.md‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,12 +25,9 @@ A guide for Collaborators is maintained at [collaborator-guide.md][].
2525

2626
## Top Level Committees
2727

28-
The project is governed jointly by the [Technical Steering Committee (TSC)][]
29-
which is responsible for high-level guidance of the project, and the
30-
[Community Committee (CommComm)][] which is responsible for guiding and
31-
extending the Node.js community.
28+
The project is governed by the [Technical Steering Committee (TSC)][]
29+
which is responsible for high-level guidance of the project.
3230

33-
[Community Committee (CommComm)]: https://github.com/nodejs/community-committee/blob/main/Community-Committee-Charter.md
3431
[Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
3532
[README.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
3633
[TSC]: https://github.com/nodejs/TSC

‎content/about/governance.fr.md‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,9 @@ Un guide pour les collaborateurs est maintenu à [collaborator-guide.md][].
2626

2727
## Comités de haut niveau
2828

29-
Le projet est dirigé conjointement par le [Comité directeur technique (TSC)][]
30-
qui est responsable de l'orientation de haut niveau du projet, et le
31-
[comité de la communauté (CommComm)][] qui est responsable de l'orientation et de
32-
l'extension de la communauté Node.js.
29+
Le projet est dirigé par le [Comité directeur technique (TSC)][]
30+
qui est responsable de l'orientation de haut niveau du projet
3331

34-
[comité de la communauté (CommComm)]: https://github.com/nodejs/community-committee/blob/main/Community-Committee-Charter.md
3532
[recherche de consensus]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
3633
[README.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
3734
[TSC]: https://github.com/nodejs/TSC

‎content/about/releases.fr.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: releases
33
displayTitle: Sorties
44
description: "Sorties | Node.js"
55
authors: ZYSzys, nstanard, mikeal, fhemberger, garybernhardt, piepmatz, boneskull, bjb568, AugustinMauroy
6-
category: releases
6+
category: about
77
---
88

99
Les versions majeures de Node.js passent au statut de version _Current_ pendant six mois, ce qui donne aux auteurs de bibliothèques le temps d'ajouter la prise en charge de ces versions.

‎content/about/security.en.md‎

Lines changed: 12 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -6,38 +6,31 @@ authors: reedloden,XhmikosR,Trott,fhemberger,MaledongGit,yous,sam-github,vdeturc
66
category: about
77
---
88

9-
## Reporting a Bug in Node.js
9+
## Reporting a bug in Node.js
1010

1111
Report security bugs in Node.js via [HackerOne](https://hackerone.com/nodejs).
1212

13-
Your report will be acknowledged within 24 hours, and you’ll receive a more
14-
detailed response to your report within 48 hours indicating the next steps in
13+
Your report will be acknowledged within 5 days, and you'll receive a more
14+
detailed response to your report within 10 days indicating the next steps in
1515
handling your submission.
1616

1717
After the initial reply to your report, the security team will endeavor to keep
1818
you informed of the progress being made towards a fix and full announcement,
1919
and may ask for additional information or guidance surrounding the reported
2020
issue.
2121

22-
### Node.js Bug Bounty Program
22+
### Node.js bug bounty program
2323

2424
The Node.js project engages in an official bug bounty program for security
25-
researchers and responsible public disclosures. The program is managed through
25+
researchers and responsible public disclosures. The program is managed through
2626
the HackerOne platform. See <https://hackerone.com/nodejs> for further details.
2727

28-
## Reporting a Bug in a third party module
28+
## Reporting a bug in a third party module
2929

3030
Security bugs in third party modules should be reported to their respective
31-
maintainers and should also be coordinated through the Node.js Ecosystem
32-
Security Team via [HackerOne](https://hackerone.com/nodejs-ecosystem).
31+
maintainers.
3332

34-
Details regarding this process can be found in the
35-
[Security Working Group repository](https://github.com/nodejs/security-wg/tree/main/processes/vuln_db.md).
36-
37-
Thank you for improving the security of Node.js and its ecosystem. Your efforts
38-
and responsible disclosure are greatly appreciated and will be acknowledged.
39-
40-
## Disclosure Policy
33+
## Disclosure policy
4134

4235
Here is the security disclosure policy for Node.js
4336

@@ -62,19 +55,19 @@ Here is the security disclosure policy for Node.js
6255

6356
* This process can take some time, especially when coordination is required
6457
with maintainers of other projects. Every effort will be made to handle the
65-
bug in as timely a manner as possible; however, it’s important that we follow
58+
bug in as timely a manner as possible; however, it's important that we follow
6659
the release process above to ensure that the disclosure is handled in a
6760
consistent manner.
6861

69-
## Receiving Security Updates
62+
## Receiving security updates
7063

7164
Security notifications will be distributed via the following methods.
7265

7366
* <https://groups.google.com/group/nodejs-sec>
7467
* <https://nodejs.org/en/blog/>
7568

76-
## Comments on this Policy
69+
## Comments on this policy
7770

7871
If you have suggestions on how this process could be improved please submit a
79-
[pull request](https://github.com/nodejs/nodejs.dev) or
72+
[pull request](https://github.com/nodejs/nodejs.org) or
8073
[file an issue](https://github.com/nodejs/security-wg/issues/new) to discuss.

0 commit comments

Comments
 (0)