expressjs · github-actions · Oct 6, 2025
@@ -8,7 +8,7 @@ static_files: 정적 파일
 examples: 더 많은 예시
 faq: 자주 묻는 질문(FAQ)
 # Guide
-guide: Gu안내서ide
+guide: 안내서
 routing: 라우팅
 writing_middleware: 미들웨어 작성
 using_middleware: 미들웨어 사용
@@ -44,7 +44,7 @@ changelog: 릴리즈 변경 로그
 # Support
 support: 지원
 # Blog
-blog: Blog
+blog: 블로그
 latest_post: 최신 게시물
 all_posts: 모든 게시물
 write_post: 게시물 작성
@@ -393,15 +393,15 @@ $ npm install serve-favicon morgan method-override express-session body-parser m
 `app.js`를 다음과 같이 변경하십시오.
 
 1. 기본 제공 Express 미들웨어 함수인 `express.favicon`,
-  `express.logger`, `express.methodOverride`,
-  `express.session`, `express.bodyParser` 및
-  `express.errorHandler`는 더 이상 `express`
-  오브젝트에 사용할 수 없습니다. 이들 함수의 대체 함수를 수동으로
-  설치한 후 앱에서 로드해야 합니다.
+   `express.logger`, `express.methodOverride`,
+   `express.session`, `express.bodyParser` 및
+   `express.errorHandler`는 더 이상 `express`
+   오브젝트에 사용할 수 없습니다. 이들 함수의 대체 함수를 수동으로
+   설치한 후 앱에서 로드해야 합니다.
 
 2. `app.router` 함수는 이제 로드할 필요가 없습니다.
-  이 함수는 유효한 Express 4 앱 오브젝트가 아니므로
-  `app.use(app.router);` 코드를 제거하십시오.
+   이 함수는 유효한 Express 4 앱 오브젝트가 아니므로
+   `app.use(app.router);` 코드를 제거하십시오.
 
 3. 미들웨어 함수들이 올바른 순서로 로드되는지 확인하십시오(앱 라우트를 로드한 후 `errorHandler`를 로드).
 

@@ -237,18 +237,18 @@ a future release of Express.
 ### Steps for contributing
 
 1. Create an issue for the
-  bug you want to fix or the feature that you want to add.
+   bug you want to fix or the feature that you want to add.
 2. Create your own fork on GitHub, then
-  checkout your fork.
+   checkout your fork.
 3. Write your code in your local copy. It's good practice to create a branch for
-  each new issue you work on, although not compulsory.
+   each new issue you work on, although not compulsory.
 4. To run the test suite, first install the dependencies by running `npm install`,
-  then run `npm test`.
+   then run `npm test`.
 5. Ensure your code is linted by running `npm run lint` -- fix any issue you
-  see listed.
+   see listed.
 6. If the tests pass, you can commit your changes to your fork and then create
-  a pull request from there. Make sure to reference your issue from the pull
-  request comments by including the issue number e.g. `#123`.
+   a pull request from there. Make sure to reference your issue from the pull
+   request comments by including the issue number e.g. `#123`.
 
 ### Issues which are questions
 
@@ -346,22 +346,22 @@ This is the contribution documentation for the [expressjs.com](https://github.co
 #### Need some ideas? These are some typical issues.
 
 1. **Website issues**: If you see anything on the site that could use a tune-up, think about how to fix it.
-  - Display or screen sizing problems
-  - Mobile responsiveness issues
-  - Missing or broken accessibility features
-  - Website outages
-  - Broken links
-  - Page structure or user interface enhancements
+   - Display or screen sizing problems
+   - Mobile responsiveness issues
+   - Missing or broken accessibility features
+   - Website outages
+   - Broken links
+   - Page structure or user interface enhancements
 
 2. **Content Issues**: Fix anything related to site content or typos.
-  - Spelling errors
-  - Incorrect/outdated Express JS documentation
-  - Missing content
+   - Spelling errors
+   - Incorrect/outdated Express JS documentation
+   - Missing content
 
 3. **Translation Issues**: Fix any translation errors or contribute new content.
-  - Fix spelling errors
-  - Fix incorrect/poorly translated words
-  - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
+   - Fix spelling errors
+   - Fix incorrect/poorly translated words
+   - Check out the [Contributing translations](#contributing-translations) section below for a contributing guide.
 
 #### Want to work on a backlog issue?
 
@@ -384,12 +384,12 @@ The steps below will guide you through the Expressjs.com contribution process.
 So you've found a problem that you want to fix, or have a site enhancement you want to make.
 
 1. If you want to get feedback or discuss, open a discussion [issue](https://github.com/expressjs/expressjs.com/issues/new/choose) prior to starting work. This is not required, but encouraged for larger proposals.
-  - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
-  - 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.
+   - While we highly encourage this step, it is only for submissions proposing significant change. It  helps us to clarify and focus the work, and ensure it aligns with overall project priorities.
+   - 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.
-  - For submissions proposing significant change, we encourage you to follow the review process before starting work.
+   - For submissions proposing significant change, we encourage you to follow the review process before starting work.
 
 #### Step 2: Get the Application Code Base
 
@@ -434,12 +434,12 @@ The Express JS website is built using [Jekyll](https://jekyllrb.com/) and is hos
 Now you'll need a way to see your changes, which means you'll need a running version of the application. You have two options.
 
 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.
+   - 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/).
-  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.
+   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.
 
 ## Contributing translations