Exécuter du JavaScript partout
diff --git a/pages/id/about/get-involved/collab-summit.md b/pages/id/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/id/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/id/about/get-involved/contribute.md b/pages/id/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/id/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/id/about/get-involved/events.mdx b/pages/id/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/id/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/id/about/get-involved/index.md b/pages/id/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/id/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/id/about/governance.md b/pages/id/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/id/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/id/about/index.mdx b/pages/id/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/id/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
+---
+
+# About Node.js®
+
+As an asynchronous event-driven JavaScript runtime, Node.js is designed to build
+scalable network applications. In the following "hello world" example, many
+connections can be handled concurrently. Upon each connection, the callback is
+fired, but if there is no work to be done, Node.js will sleep.
+
+```js
+const http = require('node:http');
+
+const hostname = '127.0.0.1';
+const port = 3000;
+
+const server = http.createServer((req, res) => {
+ res.statusCode = 200;
+ res.setHeader('Content-Type', 'text/plain');
+ res.end('Hello World');
+});
+
+server.listen(port, hostname, () => {
+ console.log(`Server running at http://${hostname}:${port}/`);
+});
+```
+
+This is in contrast to today's more common concurrency model, in which OS threads
+are employed. Thread-based networking is relatively inefficient and very
+difficult to use. Furthermore, users of Node.js are free from worries of
+dead-locking the process, since there are no locks. Almost no function in
+Node.js directly performs I/O, so the process never blocks except when the I/O is performed using
+synchronous methods of Node.js standard library. Because nothing blocks, scalable systems are very
+reasonable to develop in Node.js.
+
+If some of this language is unfamiliar, there is a full article on
+\[Blocking vs. Non-Blocking]\[].
+
+---
+
+Node.js is similar in design to, and influenced by, systems like Ruby's
+\[Event Machine]\[] and Python's \[Twisted]\[]. Node.js takes the event model a bit
+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 event-loop.
+Typically, behavior is defined through callbacks at the beginning of a script, and
+at the end a server is started through a blocking call like `EventMachine::run()`.
+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
+exits the event loop when there are no more callbacks to perform. This behavior
+is like browser JavaScript — the event loop is hidden from the user.
+
+HTTP is a first-class citizen in Node.js, designed with streaming and low
+latency in mind. This makes Node.js well suited for the foundation of a web
+library or framework.
+
+Node.js being designed without threads doesn't mean you can't take
+advantage of multiple cores in your environment. Child processes can be spawned
+by using our \[`child_process.fork()`]\[] API, and are designed to be easy to
+communicate with. Built upon that same interface is the \[`cluster`]\[] module,
+which allows you to share sockets between processes to enable load balancing
+over your cores.
+
+[blocking vs. non-blocking]: /learn/asynchronous-work/overview-of-blocking-vs-non-blocking
+[`child_process.fork()`]: https://nodejs.org/api/child_process.html
+[`cluster`]: https://nodejs.org/api/cluster.html
+[event machine]: https://github.com/eventmachine/eventmachine
+[twisted]: https://twistedmatrix.com/trac/
diff --git a/pages/id/about/previous-releases.mdx b/pages/id/about/previous-releases.mdx
new file mode 100644
index 0000000000000..3b292e56350c5
--- /dev/null
+++ b/pages/id/about/previous-releases.mdx
@@ -0,0 +1,21 @@
+---
+title: Previous Releases
+layout: about
+---
+
+# Previous Releases
+
+Major Node.js versions enter _Current_ release status for six months, which gives library authors time to add support for them.
+After six months, odd-numbered releases (9, 11, etc.) become unsupported, and even-numbered releases (10, 12, etc.) move to _Active LTS_ status and are ready for general use.
+_LTS_ release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
+Production applications should only use _Active LTS_ or _Maintenance LTS_ releases.
+
+### Release Schedule
+
+
+
+Full details regarding Node.js release schedule are available [on GitHub](https://github.com/nodejs/release#release-schedule).
+
+### Looking for latest release of a version branch?
+
+
diff --git a/pages/id/about/security-reporting.mdx b/pages/id/about/security-reporting.mdx
new file mode 100644
index 0000000000000..3ba8e266ed528
--- /dev/null
+++ b/pages/id/about/security-reporting.mdx
@@ -0,0 +1,89 @@
+---
+title: Security Reporting
+layout: about
+---
+
+# Security Reporting
+
+For more details on active Security Policies, checkout [this page](https://github.com/nodejs/node/security/policy).
+
+## Reporting a bug in Node.js
+
+Report security bugs in Node.js via [HackerOne](https://hackerone.com/nodejs).
+
+Your report will be acknowledged within 5 days, and you'll receive a more
+detailed response to your report within 10 days indicating the next steps in
+handling your submission.
+
+After the initial reply to your report, the security team will endeavor to keep
+you informed of the progress being made towards a fix and full announcement,
+and may ask for additional information or guidance surrounding the reported
+issue.
+
+### Node.js bug bounty program
+
+The Node.js project engages in an official bug bounty program for security
+researchers and responsible public disclosures. The program is managed through
+the HackerOne platform. See [https://hackerone.com/nodejs](https://hackerone.com/nodejs) for further details.
+
+## Reporting a bug in a third party module
+
+Security bugs in third party modules should be reported to their respective
+maintainers.
+
+## Disclosure policy
+
+Here is the security disclosure policy for Node.js
+
+- The security report is received and is assigned a primary handler. This
+ person will coordinate the fix and release process. The problem is confirmed
+ and a list of all affected versions is determined. Code is audited to find
+ any potential similar problems. Fixes are prepared for all releases which are
+ still under maintenance. These fixes are not committed to the public
+ repository but rather held locally pending the announcement.
+
+- A suggested embargo date for this vulnerability is chosen and a CVE (Common
+ Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability.
+
+- On the embargo date, the Node.js security mailing list is sent a copy of the
+ announcement. The changes are pushed to the public repository and new builds
+ are deployed to nodejs.org. Within 6 hours of the mailing list being
+ notified, a copy of the advisory will be published on the Node.js blog.
+
+- Typically the embargo date will be set 72 hours from the time the CVE is
+ issued. However, this may vary depending on the severity of the bug or
+ difficulty in applying a fix.
+
+- This process can take some time, especially when coordination is required
+ with maintainers of other projects. Every effort will be made to handle the
+ bug in as timely a manner as possible; however, it's important that we follow
+ the release process above to ensure that the disclosure is handled in a
+ consistent manner.
+
+## Receiving security updates
+
+Security notifications will be distributed via the following methods.
+
+- [Google Group](https://groups.google.com/group/nodejs-sec)
+- [Node.js Blog](/blog)
+
+## Comments on this policy
+
+If you have suggestions on how this process could be improved please submit a
+[pull request](https://github.com/nodejs/nodejs.org) or
+[file an issue](https://github.com/nodejs/security-wg/issues/new) to discuss.
+
+## OpenSSF Best Practices
+
+
+ 
+
+
+The Open Source Security Foundation (OpenSSF) [Best Practices badge](https://github.com/coreinfrastructure/best-practices-badge) is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices. Projects can voluntarily self-certify how they follow each best practice. Consumers of the badge can quickly assess which FLOSS projects are following best practices and as a result are more likely to produce higher-quality secure software.
diff --git a/pages/id/download/current.mdx b/pages/id/download/current.mdx
new file mode 100644
index 0000000000000..34e7ef21b4312
--- /dev/null
+++ b/pages/id/download/current.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ I want the version of Node.js for running
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out all available Node.js download options
+
+
diff --git a/pages/id/download/index.mdx b/pages/id/download/index.mdx
new file mode 100644
index 0000000000000..34e7ef21b4312
--- /dev/null
+++ b/pages/id/download/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ I want the version of Node.js for running
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out all available Node.js download options
+
+
diff --git a/pages/id/download/package-manager/all.md b/pages/id/download/package-manager/all.md
new file mode 100644
index 0000000000000..2e87e99e21fb0
--- /dev/null
+++ b/pages/id/download/package-manager/all.md
@@ -0,0 +1,410 @@
+---
+layout: docs
+title: Installing Node.js via package manager
+---
+
+# Installing Node.js via Package Managers
+
+> The packages on this page are maintained and supported by their respective packagers, **not** the Node.js core team. Please report any issues you encounter to the package maintainer. If it turns out your issue is a bug in Node.js itself, the maintainer will report the issue upstream.
+
+---
+
+- [Alpine Linux](#alpine-linux)
+- [Android](#android)
+- [Arch Linux](#arch-linux)
+- [CentOS, Fedora and Red Hat Enterprise Linux](#centos-fedora-and-red-hat-enterprise-linux)
+- [Debian and Ubuntu based Linux distributions](#debian-and-ubuntu-based-linux-distributions)
+- [fnm](#fnm)
+- [FreeBSD](#freebsd)
+- [Gentoo](#gentoo)
+- [IBM i](#ibm-i)
+- [macOS](#macos)
+- [n](#n)
+- [NetBSD](#netbsd)
+- [Nodenv](#nodenv)
+- [nvm](#nvm)
+- [nvs](#nvs)
+- [OpenBSD](#openbsd)
+- [openSUSE and SLE](#opensuse-and-sle)
+- [SmartOS and illumos](#smartos-and-illumos)
+- [Snap](#snap)
+- [Solus](#solus)
+- [Void Linux](#void-linux)
+- [Windows](#windows-1)
+- [z/OS](#zos)
+
+---
+
+## Alpine Linux
+
+Node.js LTS and npm packages are available in the Main Repository.
+
+```bash
+apk add nodejs npm
+```
+
+Node.js Current can be installed from the Community Repository.
+
+```bash
+apk add nodejs-current
+```
+
+## Android
+
+Android support is still experimental in Node.js, so precompiled binaries are not yet provided by Node.js developers.
+
+However, there are some third-party solutions. For example, [Termux](https://termux.com/) community provides terminal emulator and Linux environment for Android, as well as own package manager and [extensive collection](https://github.com/termux/termux-packages) of many precompiled applications. This command in Termux app will install the last available Node.js version:
+
+```bash
+pkg install nodejs
+```
+
+Currently, Termux Node.js binaries are linked against `system-icu` (depending on `libicu` package).
+
+## Arch Linux
+
+Node.js and npm packages are available in the Community Repository.
+
+```bash
+pacman -S nodejs npm
+```
+
+## CentOS, Fedora and Red Hat Enterprise Linux
+
+Node.js is available as a module called `nodejs` in CentOS/RHEL 8 and Fedora.
+
+```bash
+dnf module install nodejs:
+```
+
+where `` corresponds to the major version of Node.js.
+To see a list of available streams:
+
+```bash
+dnf module list nodejs
+```
+
+For example, to install Node.js 18:
+
+```bash
+dnf module install nodejs:18/common
+```
+
+### Alternatives
+
+These resources provide packages compatible with CentOS, Fedora, and RHEL.
+
+- [Node.js snaps](#snap) maintained and supported at https\://github.com/nodejs/snap
+- [Node.js binary distributions](#debian-and-ubuntu-based-linux-distributions) maintained and supported by [NodeSource](https://github.com/nodesource/distributions)
+
+## Debian and Ubuntu based Linux distributions
+
+[Node.js binary distributions](https://github.com/nodesource/distributions) are available from NodeSource.
+
+### Alternatives
+
+Packages compatible with Debian and Ubuntu based Linux distributions are available via [Node.js snaps](#snap).
+
+## fnm
+
+Fast and simple Node.js version manager built in Rust used to manage multiple released Node.js versions. It allows you to perform operations like install, uninstall, switch Node versions automatically based on the current directory, etc.
+To install fnm, use this [install script](https://github.com/Schniz/fnm#using-a-script-macoslinux).
+
+fnm has cross-platform support (macOS, Windows, Linux) & all popular shells (Bash, Zsh, Fish, PowerShell, Windows Command Line Prompt).
+fnm is built with speed in mind and compatibility support for `.node-version` and `.nvmrc` files.
+
+## FreeBSD
+
+The most recent release of Node.js is available via the [www/node](https://www.freshports.org/www/node) port.
+
+Install a binary package via [pkg](https://www.freebsd.org/cgi/man.cgi?pkg):
+
+```bash
+pkg install node
+```
+
+Or compile it on your own using [ports](https://www.freebsd.org/cgi/man.cgi?ports):
+
+```bash
+cd /usr/ports/www/node && make install
+```
+
+## Gentoo
+
+Node.js is available in the portage tree.
+
+```bash
+emerge nodejs
+```
+
+## IBM i
+
+LTS versions of Node.js are available from IBM, and are available via [the 'yum' package manager](https://ibm.biz/ibmi-rpms). The package name is `nodejs` followed by the major version number (for instance, `nodejs18`, `nodejs20` etc)
+
+To install Node.js 20.x from the command line, run the following as a user with \*ALLOBJ special authority:
+
+```bash
+yum install nodejs20
+```
+
+Node.js can also be installed with the IBM i Access Client Solutions product. See [this support document](http://www-01.ibm.com/support/docview.wss?uid=nas8N1022619) for more details
+
+## macOS
+
+Download the [macOS Installer](/#home-downloadhead) directly from the [nodejs.org](https://nodejs.org/) web site.
+
+_If you want to download the package with bash:_
+
+```bash
+curl "https://nodejs.org/dist/latest/$(curl -s https://nodejs.org/dist/latest/ | grep "pkg" | cut -d'"' -f 2)" -o "$HOME/Downloads/node-latest.pkg" && sudo installer -store -pkg "$HOME/Downloads/node-latest.pkg" -target "/"
+```
+
+### Alternatives
+
+Using **[Homebrew](https://brew.sh/)**:
+
+```bash
+brew install node
+```
+
+Using **[MacPorts](https://www.macports.org/)**:
+
+```bash
+port install nodejs
+
+# Example
+port install nodejs7
+```
+
+Using **[pkgsrc](https://pkgsrc.joyent.com/install-on-macos/)**:
+
+Install the binary package:
+
+```bash
+pkgin -y install nodejs
+```
+
+Or build manually from pkgsrc:
+
+```bash
+cd pkgsrc/lang/nodejs && bmake install
+```
+
+## n
+
+`n` is a simple to use Node.js version manager for Mac and Linux. Specify the target version to install using a rich syntax,
+or select from a menu of previously downloaded versions. The versions are installed system-wide or user-wide, and for more
+targeted use you can run a version directly from the cached downloads.
+
+See the [homepage](https://github.com/tj/n) for install methods (bootstrap, npm, Homebrew, third-party), and all the usage details.
+
+If you already have `npm` then installing `n` and then the newest LTS `node` version is as simple as:
+
+```
+npm install -g n
+n lts
+```
+
+## NetBSD
+
+Node.js is available in the pkgsrc tree:
+
+```bash
+cd /usr/pkgsrc/lang/nodejs && make install
+```
+
+Or install a binary package (if available for your platform) using pkgin:
+
+```bash
+pkgin -y install nodejs
+```
+
+## Nodenv
+
+`nodenv` is a lightweight node version manager, similar to `nvm`. It's simple and predictable. A rich plugin ecosystem lets you tailor it to suit your needs. Use `nodenv` to pick a Node version for your application and guarantee that your development environment matches production.
+
+Nodenv installation instructions are maintained [on its Github page](https://github.com/nodenv/nodenv#installation). Please visit that page to ensure you're following the latest version of the installation steps.
+
+## nvm
+
+Node Version Manager is a bash script used to manage multiple released Node.js versions. It allows
+you to perform operations like install, uninstall, switch version, etc.
+To install nvm, use this [install script](https://github.com/nvm-sh/nvm#install--update-script).
+
+On Unix / OS X systems Node.js built from source can be installed using
+[nvm](https://github.com/creationix/nvm) by installing into the location that nvm expects:
+
+```bash
+env VERSION=`python tools/getnodeversion.py` make install DESTDIR=`nvm_version_path v$VERSION` PREFIX=""
+```
+
+After this you can use `nvm` to switch between released versions and versions
+built from source.
+For example, if the version of Node.js is v8.0.0-pre:
+
+```bash
+nvm use 8
+```
+
+Once the official release is out you will want to uninstall the version built
+from source:
+
+```bash
+nvm uninstall 8
+```
+
+## nvs
+
+#### Windows
+
+The `nvs` version manager is cross-platform and can be used on Windows, macOS, and Unix-like systems
+
+To install `nvs` on Windows go to the [release page](https://github.com/jasongin/nvs/releases) here and download the MSI installer file of the latest release.
+
+You can also use `chocolatey` to install it:
+
+```bash
+choco install nvs
+```
+
+#### macOS,UnixLike
+
+You can find the documentation regarding the installation steps of `nvs` in macOS/Unix-like systems [here](https://github.com/jasongin/nvs/blob/master/doc/SETUP.md#mac-linux)
+
+#### Usage
+
+After this you can use `nvs` to switch between different versions of node.
+
+To add the latest version of node:
+
+```bash
+nvs add latest
+```
+
+Or to add the latest LTS version of node:
+
+```bash
+nvs add lts
+```
+
+Then run the `nvs use` command to add a version of node to your `PATH` for the current shell:
+
+```bash
+$ nvs use lts
+PATH -= %LOCALAPPDATA%\nvs\default
+PATH += %LOCALAPPDATA%\nvs\node\14.17.0\x64
+```
+
+To add it to `PATH` permanently, use `nvs link`:
+
+```bash
+nvs link lts
+```
+
+## OpenBSD
+
+Node.js is available through the ports system.
+
+```bash
+/usr/ports/lang/node
+```
+
+Using [pkg_add](https://man.openbsd.org/OpenBSD-current/man1/pkg_add.1) on OpenBSD:
+
+```bash
+pkg_add node
+```
+
+## openSUSE and SLE
+
+Node.js is available in the main repositories under the following packages:
+
+- **openSUSE Leap 15.2**: `nodejs10`, `nodejs12`, `nodejs14`
+- **openSUSE Tumbleweed**: `nodejs20`
+- **SUSE Linux Enterprise Server (SLES) 12**: `nodejs10`, `nodejs12`, and `nodejs14`
+ (The "Web and Scripting Module" must be [enabled](https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12-SP5/#intro-modulesExtensionsRelated).)
+- **SUSE Linux Enterprise Server (SLES) 15 SP2**: `nodejs10`, `nodejs12`, and `nodejs14`
+ (The "Web and Scripting Module" must be [enabled](https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15/#Intro.Module).)
+
+For example, to install Node.js 14.x on openSUSE Leap 15.2, run the following as root:
+
+```bash
+zypper install nodejs14
+```
+
+Different major versions of Node can be installed and used concurrently.
+
+## SmartOS and illumos
+
+SmartOS images come with pkgsrc pre-installed. On other illumos distributions, first install **[pkgsrc](https://pkgsrc.joyent.com/install-on-illumos/)**, then you may install the binary package as normal:
+
+```bash
+pkgin -y install nodejs
+```
+
+Or build manually from pkgsrc:
+
+```bash
+cd pkgsrc/lang/nodejs && bmake install
+```
+
+## Snap
+
+[Node.js snaps](https://github.com/nodejs/snap) are available as [`node`](https://snapcraft.io/node) on the Snap store.
+
+## Solus
+
+Solus provides Node.js in its main repository.
+
+```bash
+sudo eopkg install nodejs
+```
+
+## Void Linux
+
+Void Linux ships Node.js stable in the main repository.
+
+```bash
+xbps-install -Sy nodejs
+```
+
+## Windows
+
+Download the [Windows Installer](/#home-downloadhead) directly from the [nodejs.org](https://nodejs.org/) web site.
+
+### Alternatives
+
+Using **[Winget](https://aka.ms/winget-cli)**:
+
+```bash
+winget install OpenJS.NodeJS
+# or for LTS
+winget install OpenJS.NodeJS.LTS
+```
+
+After running one of the two commands above, it may be necessary to restart the
+terminal emulator before the `node` CLI command becomes available.
+
+Using **[Chocolatey](https://chocolatey.org/)**:
+
+```bash
+cinst nodejs
+# or for full install with npm
+cinst nodejs.install
+```
+
+Using **[Scoop](https://scoop.sh/)**:
+
+```bash
+scoop install nodejs
+# or for LTS
+scoop install nodejs-lts
+```
+
+## z/OS
+
+IBM® SDK for Node.js - z/OS® is available in two installation formats,
+SMP/E and PAX. Select the installation format that applies to you:
+
+- [Installing and configuring SMP/E edition of Node.js on z/OS](https://www.ibm.com/docs/en/sdk-nodejs-zos/14.0?topic=configuring-installing-smpe-edition)
+- [Installing and configuring PAX edition of Node.js on z/OS](https://www.ibm.com/docs/en/sdk-nodejs-zos/14.0?topic=configuring-installing-pax-edition)
diff --git a/pages/id/download/package-manager/current.mdx b/pages/id/download/package-manager/current.mdx
new file mode 100644
index 0000000000000..e9a55eed2a924
--- /dev/null
+++ b/pages/id/download/package-manager/current.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ Install Node.js on using
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out other community supported package managers
+
+
diff --git a/pages/id/download/package-manager/index.mdx b/pages/id/download/package-manager/index.mdx
new file mode 100644
index 0000000000000..89984b745c29e
--- /dev/null
+++ b/pages/id/download/package-manager/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ Install Node.js on using
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out other community supported package managers
+
+
diff --git a/pages/id/download/prebuilt-binaries/current.mdx b/pages/id/download/prebuilt-binaries/current.mdx
new file mode 100644
index 0000000000000..e38141bb4befc
--- /dev/null
+++ b/pages/id/download/prebuilt-binaries/current.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ I want the version of Node.js for running
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out Nightly prebuilt binaries or Unofficial Builds for other platforms
+
+
diff --git a/pages/id/download/prebuilt-binaries/index.mdx b/pages/id/download/prebuilt-binaries/index.mdx
new file mode 100644
index 0000000000000..e38141bb4befc
--- /dev/null
+++ b/pages/id/download/prebuilt-binaries/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ I want the version of Node.js for running
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out Nightly prebuilt binaries or Unofficial Builds for other platforms
+
+
diff --git a/pages/id/download/source-code/current.mdx b/pages/id/download/source-code/current.mdx
new file mode 100644
index 0000000000000..17383ba65eb3e
--- /dev/null
+++ b/pages/id/download/source-code/current.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ I want the version of the Node.js source code.
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out how to build Node.js from source.
+
+
diff --git a/pages/id/download/source-code/index.mdx b/pages/id/download/source-code/index.mdx
new file mode 100644
index 0000000000000..17383ba65eb3e
--- /dev/null
+++ b/pages/id/download/source-code/index.mdx
@@ -0,0 +1,22 @@
+---
+layout: download
+title: Download Node.js®
+subtitle: Download Node.js the way you want.
+---
+
+
+ I want the version of the Node.js source code.
+
+
+
+
+
+ Node.js includes npm () and corepack.
+
+Read the blog post for this version
+
+Learn how to verify signed SHASUMS
+
+Check out how to build Node.js from source.
+
+
diff --git a/pages/id/index.mdx b/pages/id/index.mdx
new file mode 100644
index 0000000000000..deb5105a79505
--- /dev/null
+++ b/pages/id/index.mdx
@@ -0,0 +1,121 @@
+---
+title: Run JavaScript Everywhere
+layout: home
+---
+
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/id/search.mdx b/pages/id/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/id/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/it/about/get-involved/collab-summit.md b/pages/it/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/it/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/it/about/get-involved/contribute.md b/pages/it/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/it/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/it/about/get-involved/events.mdx b/pages/it/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/it/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/it/about/get-involved/index.md b/pages/it/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/it/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/it/about/governance.md b/pages/it/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/it/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/it/about/index.mdx b/pages/it/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/it/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/it/search.mdx b/pages/it/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/it/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/ja/about/get-involved/collab-summit.md b/pages/ja/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/ja/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/ja/about/get-involved/contribute.md b/pages/ja/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/ja/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/ja/about/get-involved/events.mdx b/pages/ja/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/ja/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/ja/about/get-involved/index.md b/pages/ja/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/ja/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/ja/about/governance.md b/pages/ja/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/ja/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/ja/about/index.mdx b/pages/ja/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/ja/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/ja/search.mdx b/pages/ja/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/ja/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/ka/about/get-involved/collab-summit.md b/pages/ka/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/ka/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/ka/about/get-involved/contribute.md b/pages/ka/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/ka/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/ka/about/get-involved/events.mdx b/pages/ka/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/ka/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/ka/about/get-involved/index.md b/pages/ka/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/ka/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/ka/about/governance.md b/pages/ka/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/ka/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/ka/about/index.mdx b/pages/ka/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/ka/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/ka/search.mdx b/pages/ka/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/ka/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/ko/about/get-involved/collab-summit.md b/pages/ko/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/ko/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/ko/about/get-involved/contribute.md b/pages/ko/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/ko/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/ko/about/get-involved/events.mdx b/pages/ko/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/ko/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/ko/about/get-involved/index.md b/pages/ko/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/ko/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/ko/about/governance.md b/pages/ko/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/ko/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/ko/about/index.mdx b/pages/ko/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/ko/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/ko/search.mdx b/pages/ko/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/ko/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/pt-br/about/get-involved/collab-summit.md b/pages/pt-br/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/pt-br/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/pt-br/about/get-involved/contribute.md b/pages/pt-br/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/pt-br/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/pt-br/about/get-involved/events.mdx b/pages/pt-br/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/pt-br/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/pt-br/about/get-involved/index.md b/pages/pt-br/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/pt-br/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/pt-br/about/governance.md b/pages/pt-br/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/pt-br/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/pt-br/about/index.mdx b/pages/pt-br/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/pt-br/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/pt-br/search.mdx b/pages/pt-br/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/pt-br/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/ru/about/get-involved/collab-summit.md b/pages/ru/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/ru/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/ru/about/get-involved/contribute.md b/pages/ru/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/ru/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/ru/about/get-involved/events.mdx b/pages/ru/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/ru/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/ru/about/get-involved/index.md b/pages/ru/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/ru/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/ru/about/governance.md b/pages/ru/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/ru/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/ru/about/index.mdx b/pages/ru/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/ru/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/ru/search.mdx b/pages/ru/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/ru/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/tr/about/get-involved/collab-summit.md b/pages/tr/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..ac5f3146404c0
--- /dev/null
+++ b/pages/tr/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: İşbirlikçi Zirvesi
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/tr/about/get-involved/contribute.md b/pages/tr/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/tr/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/tr/about/get-involved/events.mdx b/pages/tr/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/tr/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/tr/about/get-involved/index.md b/pages/tr/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/tr/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/tr/about/governance.md b/pages/tr/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/tr/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/tr/about/index.mdx b/pages/tr/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/tr/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/tr/search.mdx b/pages/tr/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/tr/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/uk/about/get-involved/collab-summit.md b/pages/uk/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/uk/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/uk/about/get-involved/contribute.md b/pages/uk/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/uk/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/uk/about/get-involved/events.mdx b/pages/uk/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/uk/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/uk/about/get-involved/index.md b/pages/uk/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/uk/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/uk/about/governance.md b/pages/uk/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/uk/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/uk/about/index.mdx b/pages/uk/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/uk/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/uk/search.mdx b/pages/uk/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/uk/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/vi/about/get-involved/collab-summit.md b/pages/vi/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/vi/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/vi/about/get-involved/contribute.md b/pages/vi/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/vi/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/vi/about/get-involved/events.mdx b/pages/vi/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/vi/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/vi/about/get-involved/index.md b/pages/vi/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/vi/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/vi/about/governance.md b/pages/vi/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/vi/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/vi/about/index.mdx b/pages/vi/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/vi/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/vi/search.mdx b/pages/vi/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/vi/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+
diff --git a/pages/zh-cn/about/get-involved/collab-summit.md b/pages/zh-cn/about/get-involved/collab-summit.md
new file mode 100644
index 0000000000000..d8b152d0a2723
--- /dev/null
+++ b/pages/zh-cn/about/get-involved/collab-summit.md
@@ -0,0 +1,30 @@
+---
+title: Collab Summit
+layout: about
+---
+
+# Collaborator Summit
+
+Node.js's Collaborator Summit is an un-conference for bringing current and
+potential contributors together to discuss Node.js with lively collaboration,
+education, and knowledge sharing. Committees and working groups come together
+twice per year to make important decisions while also being able to work on some
+exciting efforts they want to push forward in-person.
+
+## Who attends?
+
+Anyone is welcome to attend Collab Summit. During the
+summit, leaders will help onboard new contributors to groups they'd love to help
+prior to integrating them into the working sessions.
+
+This is your opportunity to learn what is happening within the community to jump
+in and contribute with the skills you have and would like to hone.
+
+Working groups will put together a schedule so that people can
+familiarize themselves before folks get onsite, having the general collaborator
+discussions, and then dive into breakout sessions.
+
+We'd love to see you at Collab Summit! Check out the [Summit repo](https://github.com/nodejs/summit)
+for upcoming and past Collab Summits and have a look at the
+[issues filed](https://github.com/nodejs/summit/issues) that share what
+individual working groups and committees are looking to discuss in-person.
diff --git a/pages/zh-cn/about/get-involved/contribute.md b/pages/zh-cn/about/get-involved/contribute.md
new file mode 100644
index 0000000000000..6392c5fe32cb5
--- /dev/null
+++ b/pages/zh-cn/about/get-involved/contribute.md
@@ -0,0 +1,47 @@
+---
+title: Contributing
+layout: about
+---
+
+# Contributing
+
+Thank you for your interest in contributing to Node.js! There are multiple ways and places you can contribute, and we're here to help facilitate that.
+
+## Asking for General Help
+
+Because the level of activity in the `nodejs/node` repository is so high, questions or requests for general help using Node.js should be directed at the [Node.js help repository](https://github.com/nodejs/help/issues).
+
+## Reporting an Issue
+
+If you have found what you believe to be an issue with Node.js please do not hesitate to file an issue on the GitHub project. When filing your issue please make sure you can express the issue with a reproducible test case, and that test case should not include any external dependencies. That is to say, the test case can be executed without anything more than Node.js itself.
+
+When reporting an issue we also need as much information about your environment that you can include. We never know what information will be pertinent when trying to narrow down the issue. Please include at least the following information:
+
+- Version of Node.js
+- Platform you're running on (macOS, SmartOS, Linux, Windows)
+- Architecture you're running on (32bit or 64bit and x86 or ARM)
+
+The Node.js project is currently managed across a number of separate GitHub repositories, each with their own separate issues database. If possible, please direct any issues you are reporting to the appropriate repository but don't worry if things happen to get put in the wrong place, the community of contributors will be more than happy to help get you pointed in the right direction.
+
+- To report issues specific to Node.js, please use [nodejs/node](https://github.com/nodejs/node)
+- To report issues specific to this website, please use [nodejs/nodejs.org](https://github.com/nodejs/nodejs.org/issues)
+
+## Code contributions
+
+If you'd like to fix bugs or add a new feature to Node.js, please make sure you consult the [Node.js Contribution Guidelines](https://github.com/nodejs/node/blob/main/CONTRIBUTING.md/#pull-requests). The review process by existing collaborators for all contributions to the project is explained there as well.
+
+If you are wondering how to start, you can check [Node Todo](https://www.nodetodo.org/) which may guide you towards your first contribution.
+
+## Becoming a collaborator
+
+By becoming a collaborator, contributors can have even more impact on the project. They can help other contributors by reviewing their contributions, triage issues and take an even bigger part in shaping the project's future. Individuals identified by the TSC as making significant and valuable contributions across any Node.js repository may be made Collaborators and given commit access to the project. Activities taken into consideration include (but are not limited to) the quality of:
+
+- code commits and pull requests
+- documentation commits and pull requests
+- comments on issues and pull requests
+- contributions to the Node.js website
+- assistance provided to end users and novice contributors
+- participation in working groups
+- other participation in the wider Node.js community
+
+If individuals making valuable contributions do not believe they have been considered for commit access, they may [log an issue](https://github.com/nodejs/TSC/issues) or [contact a TSC member](https://github.com/nodejs/node#tsc-technical-steering-committee) directly.
diff --git a/pages/zh-cn/about/get-involved/events.mdx b/pages/zh-cn/about/get-involved/events.mdx
new file mode 100644
index 0000000000000..2fb8672daed2d
--- /dev/null
+++ b/pages/zh-cn/about/get-involved/events.mdx
@@ -0,0 +1,16 @@
+---
+title: Upcoming Events
+layout: about
+---
+
+## Upcoming Events
+
+Node.js events are open and available to the public. Anyone is welcome to join and participate.
+
+### Upcoming Node.js® Meetings
+
+The Node.js project holds numerous meetings throughout the year to discuss and plan aspects of the project.
+
+The following meetings are upcoming in the next 7 days.
+
+
diff --git a/pages/zh-cn/about/get-involved/index.md b/pages/zh-cn/about/get-involved/index.md
new file mode 100644
index 0000000000000..858bfc61901b2
--- /dev/null
+++ b/pages/zh-cn/about/get-involved/index.md
@@ -0,0 +1,26 @@
+---
+title: Get involved
+layout: about
+---
+
+# Get Involved
+
+## Community Discussion
+
+- The [GitHub issues list](https://github.com/nodejs/node/issues) is the place for discussion of Node.js core features.
+- For real-time chat about Node.js development use one of the platforms below
+ - For IRC, go to `irc.libera.chat` in the `#node.js` channel with an [IRC client](https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients) or connect in your web browser to the channel using [a web client](https://kiwiirc.com/nextclient/)
+ - For Slack, there are two options:
+ - The [OpenJSF Slack](https://slack-invite.openjsf.org/) is a Foundation run Slack with several Node.js channels (channels prefixed by `#nodejs-` are related to the project).
+ - [Node Slackers](https://www.nodeslackers.com/) is a Node.js-focused Slack community.
+- The official Node.js Twitter account is [nodejs](https://twitter.com/nodejs).
+- The [Node.js project calendar](https://nodejs.org/calendar) with all public team meetings.
+
+## Learning
+
+- [Official Learn section](https://nodejs.org/en/learn/) of the Node.js website.
+- [Official API reference documentation](https://nodejs.org/api/).
+- [NodeSchool.io](https://nodeschool.io/) will teach you Node.js concepts via interactive command-line games.
+- [Stack Overflow Node.js tag](https://stackoverflow.com/questions/tagged/node.js) collects new information every day.
+- [The DEV Community Node.js tag](https://dev.to/t/node) is a place to share Node.js projects, articles and tutorials as well as start discussions and ask for feedback on Node.js-related topics. Developers of all skill-levels are welcome to take part.
+- [Nodeiflux](https://discordapp.com/invite/vUsrbjd) is a friendly community of Node.js backend developers supporting each other on Discord.
diff --git a/pages/zh-cn/about/governance.md b/pages/zh-cn/about/governance.md
new file mode 100644
index 0000000000000..af512bbe769d3
--- /dev/null
+++ b/pages/zh-cn/about/governance.md
@@ -0,0 +1,35 @@
+---
+title: Project Governance
+layout: about
+---
+
+# Project Governance
+
+## Consensus Seeking Process
+
+The Node.js project follows a [Consensus Seeking][] decision making model.
+
+## Collaborators
+
+The [nodejs/node][] core GitHub repository is maintained by the Collaborators
+who are added by the Technical Steering Committee ([TSC][]) on an ongoing basis.
+
+Individuals making significant and valuable contributions are made Collaborators
+and given commit-access to the project. These individuals are identified by the
+TSC and their nomination is discussed with the existing Collaborators.
+
+For the current list of Collaborators, see the project's [README.md][].
+
+A guide for Collaborators is maintained at [collaborator-guide.md][].
+
+## Technical Steering Committee
+
+The project is governed by the [Technical Steering Committee (TSC)][]
+which is responsible for high-level guidance of the project.
+
+[consensus seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
+[readme.md]: https://github.com/nodejs/node/blob/main/README.md#current-project-team-members
+[tsc]: https://github.com/nodejs/TSC
+[technical steering committee (tsc)]: https://github.com/nodejs/TSC/blob/main/TSC-Charter.md
+[collaborator-guide.md]: https://github.com/nodejs/node/blob/main/doc/contributing/collaborator-guide.md
+[nodejs/node]: https://github.com/nodejs/node
diff --git a/pages/zh-cn/about/index.mdx b/pages/zh-cn/about/index.mdx
new file mode 100644
index 0000000000000..13459154c71d4
--- /dev/null
+++ b/pages/zh-cn/about/index.mdx
@@ -0,0 +1,78 @@
+---
+title: About Node.js®
+layout: about
+---
+
+
+
+
+
Run JavaScript Everywhere
+
+ Node.js® is a free, open-source, cross-platform JavaScript runtime
+ environment that lets developers create servers, web apps,
+ command line tools and scripts.
+
+
+
+
+
+ {({ release }) => (
+ <>
+ Download Node.js (LTS)
+
+ Downloads Node.js {release.versionWithPrefix}
+ 1 with long-term support.
+ Node.js can also be installed via package managers.
+
+
+ )}
+
+
+
+ {({ release }) => (
+
+ Want new features sooner?
+ Get Node.js {release.versionWithPrefix}
+ 1 instead.
+
+ )}
+
+
+
+ ```js displayName="Create an HTTP Server"
+ import { createServer } from 'node:http';
+
+ const server = createServer((req, res) => {
+ res.writeHead(200, { 'Content-Type': 'text/plain' });
+ res.end('Hello World!\n');
+ });
+
+ // starts a simple http server locally on port 3000
+ server.listen(3000, '127.0.0.1', () => {
+ console.log('Listening on 127.0.0.1:3000');
+ });
+ ```
+
+ ```js displayName="Write Tests"
+ import assert from 'node:assert';
+ import test from 'node:test';
+
+ test('that 1 is equal 1', () => {
+ assert.strictEqual(1, 1);
+ });
+
+ test('that throws as 1 is not equal 2', () => {
+ // throws an exception because 1 != 2
+ assert.strictEqual(1, 2);
+ });
+ ```
+
+ ```js displayName="Read and Hash a File"
+ import { createHash } from 'node:crypto';
+ import { readFile } from 'node:fs/promises';
+
+ const hasher = createHash('sha1');
+ const fileContent = await readFile('./package.json');
+
+ hasher.setEncoding('hex');
+ hasher.write(fileContent);
+ hasher.end();
+
+ const fileHash = hasher.read();
+ ```
+
+ ```js displayName="Read Streams"
+ import { createReadStream, createWriteStream } from 'node:fs';
+
+ const res = await fetch('https://nodejs.org/dist/index.json');
+ const json = await res.json(); // yields a json object
+
+ const readableStream = createReadStream('./package.json');
+ const writableStream = createWriteStream('./package2.json');
+
+ readableStream.setEncoding('utf8');
+
+ readableStream.on('data', chunk => writableStream.write(chunk));
+ ```
+
+ ```js displayName="Work with Threads"
+ import { Worker, isMainThread,
+ workerData, parentPort } from 'node:worker_threads';
+
+ if (isMainThread) {
+ const data = 'some data';
+ const worker = new Worker(import.meta.filename, { workerData: data });
+ worker.on('message', msg => console.log('Reply from Thread:', msg));
+ } else {
+ const source = workerData;
+ parentPort.postMessage(btoa(source.toUpperCase()));
+ }
+ ```
+
+
+
+Learn more what Node.js is able to offer with our [Learning materials](/learn).
+
+
diff --git a/pages/zh-cn/search.mdx b/pages/zh-cn/search.mdx
new file mode 100644
index 0000000000000..ac57c0e414803
--- /dev/null
+++ b/pages/zh-cn/search.mdx
@@ -0,0 +1,6 @@
+---
+layout: search
+title: Search Results
+---
+
+