amirho/expressjs.com
1
0
Fork 0
mirror of https://github.com/expressjs/expressjs.com.git synced 2026-02-21 19:41:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

i18n: new crowdin translations (#2145)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
github-actions[bot]
2026-01-04 12:50:29 -05:00
committed by GitHub
parent bb00d0c196
commit a8bc26cc73
18 changed files with 98 additions and 102 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
de/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>Überblick</h2>
_Middlewarefunktionen_ sind Funktionen, die Zugriff auf das [Anforderungsobjekt](/{{ page.lang }}/5x/api.html#req) (`req`), das [Antwortobjekt](/{{ page.lang }}/5x/api.html#res) (`res`) und die nächste Middlewarefunktion im Anforderung/Antwort-Zyklus der Anwendung haben. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. Die nächste Middlewarefunktion wird im Allgemeinen durch die Variable `next` bezeichnet.
Über Middlewarefunktionen lassen sich die folgenden Tasks ausführen:
@@ -38,9 +38,9 @@ Das folgende Beispiel zeigt die Elemente eines Middlewarefunktionsaufrufs:
<div class="callout" id="callout4">Callback-Argument zur Middlewarefunktion, die nach der geltenden Konvention als "next" bezeichnet wird.</div>
<div class="callout" id="callout5">HTTP-<a href="../5x/api.html#res">Antwort</a>argument zur Middlewarefunktion, die nach der geltenden Konvention als "res" bezeichnet wird.</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">HTTP-<a href="../5x/api.html#req">Anforderungs</a>argument zur Middlewarefunktion, die nach der geltenden Konvention als "req" bezeichnet wird.</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
de/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

6
es/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>Overview</h2>
Las funciones de _middleware_ son funciones que tienen acceso al [objeto de solicitud](/{{ page.lang }}/5x/api.html#req) (`req`), al [objeto de respuesta](/{{ page.lang }}/5x/api.html#res) (`res`) y a la siguiente función de middleware en el ciclo de solicitud/respuestas de la aplicación. La siguiente función de middleware se denota normalmente con una variable denominada `next`.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La siguiente función de middleware se denota normalmente con una variable denominada `next`.
Las funciones de middleware pueden realizar las siguientes tareas:
@@ -38,9 +38,9 @@ El siguiente ejemplo muestra los elementos de una llamada a función de middlewa
<div class="callout" id="callout4">Argumento de devolución de llamada a la función de middleware, denominado "next" por convención.</div>
<div class="callout" id="callout5">Argumento de <a href="../5x/api.html#res">respuesta</a> HTTP a la función de middleware, denominado "res" por convención.</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">Argumento de <a href="../5x/api.html#req">solicitud</a> HTTP a la función de middleware, denominado "req" por convención.</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
es/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

6
fr/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>Présentation</h2>
Les fonctions de _middleware_ sont des fonctions qui peuvent accéder à l'[objet Request](/{{ page.lang }}/5x/api.html#req) (`req`), l'[objet response](/{{ page.lang }}/5x/api.html#res) (`res`) et à la fonction middleware suivant dans le cycle demande-réponse de l'application. La fonction middleware suivant est couramment désignée par une variable nommée `next`.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La fonction middleware suivant est couramment désignée par une variable nommée `next`.
Les fonctions middleware effectuent les tâches suivantes :
@@ -38,9 +38,9 @@ L'exemple suivant montre les éléments d'un appel de fonction middleware:
<div class="callout" id="callout4">Argument de rappel à la fonction middleware, appelée "next" par convention.</div>
<div class="callout" id="callout5">Argument de <a href="../5x/api.html#res">réponse</a> HTTP à la fonction middleware, appelé "res" par convention.</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">Argument de <a href="../5x/api.html#req">demande</a> HTTP à la fonction middleware, appelé "req" par convention.</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
fr/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

6
it/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>Panoramica</h2>
Le funzioni _middleware_ sono funzioni con accesso all'[oggetto richiesta](/{{ page.lang }}/5x/api.html#req) (`req`), all'[oggetto risposta](/{{ page.lang }}/5x/api.html#res) (`res`) e alla successiva funzione middleware nel ciclo richiesta-risposta dell'applicazione. La successiva funzione middleware viene comunemente denotata da una variabile denominata `next`.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. La successiva funzione middleware viene comunemente denotata da una variabile denominata `next`.
Le funzioni middleware possono eseguire le attività elencate di seguito:
@@ -38,9 +38,9 @@ I seguenti esempi mostrano gli elementi di una chiamata alla funzione middleware
<div class="callout" id="callout4">Argomento di callback nella funzione middleware, denominata per convenzione "next".</div>
<div class="callout" id="callout5">Argomento <a href="../5x/api.html#res">risposta</a> HTTP nella funzione middleware, denominato "res" per convenzione.</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">Argomento <a href="../5x/api.html#req">richiesta</a> HTTP nella funzione middleware, denominato "req" per convenzione.</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
it/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

6
ja/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>概説</h2>
_ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ page.lang }}/5x/api.html#req) (`req`)、[レスポンスオブジェクト](/{{ page.lang }}/5x/api.html#res) (`res`)、およびアプリケーションのリクエストレスポンスサイクルにおける次のミドルウェア関数に対するアクセス権限を持つ関数です。次のミドルウェア関数は一般的に、`next` という変数で表されます。 The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
ミドルウェア関数は以下のタスクを実行できます。
@@ -38,9 +38,9 @@ _ミドルウェア_ 関数は、[リクエストオブジェクト](/{{ page.la
<div class="callout" id="callout4">ミドルウェア関数へのコールバック引数 (慣習的に「next」と呼ばれます)。</div>
<div class="callout" id="callout5">ミドルウェア関数への HTTP <a href="../5x/api.html#res">レスポンス</a>引数 (慣習的に「res」と呼ばれます)。</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">ミドルウェア関数への HTTP <a href="../5x/api.html#req">リクエスト</a>引数 (慣習的に「req」と呼ばれます)。</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
ja/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

6
ko/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>개요</h2>
_미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/5x/api.html#req)(`req`), [응답 오브젝트](/{{ page.lang }}/5x/api.html#res) (`res`), 그리고 애플리케이션의 요청-응답 주기 중 그 다음의 미들웨어 함수 대한 액세스 권한을 갖는 함수입니다. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. 그 다음의 미들웨어 함수는 일반적으로 `next`라는 이름의 변수로 표시됩니다.
미들웨어 함수는 다음과 같은 태스크를 수행할 수 있습니다.
@@ -38,9 +38,9 @@ _미들웨어_ 함수는 [요청 오브젝트](/{{ page.lang }}/5x/api.html#req)
<div class="callout" id="callout4">미들웨어 함수에 대한 콜백 인수(일반적으로 "next"라 불림).</div>
<div class="callout" id="callout5">미들웨어 함수에 대한 HTTP <a href="../5x/api.html#res">응답</a> 인수(일반적으로 "res"라 불림).</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">미들웨어 함수에 대한 HTTP <a href="../5x/api.html#req">요청</a> 인수(일반적으로 "req"라 불림).</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
ko/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

10
pt-br/guide/writing-middleware.md
View File

@@ -11,11 +11,7 @@ redirect_from: " "
<h2>Visão Geral</h2>
Funções de _Middleware_ são funções que tem acesso
ao [objeto de solicitação](/{{ page.lang }}/5x/api.html#req)
(`req`), o [objeto de resposta](/{{ page.lang }}/5x/api.html#res)
(`res`), e a próxima função de middleware no ciclo
solicitação-resposta do aplicativo. A próxima função middleware é
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. A próxima função middleware é
comumente denotada por uma variável chamada `next`.
Funções de middleware podem executar as seguintes tarefas:
@@ -46,9 +42,9 @@ O exemplo a seguir mostra os elementos de uma chamada de função de middleware:
<div class="callout" id="callout4">Argumento de retorno de chamada para a função de middleware, chamado de "next" por convenção.</div>
<div class="callout" id="callout5">Argumento de <a href="../5x/api.html#res">resposta</a> HTTP para a função de middleware, chamado de "res" por convenção.</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">Argumento de <a href="../5x/api.html#req">solicitação</a> HTTP para a função de middleware, chamado de "req" por convenção.</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
pt-br/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

6
zh-cn/guide/writing-middleware.md
View File

@@ -11,7 +11,7 @@ redirect_from: " "
<h2>概述</h2>
_中间件_函数能够访问[请求对象](/{{ page.lang }}/5x/api.html#req) (`req`)、[响应对象](/{{ page.lang }}/5x/api.html#res) (`res`) 以及应用程序的请求/响应循环中的下一个中间件函数。下一个中间件函数通常由名为 `next` 的变量来表示。 The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
_Middleware_ functions are functions that have access to the [request object](/{{ page.lang }}/5x/api.html#req) (`req`), the [response object](/{{ page.lang }}/5x/api.html#res) (`res`), and the `next` function in the application's request-response cycle. The `next` function is a function in the Express router which, when invoked, executes the middleware succeeding the current middleware.
中间件函数可以执行以下任务：
@@ -38,9 +38,9 @@ _中间件_函数能够访问[请求对象](/{{ page.lang }}/5x/api.html#req) (`
<div class="callout" id="callout4">中间件函数的回调自变量，按约定称为“next”。</div>
<div class="callout" id="callout5">中间件函数的 HTTP <a href="../5x/api.html#res">响应</a>自变量，按约定称为“res”。</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">中间件函数的 HTTP <a href="../5x/api.html#req">请求</a>自变量，按约定称为“req”。</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
zh-cn/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)

4
zh-tw/guide/writing-middleware.md
View File

@@ -38,9 +38,9 @@ The following figure shows the elements of a middleware function call:
<div class="callout" id="callout4">中介軟體函數的回呼引數，依慣例，稱為 "next"。</div>
<div class="callout" id="callout5">中介軟體函數的 HTTP <a href="../5x/api.html#res">response</a> 引數，依慣例，稱為 "res"。</div>
<div class="callout" id="callout5">HTTP <a href="/{{ page.lang }}/5x/api.html#res">response</a> argument to the middleware function, called "res" by convention.</div>
<div class="callout" id="callout6">中介軟體函數的 HTTP <a href="../5x/api.html#req">request</a> 引數，依慣例，稱為 "req"。</div>
<div class="callout" id="callout6">HTTP <a href="/{{ page.lang }}/5x/api.html#req">request</a> argument to the middleware function, called "req" by convention.</div>
</td></tr>
</table>
</div>

16
zh-tw/resources/contributing.md
View File

@@ -360,7 +360,7 @@ pull request.
<!-- LOCAL: expressjs/expressjs.com ../../CONTRIBUTING.md -->
### The Official Documentation of the Express JS Framework
### The Official Documentation of the Express.js Framework
This is the contribution documentation for the [expressjs.com](https://github.com/expressjs/expressjs.com) website.
@@ -376,7 +376,7 @@ This is the contribution documentation for the [expressjs.com](https://github.co
2. **Content Issues**: Fix anything related to site content or typos.
- Spelling errors
- Incorrect/outdated Express JS documentation
- Incorrect/outdated Express.js documentation
- Missing content
3. **Translation Issues**: Fix any translation errors or contribute new content.
@@ -394,7 +394,7 @@ If you've found a bug or a typo, or if you have an idea for an enhancement, you
- Submit a [new issue](https://github.com/expressjs/expressjs.com/issues/new/choose) on our repo. Do this for larger proposals, or if you'd like to discuss or get feedback first.
- Make a [Github pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work and it's ready to go, feel free to send it our way.
- Make a [GitHub pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). If you have already done work, and it's ready to go, feel free to send it our way.
## Getting Started
@@ -409,7 +409,7 @@ So you've found a problem that you want to fix, or have a site enhancement you w
- For submissions proposing minor improvements or corrections, this is not needed. You can skip this step.
- When opening an issue please give it a title and fill in the description section. The more details you provide, the more feedback we can give.
2. After receiving your issue the Express JS documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
2. After receiving your issue the Express.js documentation team will respond with feedback. We read every submission and always try to respond quickly with feedback.
- For submissions proposing significant change, we encourage you to follow the review process before starting work.
#### Step 2: Get the Application Code Base
@@ -448,7 +448,7 @@ But just in case you need a little extra explanation, this section below outline
- All css and js files are kept in `css` and `js` folders on the project root.
The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [Github Pages](https://pages.github.com/).
The Express.js website is built using [Jekyll](https://jekyllrb.com/) and is hosted on [GitHub Pages](https://pages.github.com/).
#### Step 3: Running the Application
@@ -457,10 +457,10 @@ Now you'll need a way to see your changes, which means you'll need a running ver
1. **Run Locally**: This gets the local version of the application up and running on your machine. Follow our [Local Setup Guide](https://github.com/expressjs/expressjs.com?tab=readme-ov-file#build-the-website-locally) to use this option.
- This is the recommended option for moderate to complex work.
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/site-deploys/deploy-previews/).
2. **Run using Deploy Preview**: Use this option if you don't want to bother with a local installation. Part of our continuous integration pipeline includes [Netlify Deploy Preview](https://docs.netlify.com/deploy/deploy-types/deploy-previews/).
1. To use this you'll need to get your changes online - after you've made your first commit on your feature branch, make a _draft_ pull request.
2. After the build steps are complete, you'll have access to a **Deploy Preview** tab that will run your changes on the web, rebuilding after each commit is pushed.
3. After you are completely done your work and it's ready for review, remove the draft status on your pull request and submit your work.
3. After you are completely done your work, and it's ready for review, remove the draft status on your pull request and submit your work.
## Contributing translations
@@ -482,6 +482,6 @@ The documentation is translated into these languages:
### How to translate
1. Request to join the Express.js Website project on [Crowdin](https://express.crowdin.com/website)
2. [Select the language you want to translate](https://support.crowdin.com/joining-translation-project/#starting-translation)
2. [Select the language you want to translate](https://support.crowdin.com/for-translators/#starting-translation)
3. [Start translating](https://support.crowdin.com/online-editor/)