From ca1de1bd692d03517ece65fa8e21dc553b78cb9d Mon Sep 17 00:00:00 2001 From: camperbot Date: Fri, 26 May 2023 21:51:43 +0530 Subject: [PATCH] chore(i18n,docs): processed translations (#50523) --- docs/i18n/chinese-traditional/FAQ.md | 56 ++-- docs/i18n/chinese-traditional/_sidebar.md | 4 +- docs/i18n/chinese-traditional/devops.md | 8 +- .../how-to-enable-new-languages.md | 2 +- ...o-setup-freecodecamp-mobile-app-locally.md | 6 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 4 + .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 10 +- .../how-to-work-on-the-docs-theme.md | 6 +- .../chinese-traditional/moderator-handbook.md | 245 +----------------- .../chinese-traditional/reply-templates.md | 232 +++++++++++++++++ .../security-hall-of-fame.md | 2 +- docs/i18n/chinese/FAQ.md | 56 ++-- docs/i18n/chinese/_sidebar.md | 4 +- docs/i18n/chinese/devops.md | 8 +- .../chinese/how-to-enable-new-languages.md | 2 +- ...o-setup-freecodecamp-mobile-app-locally.md | 6 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 4 + .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 10 +- .../chinese/how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/chinese/moderator-handbook.md | 245 +----------------- docs/i18n/chinese/reply-templates.md | 232 +++++++++++++++++ docs/i18n/chinese/security-hall-of-fame.md | 2 +- docs/i18n/espanol/FAQ.md | 90 ++++--- docs/i18n/espanol/_sidebar.md | 38 +-- docs/i18n/espanol/devops.md | 8 +- .../espanol/how-to-enable-new-languages.md | 6 +- ...o-setup-freecodecamp-mobile-app-locally.md | 12 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 10 +- .../espanol/how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/espanol/moderator-handbook.md | 245 +----------------- docs/i18n/espanol/reply-templates.md | 232 +++++++++++++++++ docs/i18n/espanol/security-hall-of-fame.md | 2 +- docs/i18n/german/FAQ.md | 88 ++++--- docs/i18n/german/_sidebar.md | 14 +- docs/i18n/german/devops.md | 8 +- .../german/how-to-enable-new-languages.md | 16 +- ...o-setup-freecodecamp-mobile-app-locally.md | 12 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 10 +- .../german/how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/german/moderator-handbook.md | 245 +----------------- docs/i18n/german/reply-templates.md | 232 +++++++++++++++++ docs/i18n/german/security-hall-of-fame.md | 2 +- docs/i18n/italian/FAQ.md | 92 +++---- docs/i18n/italian/_sidebar.md | 38 +-- docs/i18n/italian/devops.md | 8 +- .../italian/how-to-enable-new-languages.md | 18 +- ...o-setup-freecodecamp-mobile-app-locally.md | 12 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 12 +- .../italian/how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/italian/moderator-handbook.md | 245 +----------------- docs/i18n/italian/reply-templates.md | 232 +++++++++++++++++ docs/i18n/italian/security-hall-of-fame.md | 2 +- docs/i18n/japanese/FAQ.md | 82 +++--- docs/i18n/japanese/_sidebar.md | 10 +- docs/i18n/japanese/devops.md | 8 +- .../japanese/how-to-enable-new-languages.md | 2 +- ...o-setup-freecodecamp-mobile-app-locally.md | 6 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 10 +- .../japanese/how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/japanese/moderator-handbook.md | 245 +----------------- docs/i18n/japanese/reply-templates.md | 232 +++++++++++++++++ docs/i18n/japanese/security-hall-of-fame.md | 2 +- docs/i18n/portuguese/FAQ.md | 92 +++---- docs/i18n/portuguese/_sidebar.md | 38 +-- docs/i18n/portuguese/devops.md | 8 +- .../portuguese/how-to-enable-new-languages.md | 18 +- .../how-to-setup-freecodecamp-locally.md | 2 +- ...o-setup-freecodecamp-mobile-app-locally.md | 22 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 14 +- .../how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/portuguese/moderator-handbook.md | 245 +----------------- docs/i18n/portuguese/reply-templates.md | 232 +++++++++++++++++ docs/i18n/portuguese/security-hall-of-fame.md | 2 +- docs/i18n/ukrainian/FAQ.md | 38 +-- docs/i18n/ukrainian/_sidebar.md | 38 +-- .../ukrainian/courses-vscode-extension.md | 28 +- docs/i18n/ukrainian/devops.md | 72 ++--- .../ukrainian/how-to-enable-new-languages.md | 18 +- ...o-setup-freecodecamp-mobile-app-locally.md | 6 +- .../how-to-work-on-coding-challenges.md | 8 +- .../how-to-work-on-localized-client-webapp.md | 4 + .../how-to-work-on-practice-projects.md | 4 + .../how-to-work-on-the-component-library.md | 108 ++++---- .../how-to-work-on-the-docs-theme.md | 6 +- docs/i18n/ukrainian/moderator-handbook.md | 245 +----------------- docs/i18n/ukrainian/reply-templates.md | 232 +++++++++++++++++ docs/i18n/ukrainian/security-hall-of-fame.md | 2 +- 106 files changed, 2727 insertions(+), 2575 deletions(-) create mode 100644 docs/i18n/chinese-traditional/reply-templates.md create mode 100644 docs/i18n/chinese/reply-templates.md create mode 100644 docs/i18n/espanol/reply-templates.md create mode 100644 docs/i18n/german/reply-templates.md create mode 100644 docs/i18n/italian/reply-templates.md create mode 100644 docs/i18n/japanese/reply-templates.md create mode 100644 docs/i18n/portuguese/reply-templates.md create mode 100644 docs/i18n/ukrainian/reply-templates.md diff --git a/docs/i18n/chinese-traditional/FAQ.md b/docs/i18n/chinese-traditional/FAQ.md index 6b230e871cc..80013726ff6 100644 --- a/docs/i18n/chinese-traditional/FAQ.md +++ b/docs/i18n/chinese-traditional/FAQ.md @@ -1,62 +1,66 @@ -### I am new to GitHub and Open Source. Where should I start? +# Frequently Asked Questions + +Answers to common questions. + +## I am new to GitHub and Open Source. Where should I start? Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### What do I need to know to contribute to the codebase? +## What do I need to know to contribute to the codebase? freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -### Can I translate freeCodeCamp's resources? +## Can I translate freeCodeCamp's resources? Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). -如果你對參與翻譯貢獻有興趣，請務必首先[閱讀本指南](how-to-translate-files.md)。 +If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -### Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? Yes - you can contribute to our publication blog and YouTube channel. -如果你有興趣爲 freeCodeCamp News 撰寫文章，請訪問此 [專欄寫作指南](https://www.freecodecamp.org/chinese/news/developer-news-style-guide/)。 In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -### 我如何報告一個新的 bug？ +## How can I report a new bug? If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -如果你確信這是一個新的bug，請創建一個新的 GitHub issue。 請務必包含儘可能多的信息，以便我們能夠重現 bug。 我們有預設的 issue 模版來幫助你提交 GitHub issue。 +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -請注意，這些 GitHub issues 僅爲了代碼庫相關的問題和討論，而不是爲了獲得編程學習方面的幫助。 當你有疑問時，應該在創建一個 GitHub issue 前[在論壇上尋求幫助](https://forum.freecodecamp.org)。 +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### 我如何報告一個安全問題？ +## How can I report a security issue? -請不要爲安全問題來創建 GitHub issue。 反之，請 [遵循我們的安全政策](https://contribute.freecodecamp.org/#/security)。 +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -### 我是一名學生。 我可以爲學術學分參與一個功能開發嗎？ +## I am a student. Can I work on a feature for academic credits? -可以的。 請注意，我們無法承諾你的學院或大學可能要求的任何時間表或文書工作。 我們收到了許多來自於志願開發者的推送請求以及代碼貢獻，並且我們尊重他們的時間與勞動。 出於對我們所有其他貢獻者的尊重，我們不會僅僅因爲與學校有關而給予任何優先考慮。 +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -我們請求你提前計劃，並在貢獻代碼時知曉這一點。 +We request you to plan ahead and work on code contributions with this in mind. -### 這些不同的在問題上標籤意味着什麼？ +## What do these different labels that are tagged on issues mean? -代碼維護人員會根據優先級、嚴重程度和其他因素對 issue 和 pull request 進行[分類](https://en.wikipedia.org/wiki/Software_bug#Bug_management)。 你可以在這裏找到[其含義的完整詞彙表](https://github.com/freecodecamp/freecodecamp/labels). +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). -### 如果我想就一個問題開展工作，我將從哪裏開始？ +## Where do I start if I want to work on an issue? -你應該瀏覽標註有 [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) 或 [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) 的 issue，以快速瞭解可供你貢獻的內容。 +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] **`help wanted`** issues are up for grabs, and you do not need to seek permission before working on them. 然而，具有 **`first timers only`** 標籤的 issue 是特別爲以前沒有爲 freeCodeCodeCamp 代碼庫貢獻的人設計的任務。 -### I found a typo. Should I report an issue before I can make a pull request? +## I found a typo. Should I report an issue before I can make a pull request? For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### How can I get an issue assigned to me? +## How can I get an issue assigned to me? We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: @@ -69,7 +73,7 @@ We typically do not assign issues to anyone other than long-time contributors. I - Did you follow the pull request checklist? - Did you give your pull request a meaningful title? -### I am interested in being a moderator at freeCodeCamp. Where should I start? +## I am interested in being a moderator at freeCodeCamp. Where should I start? Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. @@ -81,13 +85,13 @@ Here are some recommended paths for some of our platforms: - To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information. - To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself). -Altogether, be respectful to others. 我們是來自世界各地的人。 With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### I am stuck on something that is not included in this documentation. +## I am stuck on something that is not included in this documentation. **Feel free to ask for help in:** @@ -98,8 +102,8 @@ We are excited to help you contribute to any of the topics that you would like t Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### Additional Assistance +## Additional Assistance -如果你對技術棧、代碼庫的架構、翻譯或其他方面有疑問，請隨時[在論壇上](https://forum.freecodecamp.org/g/team)與我們的員工團隊聯繫。 +If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**你可以發郵件到 `dev[at]freecodecamp.org` 以聯繫我們團隊的開發者。** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/chinese-traditional/_sidebar.md b/docs/i18n/chinese-traditional/_sidebar.md index bd7c3ed848b..a56cd55b54d 100644 --- a/docs/i18n/chinese-traditional/_sidebar.md +++ b/docs/i18n/chinese-traditional/_sidebar.md @@ -8,7 +8,6 @@ - **Code Contribution** - [Set up freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Follow best-practices](codebase-best-practices.md) - - [Open a pull request](how-to-open-a-pull-request.md) - [Work on Codebase](how-to-contribute-to-the-codebase.md) - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) - [Work on Component Library](how-to-work-on-the-component-library.md) @@ -19,10 +18,12 @@ - [Work on Cypress tests](how-to-add-cypress-tests.md) - [Work on Video Challenges](how-to-help-with-video-challenges.md) - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Additional Guides** - [Understand the curriculum file structure](curriculum-file-structure.md) - [Debug outgoing emails locally](how-to-catch-outgoing-emails-locally.md) - [Set up freeCodeCamp on Windows (WSL)](how-to-setup-wsl.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) - [User Token Workflow](user-token-workflow.md) - [Troubleshooting Development Issues](troubleshooting-development-issues.md) - [Authors Analytics Manual](authors-analytics-manual.md) @@ -31,6 +32,7 @@ - **飛行手冊**（針對員工 & 維護人員） - [維護人員手冊](moderator-handbook.md) + - [Reply Templates](reply-templates.md) - [Language Lead Handbook](language-lead-handbook.md) - [DevOps Handbook](devops.md) - [Courses VSCode Extension](courses-vscode-extension.md) diff --git a/docs/i18n/chinese-traditional/devops.md b/docs/i18n/chinese-traditional/devops.md index e25458c86ab..40ecd2fd9ff 100644 --- a/docs/i18n/chinese-traditional/devops.md +++ b/docs/i18n/chinese-traditional/devops.md @@ -203,19 +203,19 @@ You can identify the exact version deployed by visiting the build and deployment There are some known limitations and tradeoffs when using the beta version of the platform. -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Users on the beta version will have a separate account from the production.** The beta version uses a physically separate database from production. This gives us the ability to prevent any accidental loss of data or modifications. The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** Deployment is expected to be frequent and in rapid iterations, sometimes multiple times a day. As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### Do not send regular users to this site as a measure of confirming a fix +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** The beta site is and always has been to augment local development and testing, nothing else. It's not a promise of what’s coming, but a glimpse of what is being worked upon. -- #### Sign in page may look different than production +- **Sign in page may look different than production** We use a test tenant for freeCodeCamp.dev on Auth0, and hence do not have the ability to set a custom domain. This makes it so that all the redirect callbacks and the login page appear at a default domain like: `https://freecodecamp-dev.auth0.com/`. This does not affect the functionality and is as close to production as we can get. diff --git a/docs/i18n/chinese-traditional/how-to-enable-new-languages.md b/docs/i18n/chinese-traditional/how-to-enable-new-languages.md index a17f211ef05..af975a8e144 100644 --- a/docs/i18n/chinese-traditional/how-to-enable-new-languages.md +++ b/docs/i18n/chinese-traditional/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Enabling Localized Videos +### Enabling Localized Videos For the video challenges, you need to change a few things. First, add the new locale to the GraphQL query in the `client/src/templates/Challenges/video/Show.tsx` file. For example, adding Dothraki to the query: diff --git a/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md index 9deae099e21..2ee38da1b31 100644 --- a/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Follow this guide for setting up the freeCodeCamp mobile app locally on your sys Some of the contribution workflows – like fixing bugs in the codebase – need you to run the freeCodeCamp app locally. -### How to Prepare your Local Machine +## How to Prepare your Local Machine Start by installing the prerequisite software for your operating system. -#### Prerequisites +### Prerequisites | Prerequisite | Version | Notes | | --------------------------------- | ------- | ---------------------------------------- | @@ -26,7 +26,7 @@ dart --version Once you have the prerequisites installed, you need to prepare your development environment. This is common for many development workflows, and you will only need to do this once. -##### Follow these steps to get your development environment ready: +#### Follow these steps to get your development environment ready: 1. Install [Git](https://git-scm.com/) or your favorite Git client, if you haven't already. Update to the latest version; the version that came bundled with your OS may be outdated. diff --git a/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md b/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md index c0dd14498b1..1984bd4606b 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md @@ -483,13 +483,15 @@ You are also able to test one challenge individually by performing the following ``` pnpm run test -- -g challenge-title-goes-here ``` -Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](how-to-open-a-pull-request.md). - > [!TIP] You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test. > > The currently accepted values are `english` and `chinese`, with `english` being set by default. -### Useful Links +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links Creating and Editing Challenges: diff --git a/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md b/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md index b75c277d600..50648de0844 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md @@ -266,6 +266,10 @@ It would be nice to keep the keys in the same order across all the files as well > [!NOTE] The underscore (`_`) is a reserved character for keys in the client-side files. See [the documentation](https://www.i18next.com/translation-function/plurals) for how they are used. +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Helpful Documentation - [react-i18next docs](https://react.i18next.com/latest/usetranslation-hook) diff --git a/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md b/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md index a499583fae6..e841f107add 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ A one-off script that automatically updates the frontmatter in a project's markd ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/chinese-traditional/how-to-work-on-the-component-library.md b/docs/i18n/chinese-traditional/how-to-work-on-the-component-library.md index 58f2e03ea47..428e2c327da 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-the-component-library.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). - # How to Work on the Component Library +Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > freeCodeCamp has been using Bootstrap components in the UI. However, we are moving away from it and building our own component library, which helps standardize our UX/UI patterns and improve accessibility. The project is tracked in [this GitHub issue](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,6 +91,10 @@ To run tests against the component library, run the following command from the r pnpm run test-ui-components ``` +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Adding Packages to the UI-Component Library We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: @@ -100,7 +104,7 @@ cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Useful Links - [Testing for Accessibility](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Order of priority of React Testing Library's queries](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/chinese-traditional/how-to-work-on-the-docs-theme.md b/docs/i18n/chinese-traditional/how-to-work-on-the-docs-theme.md index 9e6080da9be..8a543eb6a69 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Typically you would not need to change any configuration or build the site local Install freeCodeCamp locally ([see the local setup guide](how-to-setup-freecodecamp-locally)), we bundled the CLI with the development tools so you can run the command below as needed from the root of the repo: -#### Serve and Launch the Documentation Site - ```console pnpm run docs:serve ``` > The documentation site should be available at + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/chinese-traditional/moderator-handbook.md b/docs/i18n/chinese-traditional/moderator-handbook.md index 933ba787467..1da21d0f830 100644 --- a/docs/i18n/chinese-traditional/moderator-handbook.md +++ b/docs/i18n/chinese-traditional/moderator-handbook.md @@ -39,7 +39,7 @@ We use our main [`freeCodeCamp/freeCodeCamp`](https://github.com/freeCodeCamp/fr 請特別注意標籤 `"help wanted"`（“需要幫助”）和 `"first timers only"`（“僅限新手使用”）。 這些標籤將添加到你認爲可以向潛在貢獻者開放，以便他們提出拉取請求的主題中。 -A `"first timers only"` label should be applied to a trivial issue (ie a typo fix) and should include additional information. 你可以使用這個[回覆模板](moderator-handbook.md#first-timer-only-issues)去分流。 +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### 關閉陳舊的、過時的、不活躍的 issue 和拉取請求 @@ -49,7 +49,7 @@ A `"first timers only"` label should be applied to a trivial issue (ie a typo fi - If the contributor asks for additional assistance or even time, the above can be relaxed and revisited after a response is given. In any case, the mods should use their best judgment to resolve the outstanding PR's status. -> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### 管理拉取請求（Pull Requests） @@ -63,7 +63,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi You can also review these right on GitHub and decide whether to merge them. 因爲會有無數的人通過 freeCodeCamp 課程讀到這段文字， 所以我們應該要更加認真對待。 Does the pull request make the text more clear without making it much longer? Are the edits relevant and not overly pedantic? Remember that our goal is for challenges to be as clear and as short as possible. They aren't the place for obscure details. Contributors may try to add links to resources to the challenges. - You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with a "LGTM" (Looks Good To Me) comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -75,7 +75,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi Some contributors may try to add additional tests to cover pedantic corner-cases. We need to be careful to not make the challenge too complicated. These challenges and their tests should be as simple and intuitive as possible. Aside from the algorithm challenges and interview prep section, learners should be able to solve each challenge within about 2 minutes. - You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with an "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -142,7 +142,7 @@ Often, a pull request will be low effort. You can usually tell this immediately There are also situations where the contributor is trying to add a link to their website, include a library they created, or have a frivolous edit that doesn't help anyone but themselves. -You can close these invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Other Guidelines for Moderators on GitHub @@ -344,238 +344,3 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
Thanks for reading this, and thanks for helping the developer community! - -## Reply Templates - -These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. - -> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. - -### Thank You - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Thank you and congrats - -> For thanking and encouraging first-time contributors. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Build Error - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Syncing Fork - -> When PR is not up to date with the `main` branch. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Merge Conflicts - -> When PR has merge conflicts that need to be resolved.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. - -### Duplicate - -> When PR is repetitive or a duplicate. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Closing Invalid Pull Requests - -> When PR is invalid. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> When PR adds links to external resources. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adding Comment About Newbie Mistakes - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Closing Invalid Issues - -> When an issue relates to the camper's code. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> When an issue is duplicate of an earlier issue. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> When an issue is fixed in staging. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### `first timer only` Issues - -> When an issue is deemed to be eligible for first-time code contributors. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Requests for Assignment - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/chinese-traditional/reply-templates.md b/docs/i18n/chinese-traditional/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/chinese-traditional/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/chinese-traditional/security-hall-of-fame.md b/docs/i18n/chinese-traditional/security-hall-of-fame.md index 476070b6172..ac615e5a645 100644 --- a/docs/i18n/chinese-traditional/security-hall-of-fame.md +++ b/docs/i18n/chinese-traditional/security-hall-of-fame.md @@ -8,4 +8,4 @@ While we do not offer any bounties or swags at the moment, we are grateful to th - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) working with IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Thank you for your contributions :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/chinese/FAQ.md b/docs/i18n/chinese/FAQ.md index 6a18d12dec8..ffea35ae553 100644 --- a/docs/i18n/chinese/FAQ.md +++ b/docs/i18n/chinese/FAQ.md @@ -1,62 +1,66 @@ -### I am new to GitHub and Open Source. Where should I start? +# Frequently Asked Questions + +Answers to common questions. + +## I am new to GitHub and Open Source. Where should I start? Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### What do I need to know to contribute to the codebase? +## What do I need to know to contribute to the codebase? freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -### Can I translate freeCodeCamp's resources? +## Can I translate freeCodeCamp's resources? Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). -如果你对参与翻译贡献有兴趣，请务必首先[阅读本指南](how-to-translate-files.md)。 +If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -### Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? Yes - you can contribute to our publication blog and YouTube channel. -如果你有兴趣为 freeCodeCamp News 撰写文章，请访问此 [专栏写作指南](https://www.freecodecamp.org/chinese/news/developer-news-style-guide/)。 In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -### 我如何报告一个新的 bug？ +## How can I report a new bug? If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -如果你确信这是一个新的bug，请创建一个新的 GitHub issue。 请务必包含尽可能多的信息，以便我们能够重现 bug。 我们有预设的 issue 模版来帮助你提交 GitHub issue。 +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -请注意，这些 GitHub issues 仅为了代码库相关的问题和讨论，而不是为了获得编程学习方面的帮助。 当你有疑问时，应该在创建一个 GitHub issue 前[在论坛上寻求帮助](https://forum.freecodecamp.org)。 +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### 我如何报告一个安全问题？ +## How can I report a security issue? -请不要为安全问题来创建 GitHub issue。 反之，请 [遵循我们的安全政策](https://contribute.freecodecamp.org/#/security)。 +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -### 我是一名学生。 我可以为学术学分参与一个功能开发吗？ +## I am a student. Can I work on a feature for academic credits? -可以的。 请注意，我们无法承诺你的学院或大学可能要求的任何时间表或文书工作。 我们收到了许多来自于志愿开发者的推送请求以及代码贡献，并且我们尊重他们的时间与劳动。 出于对我们所有其他贡献者的尊重，我们不会仅仅因为与学校有关而给予任何优先考虑。 +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -我们请求你提前计划，并在贡献代码时知晓这一点。 +We request you to plan ahead and work on code contributions with this in mind. -### 这些不同的在问题上标签意味着什么？ +## What do these different labels that are tagged on issues mean? -代码维护人员会根据优先级、严重程度和其他因素对 issue 和 pull request 进行[分类](https://en.wikipedia.org/wiki/Software_bug#Bug_management)。 你可以在这里找到[其含义的完整词汇表](https://github.com/freecodecamp/freecodecamp/labels). +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). -### 如果我想就一个问题开展工作，我将从哪里开始？ +## Where do I start if I want to work on an issue? -你应该浏览标注有 [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) 或 [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) 的 issue，以快速了解可供你贡献的内容。 +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] **`help wanted`** issues are up for grabs, and you do not need to seek permission before working on them. 然而，具有 **`first timers only`** 标签的 issue 是特别为以前没有为 freeCodeCodeCamp 代码库贡献的人设计的任务。 -### I found a typo. Should I report an issue before I can make a pull request? +## I found a typo. Should I report an issue before I can make a pull request? For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### How can I get an issue assigned to me? +## How can I get an issue assigned to me? We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: @@ -69,7 +73,7 @@ We typically do not assign issues to anyone other than long-time contributors. I - Did you follow the pull request checklist? - Did you give your pull request a meaningful title? -### I am interested in being a moderator at freeCodeCamp. Where should I start? +## I am interested in being a moderator at freeCodeCamp. Where should I start? Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. @@ -81,13 +85,13 @@ Here are some recommended paths for some of our platforms: - To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information. - To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself). -Altogether, be respectful to others. 我们是来自世界各地的人。 With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### I am stuck on something that is not included in this documentation. +## I am stuck on something that is not included in this documentation. **Feel free to ask for help in:** @@ -98,8 +102,8 @@ We are excited to help you contribute to any of the topics that you would like t Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### Additional Assistance +## Additional Assistance -如果你对技术栈、代码库的架构、翻译或其他方面有疑问，请随时[在论坛上](https://forum.freecodecamp.org/g/team)与我们的员工团队联系。 +If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**你可以发邮件到 `dev[at]freecodecamp.org` 以联系我们团队的开发者。** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/chinese/_sidebar.md b/docs/i18n/chinese/_sidebar.md index 241263ffe2e..2a3a8a4e1b6 100644 --- a/docs/i18n/chinese/_sidebar.md +++ b/docs/i18n/chinese/_sidebar.md @@ -8,7 +8,6 @@ - **Code Contribution** - [Set up freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Follow best-practices](codebase-best-practices.md) - - [Open a pull request](how-to-open-a-pull-request.md) - [Work on Codebase](how-to-contribute-to-the-codebase.md) - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) - [Work on Component Library](how-to-work-on-the-component-library.md) @@ -19,10 +18,12 @@ - [Work on Cypress tests](how-to-add-cypress-tests.md) - [Work on Video Challenges](how-to-help-with-video-challenges.md) - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Additional Guides** - [Understand the curriculum file structure](curriculum-file-structure.md) - [Debug outgoing emails locally](how-to-catch-outgoing-emails-locally.md) - [Set up freeCodeCamp on Windows (WSL)](how-to-setup-wsl.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) - [User Token Workflow](user-token-workflow.md) - [Troubleshooting Development Issues](troubleshooting-development-issues.md) - [Authors Analytics Manual](authors-analytics-manual.md) @@ -31,6 +32,7 @@ - **飞行手册**（针对员工 & 维护人员） - [维护人员手册](moderator-handbook.md) + - [Reply Templates](reply-templates.md) - [Language Lead Handbook](language-lead-handbook.md) - [DevOps Handbook](devops.md) - [Courses VSCode Extension](courses-vscode-extension.md) diff --git a/docs/i18n/chinese/devops.md b/docs/i18n/chinese/devops.md index cc8c914f3b4..63893c9875e 100644 --- a/docs/i18n/chinese/devops.md +++ b/docs/i18n/chinese/devops.md @@ -203,19 +203,19 @@ You can identify the exact version deployed by visiting the build and deployment There are some known limitations and tradeoffs when using the beta version of the platform. -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Users on the beta version will have a separate account from the production.** The beta version uses a physically separate database from production. This gives us the ability to prevent any accidental loss of data or modifications. The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** Deployment is expected to be frequent and in rapid iterations, sometimes multiple times a day. As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### Do not send regular users to this site as a measure of confirming a fix +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** The beta site is and always has been to augment local development and testing, nothing else. It's not a promise of what’s coming, but a glimpse of what is being worked upon. -- #### Sign in page may look different than production +- **Sign in page may look different than production** We use a test tenant for freeCodeCamp.dev on Auth0, and hence do not have the ability to set a custom domain. This makes it so that all the redirect callbacks and the login page appear at a default domain like: `https://freecodecamp-dev.auth0.com/`. This does not affect the functionality and is as close to production as we can get. diff --git a/docs/i18n/chinese/how-to-enable-new-languages.md b/docs/i18n/chinese/how-to-enable-new-languages.md index a8690b8c139..4b8cb33227d 100644 --- a/docs/i18n/chinese/how-to-enable-new-languages.md +++ b/docs/i18n/chinese/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Enabling Localized Videos +### Enabling Localized Videos For the video challenges, you need to change a few things. First, add the new locale to the GraphQL query in the `client/src/templates/Challenges/video/Show.tsx` file. For example, adding Dothraki to the query: diff --git a/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md index 9deae099e21..2ee38da1b31 100644 --- a/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Follow this guide for setting up the freeCodeCamp mobile app locally on your sys Some of the contribution workflows – like fixing bugs in the codebase – need you to run the freeCodeCamp app locally. -### How to Prepare your Local Machine +## How to Prepare your Local Machine Start by installing the prerequisite software for your operating system. -#### Prerequisites +### Prerequisites | Prerequisite | Version | Notes | | --------------------------------- | ------- | ---------------------------------------- | @@ -26,7 +26,7 @@ dart --version Once you have the prerequisites installed, you need to prepare your development environment. This is common for many development workflows, and you will only need to do this once. -##### Follow these steps to get your development environment ready: +#### Follow these steps to get your development environment ready: 1. Install [Git](https://git-scm.com/) or your favorite Git client, if you haven't already. Update to the latest version; the version that came bundled with your OS may be outdated. diff --git a/docs/i18n/chinese/how-to-work-on-coding-challenges.md b/docs/i18n/chinese/how-to-work-on-coding-challenges.md index c0dd14498b1..1984bd4606b 100644 --- a/docs/i18n/chinese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/chinese/how-to-work-on-coding-challenges.md @@ -483,13 +483,15 @@ You are also able to test one challenge individually by performing the following ``` pnpm run test -- -g challenge-title-goes-here ``` -Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](how-to-open-a-pull-request.md). - > [!TIP] You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test. > > The currently accepted values are `english` and `chinese`, with `english` being set by default. -### Useful Links +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links Creating and Editing Challenges: diff --git a/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md b/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md index b75c277d600..50648de0844 100644 --- a/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md @@ -266,6 +266,10 @@ It would be nice to keep the keys in the same order across all the files as well > [!NOTE] The underscore (`_`) is a reserved character for keys in the client-side files. See [the documentation](https://www.i18next.com/translation-function/plurals) for how they are used. +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Helpful Documentation - [react-i18next docs](https://react.i18next.com/latest/usetranslation-hook) diff --git a/docs/i18n/chinese/how-to-work-on-practice-projects.md b/docs/i18n/chinese/how-to-work-on-practice-projects.md index a499583fae6..e841f107add 100644 --- a/docs/i18n/chinese/how-to-work-on-practice-projects.md +++ b/docs/i18n/chinese/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ A one-off script that automatically updates the frontmatter in a project's markd ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/chinese/how-to-work-on-the-component-library.md b/docs/i18n/chinese/how-to-work-on-the-component-library.md index 58f2e03ea47..428e2c327da 100644 --- a/docs/i18n/chinese/how-to-work-on-the-component-library.md +++ b/docs/i18n/chinese/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). - # How to Work on the Component Library +Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > freeCodeCamp has been using Bootstrap components in the UI. However, we are moving away from it and building our own component library, which helps standardize our UX/UI patterns and improve accessibility. The project is tracked in [this GitHub issue](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,6 +91,10 @@ To run tests against the component library, run the following command from the r pnpm run test-ui-components ``` +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Adding Packages to the UI-Component Library We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: @@ -100,7 +104,7 @@ cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Useful Links - [Testing for Accessibility](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Order of priority of React Testing Library's queries](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/chinese/how-to-work-on-the-docs-theme.md b/docs/i18n/chinese/how-to-work-on-the-docs-theme.md index 3cc3ea259ed..ce4f7f00b0d 100644 --- a/docs/i18n/chinese/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/chinese/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Typically you would not need to change any configuration or build the site local Install freeCodeCamp locally ([see the local setup guide](how-to-setup-freecodecamp-locally)), we bundled the CLI with the development tools so you can run the command below as needed from the root of the repo: -#### Serve and Launch the Documentation Site - ```console pnpm run docs:serve ``` > The documentation site should be available at + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/chinese/moderator-handbook.md b/docs/i18n/chinese/moderator-handbook.md index e9561929c3d..b422d57832b 100644 --- a/docs/i18n/chinese/moderator-handbook.md +++ b/docs/i18n/chinese/moderator-handbook.md @@ -39,7 +39,7 @@ We use our main [`freeCodeCamp/freeCodeCamp`](https://github.com/freeCodeCamp/fr 请特别注意标签 `"help wanted"`（“需要帮助”）和 `"first timers only"`（“仅限新手使用”）。 这些标签将添加到你认为可以向潜在贡献者开放，以便他们提出拉取请求的主题中。 -A `"first timers only"` label should be applied to a trivial issue (ie a typo fix) and should include additional information. 你可以使用这个[回复模板](moderator-handbook.md#first-timer-only-issues)去分流。 +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### 关闭陈旧的、过时的、不活跃的 issue 和拉取请求 @@ -49,7 +49,7 @@ A `"first timers only"` label should be applied to a trivial issue (ie a typo fi - If the contributor asks for additional assistance or even time, the above can be relaxed and revisited after a response is given. In any case, the mods should use their best judgment to resolve the outstanding PR's status. -> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### 管理拉取请求（Pull Requests） @@ -63,7 +63,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi You can also review these right on GitHub and decide whether to merge them. 因为会有无数的人通过 freeCodeCamp 课程读到这段文字， 所以我们应该要更加认真对待。 Does the pull request make the text more clear without making it much longer? Are the edits relevant and not overly pedantic? Remember that our goal is for challenges to be as clear and as short as possible. They aren't the place for obscure details. Contributors may try to add links to resources to the challenges. - You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with a "LGTM" (Looks Good To Me) comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -75,7 +75,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi Some contributors may try to add additional tests to cover pedantic corner-cases. We need to be careful to not make the challenge too complicated. These challenges and their tests should be as simple and intuitive as possible. Aside from the algorithm challenges and interview prep section, learners should be able to solve each challenge within about 2 minutes. - You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with an "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -142,7 +142,7 @@ Often, a pull request will be low effort. You can usually tell this immediately There are also situations where the contributor is trying to add a link to their website, include a library they created, or have a frivolous edit that doesn't help anyone but themselves. -You can close these invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Other Guidelines for Moderators on GitHub @@ -344,238 +344,3 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
Thanks for reading this, and thanks for helping the developer community! - -## Reply Templates - -These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. - -> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. - -### Thank You - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Thank you and congrats - -> For thanking and encouraging first-time contributors. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Build Error - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Syncing Fork - -> When PR is not up to date with the `main` branch. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Merge Conflicts - -> When PR has merge conflicts that need to be resolved.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. - -### Duplicate - -> When PR is repetitive or a duplicate. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Closing Invalid Pull Requests - -> When PR is invalid. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> When PR adds links to external resources. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adding Comment About Newbie Mistakes - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Closing Invalid Issues - -> When an issue relates to the camper's code. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> When an issue is duplicate of an earlier issue. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> When an issue is fixed in staging. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### `first timer only` Issues - -> When an issue is deemed to be eligible for first-time code contributors. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Requests for Assignment - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/chinese/reply-templates.md b/docs/i18n/chinese/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/chinese/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/chinese/security-hall-of-fame.md b/docs/i18n/chinese/security-hall-of-fame.md index 476070b6172..ac615e5a645 100644 --- a/docs/i18n/chinese/security-hall-of-fame.md +++ b/docs/i18n/chinese/security-hall-of-fame.md @@ -8,4 +8,4 @@ While we do not offer any bounties or swags at the moment, we are grateful to th - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) working with IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Thank you for your contributions :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/espanol/FAQ.md b/docs/i18n/espanol/FAQ.md index 6bcc3a83776..211f66b39ea 100644 --- a/docs/i18n/espanol/FAQ.md +++ b/docs/i18n/espanol/FAQ.md @@ -1,64 +1,68 @@ -### Soy nuevo en GitHub y Open Source. ¿Dónde debo empezar? +# Frequently Asked Questions -Lee nuestra ["Guía de como contribuir a Open Source"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). Es una referencia completa para proyectos aptos para principiantes. And it includes a lot of open-source contribution tips. +Answers to common questions. -### ¿Qué necesito saber para contribuir al código base? +## I am new to GitHub and Open Source. Where should I start? -freeCodeCamp se ejecuta en una moderna plataforma de JavaScript. Si estás interesado en contribuir a nuestra base de código, necesitarás cierta familiaridad con JavaScript y algunas de las tecnologías que usamos como Node.js, MongoDB, OAuth 2.0, React, Gatsby, y Webpack. +Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### ¿Puedo traducir los recursos de freeCodeCamp? +## What do I need to know to contribute to the codebase? -Sí - Puedes contribuir cualquiera de los más de 30 idiomas que hemos habilitado en nuestra plataforma de traducción. +freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -Tenemos traducciones hechas por usuarios nativos en algunos idiomas. Tenemos la intención de traducir freeCodeCamp a los principales idiomas del mundo. Puedes leer todo acerca de esto en nuestro [anuncio aquí](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). +## Can I translate freeCodeCamp's resources? -Si estás interesado en ayudar a traducir, por favor asegúrate de [leer esta guía](how-to-translate-files.md) primero. +Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. -### Puedo contribuír con artículos a las Noticias de freeCodeCamp o con vídeos al canal de YouTube de freeCodeCamp? +We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). -Sí - puedes contribuir a las publicaciones de nuestro blog y canal de YouTube. +If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -Si estás interesade en escribir artículos para las Noticias de freeCodeCamp, por favor visita esta [guía de publicaciones](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). Además, por favor lea nuestra [guía de estilo](https://www.freecodecamp.org/news/developer-news-style-guide/) ya que esto le ayudará a escribir artículos más fuertes y efectivos. +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? -Para ayudarnos a crear vídeos educacionales para nuestro canal de YouTube, puedes seguir la [guía del canal de YouTube](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). +Yes - you can contribute to our publication blog and YouTube channel. -### Cómo puedo reportar un nuevo error? +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. -Si piensas que has encontrado un error, primero lea el artículo ["Como reportar un error"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) y siga las instrucciones. +To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -Si estás seguro de que es un error nuevo, crea un tema de GitHub nuevo. Asegúrate de incluir tanta información como sea posible para que podamos reproducir el error. Tenemos una plantilla de informe predefinida para ayudarte con esto. +## How can I report a new bug? -Ten en cuenta que estos temas de GitHub son para debates y problemas relacionados al código base, no para obtener ayuda para aprender a programar. Siempre que tenga dudas, debe [buscar ayuda en el foro](https://forum.freecodecamp.org) antes de reportar un problema de GitHub. +If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -### ¿Cómo puedo reportar un problema de seguridad? +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -Por favor, no crees Tema de GitHub para problemas de seguridad. En su lugar, [siga nuestra política de seguridad](https://contribute.freecodecamp.org/#/security). +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### Soy estudiante. ¿Puedo trabajar en una característica para los créditos académicos? +## How can I report a security issue? -Sí. Tenga en cuenta que no podemos comprometernos con ningún plazo o papeleo que pueda ser un requisito de su colegio o universidad. Recibimos muchas solicitudes de incorporación de cambios y contribuciones de código de desarrolladores voluntarios, y respetamos su tiempo y esfuerzos. Por respeto a todos nuestros otros colaboradores, no le daremos prioridad especial a las relaciones públicas solo porque esté relacionado con la escuela. +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -Le solicitamos que planifique con anticipación y trabaje en las contribuciones de código teniendo esto en cuenta. +## I am a student. Can I work on a feature for academic credits? -### ¿Qué significan estas diferentes etiquetas que se etiquetan en los problemas? +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -Los mantenedores de código [clasifican](https://en.wikipedia.org/wiki/Software_bug#Bug_management) problemas y pull requests basados en su prioridad, gravedad y otros factores. Puedes [encontrar un glosario completo de sus significados aquí](https://github.com/freecodecamp/freecodecamp/labels). +We request you to plan ahead and work on code contributions with this in mind. -### ¿Dónde comienzo si quiero trabajar en un problema? +## What do these different labels that are tagged on issues mean? -Deberías pasar por los temas [**`se busca ayuda`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) o [**`solo principiantes`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) para una rápida visión general de lo que está disponible para que trabajes. +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). + +## Where do I start if I want to work on an issue? + +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] Los temas de **`se busca ayuda`** están en marcha y no es necesario pedir permiso antes de trabajar en ellos. Sin embargo, temas con la etiqueta **`solo principiantes`** son temas especiales que están diseñados para personas que no han contribuido a la base de código de freeCodeCamp antes. -### Encontré un error tipográfico. ¿Debo informar de un problema antes de poder hacer un pull request? +## I found a typo. Should I report an issue before I can make a pull request? -Para errores tipográficos y otros cambios de redacción, puedes abrir pull-requests directamente sin tener que crear un problema primero. Asegúrese de mencionar los detalles en la descripción del pull request para ayudarnos a comprender y revisar su contribución, incluso si es solo un cambio menor. +For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. -Por favor crea un reporte si deseas discutir aspectos más amplios del código base o currículo. +Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### ¿Cómo puedo conseguir que me asignen un tema? +## How can I get an issue assigned to me? -Por lo general, no asignamos los temas a nadie más que a los colaboradores con mucha antigüedad. En su lugar, seguimos la siguiente política para ser justos con todos: +We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: 1. Lo más probable es que fusionemos el primer pull request que aborde el tema o problema. 2. En el caso de múltiples colaboradores abriendo un pull request para el mismo problema más o menos al mismo tiempo, daremos prioridad al pull request que aborde mejor la cuestión. Algunas de las cosas que consideramos: @@ -69,41 +73,41 @@ Por lo general, no asignamos los temas a nadie más que a los colaboradores con - ¿Has seguido la lista de verificación de pull request? - ¿Has dado a tu pull request un título significativo? -### Estoy interesado en ser moderador en freeCodeCamp. ¿Dónde debería empezar? +## I am interested in being a moderator at freeCodeCamp. Where should I start? -Los moderadores de la comunidad son nuestros héroes. Su contribución voluntaria hace de freeCodeCamp una comunidad segura y acogedora. +Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. -Primero y principal, necesitaremos que seas un participante activo en la comunidad y vivas de acuerdo a nuestro [código de conducta](https://www.freecodecamp.org/news/code-of-conduct/) (no sólo hacerlo cumplir). +First and foremost, we would need you to be an active participant in the community, and live by our [code of conduct](https://www.freecodecamp.org/news/code-of-conduct/) (not just enforce it). -Aquí hay algunas rutas para algunas de nuestras plataformas: +Here are some recommended paths for some of our platforms: - To be a **Discord/Chat** moderator, have an active presence in our chat and have positive engagements with others, while also learning and practicing how to deal with potential conflicts that may arise. - To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information. - To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself). -En total, sé respetuoso con los demás. Somos humanos alreder del mundo. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. -If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. El trabajo de código abierto es voluntario, y nuestro tiempo es limitado. Reconocemos que esto probablemente también sea cierto en su caso. So we emphasize being **consistent** rather than engaging in the community 24/7. +If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### Estoy atascado en algo que no está incluido en esta documentación. +## I am stuck on something that is not included in this documentation. -**Siéntete libre de pedir ayuda en:** +**Feel free to ask for help in:** - La categoria de `Contributors` de [nuestro foro de comunidad](https://forum.freecodecamp.org/c/contributors). - El canal `#Contributors` de nuestro servidor de chat<1>. - Estamos encantados de ayudarte a contribuir en cualquiera de los temas en los que quieras trabajar. Si nos hace preguntas sobre los issue threads, estaremos encantados de aclararlo. Asegúrate de buscar tu pregunta antes de publicar una nueva. + We are excited to help you contribute to any of the topics that you would like to work on. If you ask us questions on the related issue threads, we will be glad to clarify. Be sure to search for your question before posting a new one. - Gracias de antemano por ser amable y paciente. Recuerda, esta comunidad es manejada principalmente por voluntarios. + Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### Asistencia adicional +## Additional Assistance -Si tiene preguntas sobre el stack, arquitectura del código fuente, traducciones, o cualquier otra cosa, no dudes en contactar con nuestro equipo de trabajo [en el foro](https://forum.freecodecamp.org/g/team). +If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**Puedes enviar un correo a nuestro grupo de desarrolladores en: `dev[at]freecodecamp.org`** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/espanol/_sidebar.md b/docs/i18n/espanol/_sidebar.md index 2ec928fddee..670becb24b3 100644 --- a/docs/i18n/espanol/_sidebar.md +++ b/docs/i18n/espanol/_sidebar.md @@ -8,33 +8,35 @@ - **Participa en la programación** - [Configuración de FreeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Seguir las mejores prácticas de código](codebase-best-practices.md) - - [Abrir una solicitud de cambio](how-to-open-a-pull-request.md) - - [Trabajar en Codebase](how-to-contribute-to-the-codebase.md) - - [Realizar desafíos de código](how-to-work-on-coding-challenges.md) - - [Trabajar con la biblioteca de componentes](how-to-work-on-the-component-library.md) - - [Trabajar en proyectos de práctica](how-to-work-on-practice-projects.md) - - [Trabajar con una aplicación de móvil](how-to-setup-freecodecamp-mobile-app-locally.md) - - [Ayudar en tutoriales con CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) - - [Trabajar en una aplicación web localizada](how-to-work-on-localized-client-webapp.md) - - [Realizar las pruebas Cypress](how-to-add-cypress-tests.md) - - [Ayudar con los desafíos de videos](how-to-help-with-video-challenges.md) - - [Trabajar en la Documentación](how-to-work-on-the-docs-theme.md) + - [Work on Codebase](how-to-contribute-to-the-codebase.md) + - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) + - [Work on Component Library](how-to-work-on-the-component-library.md) + - [Work on Practice Projects](how-to-work-on-practice-projects.md) + - [Work on Mobile app](how-to-setup-freecodecamp-mobile-app-locally.md) + - [Work on tutorials with CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) + - [Work on Localized Web App](how-to-work-on-localized-client-webapp.md) + - [Work on Cypress tests](how-to-add-cypress-tests.md) + - [Work on Video Challenges](how-to-help-with-video-challenges.md) + - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Guías adicionales** - [Entender la estructura de los archivos del currículo](curriculum-file-structure.md) - [Depurar localmente los emails salientes](how-to-catch-outgoing-emails-locally.md) - [Configurar freeCodeCamp en Windows (WSL)](how-to-setup-wsl.md) - - [Flujo de trabajo del Token del usuario](user-token-workflow.md) - - [Solución de Problemas en el Desarrollo](troubleshooting-development-issues.md) - - [Manual para Autores de Google Analytics](authors-analytics-manual.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) + - [User Token Workflow](user-token-workflow.md) + - [Troubleshooting Development Issues](troubleshooting-development-issues.md) + - [Authors Analytics Manual](authors-analytics-manual.md) --- - **Manuales de Vuelo** (para el personal & moderadores) - [Manual del moderador](moderator-handbook.md) - - [Libro Principal de Idiomas](language-lead-handbook.md) - - [Manual de DevOps](devops.md) - - [Extensión de cursos de VSCode](courses-vscode-extension.md) - - [Habilitar nuevo idioma](how-to-enable-new-languages.md) + - [Reply Templates](reply-templates.md) + - [Language Lead Handbook](language-lead-handbook.md) + - [DevOps Handbook](devops.md) + - [Courses VSCode Extension](courses-vscode-extension.md) + - [Enable New Language](how-to-enable-new-languages.md) --- diff --git a/docs/i18n/espanol/devops.md b/docs/i18n/espanol/devops.md index e975de48056..215f08d67cc 100644 --- a/docs/i18n/espanol/devops.md +++ b/docs/i18n/espanol/devops.md @@ -203,19 +203,19 @@ Puedes identificar la versión exacta desplegada visitando los registros de comp Existen algunas limitaciones y problemas conocidos al utilizar la versión beta de la plataforma. -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Los usuarios de la versión beta tendrán una cuenta separada a la de producción.** La versión beta usa una base de datos físicamente separada de la de producción. Esto nos da la capacidad de prevenir cualquier pérdida accidental de datos o modificaciones. The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** Se espera que el despliegue sea frecuente y en iteraciones rápidas, a veces varias veces al día. As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### No envíes a los usuarios habituales a este sitio como una medida para confirmar una solución +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** El sitio beta es y siempre ha sido para aumentar el desarrollo y las pruebas locales, nada más. No es una promesa de lo que se avecina, sino un vistazo de lo que se está trabajando. -- #### La página de inicio de sesión puede verse diferente a la de producción +- **Sign in page may look different than production** Usamos un entorno de prueba para freeCodeCamp.dev en Auth0 y por lo tanto, no tenemos la capacidad de establecer un dominio personalizado. Esto hace que todas las redirecciones de peticiones y la página de inicio de sesión aparezcan en un dominio predeterminado como: `https://freecodecamp-dev.auth0.com/`. Esto no afecta la funcionalidad y es lo más cercano a la producción que podemos conseguir. diff --git a/docs/i18n/espanol/how-to-enable-new-languages.md b/docs/i18n/espanol/how-to-enable-new-languages.md index 37ad6627ef7..f3c5d4050cf 100644 --- a/docs/i18n/espanol/how-to-enable-new-languages.md +++ b/docs/i18n/espanol/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Habilitar Videos Localizados +### Enabling Localized Videos Para los desafìos de video, debe cambiar algunas cosas. First, add the new locale to the GraphQL query in the `client/src/templates/Challenges/video/Show.tsx` file. Por ejemplo, agregando a Dothraki para la consulta: @@ -270,7 +270,7 @@ videoLocaleIds: Joi.when('challengeType', { }), ``` -## IU del cliente +## Client UI Necesitará dar un paso adicional para manejar las traducciones de la interfaz de usuario del cliente. @@ -283,7 +283,7 @@ Usted quedrá copiar los siguientes archivos desde `/client/i18n/locales/english - `motivation.json` - `trending.json` -## Pevisualiza las traducciones localmente +## Testing Translations Locally Si desea probar las traducciones localmente, antes de añadirlas a nuestro repositorio principal, salte los cambios del flujo de trabajo de Crowdin. Siga los pasos para activar un idioma, luego descargue las traducciones de Crowdin y cargue las traducciones en su código local. diff --git a/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md index aae92a98539..fd4b74f9ef6 100644 --- a/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Siga esta guía para establecer la aplicación móvil FreeCodeCamp en su sistema Some of the contribution workflows – like fixing bugs in the codebase – need you to run the freeCodeCamp app locally. -### How to Prepare your Local Machine +## How to Prepare your Local Machine Empezar instalando el software requerido previamente para su sistema operativo. -#### Prerequisites +### Prerequisites | Requisito | Versión | Notas | | ------------------------------- | ------- | ---------------------------------------- | @@ -26,7 +26,7 @@ dart --version Una vez que estén instalados los requisitos previos, hay que preparar el entorno de desarrollo. Es muy común para muchos equipos de trabajo, y solo hace falta hacerlo una vez. -##### Seguir estos pasos para tener listo el entorno de desrrollo: +#### Follow these steps to get your development environment ready: 1. Instalar [Git](https://git-scm.com/) u otro cliente Git, si todavía no hay ningumo. Acualizar a la versión más reciente. La que viene con el sistema operativo puede estar desactualizada. @@ -361,7 +361,7 @@ Sigue estos pasos: git push origin nombre/rama-aqui ``` -## Proponer una Pull Request (PR) +## Proposing a Pull Request (PR) Después de que hayas hecho commit de tus cambios, consulta aquí [cómo abrir una Pull Request](how-to-open-a-pull-request.md). @@ -374,7 +374,7 @@ A quick reference to the commands that you will need when working locally. | `npm ci` | Installs / re-install all dependencies and bootstraps the different services. | | `npm run seed` | Parses all the challenge markdown files and inserts them into MongoDB. | --> -## Solución de problemas +## Troubleshooting ### Problemas con la instalación de los prerrequisitos recomendados @@ -398,7 +398,7 @@ Si obtienes errores al instalar las dependencias, por favor asegúrate de que no Be patient as the first-time setup can take a while depending on your network bandwidth. -## Obtener ayuda +## Getting Help Si estás atascado y necesitas ayuda, siéntete libre de hacer preguntas en la categoría de ['Contribuyentes' en nuestro foro](https://forum.freecodecamp.org/c/contributors) o en [la sala de chat de contribuyentes](https://discord.gg/PRyKn3Vbay). diff --git a/docs/i18n/espanol/how-to-work-on-coding-challenges.md b/docs/i18n/espanol/how-to-work-on-coding-challenges.md index 60f69eb77a6..9915032ecaa 100644 --- a/docs/i18n/espanol/how-to-work-on-coding-challenges.md +++ b/docs/i18n/espanol/how-to-work-on-coding-challenges.md @@ -487,13 +487,15 @@ También puedes probar un desafío individualmente realizando los siguientes pas ``` pnpm run test -- -g challenge-title-goes-here ``` -Una vez que haya verificado que cada desafío en el que ha trabajado supera las pruebas, [cree una solicitud de extracción](how-to-open-a-pull-request.md). - > [!TIP] Puede establecer la variable de entorno `LOCALE` en `.env` en el idioma de los retos que necesita probar. > > Los valores aceptados actualmente son `english` y `chinese`, con `english` configurado de manera predeterminada. -### Enlaces útiles +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links Creación y edición de desafíos: diff --git a/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md b/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md index 18b524f7b31..7fce05b0ff2 100644 --- a/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md @@ -266,7 +266,11 @@ Sería bueno mantener la clave en el mismo orden en todos los archivos también. > [!NOTE] The underscore (`_`) is a reserved character for keys in the client-side files. Vea [the documentation](https://www.i18next.com/translation-function/plurals) de como debe ser usado. -## Documentación útil +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Helpful Documentation - [Documentación de react-i18next ](https://react.i18next.com/latest/usetranslation-hook) - [Documentación de i18next](https://www.i18next.com/translation-function/essentials) diff --git a/docs/i18n/espanol/how-to-work-on-practice-projects.md b/docs/i18n/espanol/how-to-work-on-practice-projects.md index aecd420c688..cff73bdf10d 100644 --- a/docs/i18n/espanol/how-to-work-on-practice-projects.md +++ b/docs/i18n/espanol/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ A one-off script that automatically updates the frontmatter in a project's markd ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/espanol/how-to-work-on-the-component-library.md b/docs/i18n/espanol/how-to-work-on-the-component-library.md index 43f49db0bae..6f5466dfc10 100644 --- a/docs/i18n/espanol/how-to-work-on-the-component-library.md +++ b/docs/i18n/espanol/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Bienvenido a la librería `ui-components` de freeCodeCamp. Los componentes se construyen principalmente desde cero con elementos HTML básicos y [Tailwind CSS](https://tailwindcss.com/). - # Cómo trabajar en la biblioteca de componentes +Bienvenido a la librería `ui-components` de freeCodeCamp. Los componentes se construyen principalmente desde cero con elementos HTML básicos y [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > freeCodeCamp ha estado usando componentes de Bootstrap en la interfaz de usuario. Sin embargo, nos estamos alejando de ella y construyendo nuestra propia biblioteca de componentes, lo que ayuda a estandarizar nuestros patrones UX/UI y a mejorar la accesibilidad. El proyecto está rastreado en [este problema de GitHub](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,6 +91,10 @@ Para ejecutar pruebas a la biblioteca de componentes, ejecute el siguiente coman pnpm run test-ui-components ``` +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Adding Packages to the UI-Component Library We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: @@ -100,7 +104,7 @@ cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Useful Links - [Pruebas de Accesibilidad](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Orden de prioridad de las consultas de React Testing Library](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/espanol/how-to-work-on-the-docs-theme.md b/docs/i18n/espanol/how-to-work-on-the-docs-theme.md index 50274d25884..703b9c7b5f8 100644 --- a/docs/i18n/espanol/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/espanol/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Normalmente no vas a necesitar cambiar ninguna configuración o compliar el siti Install freeCodeCamp locally ([see the local setup guide](how-to-setup-freecodecamp-locally)), we bundled the CLI with the development tools so you can run the command below as needed from the root of the repo: -#### Serve and Launch the Documentation Site - ```console pnpm run docs:serve ``` > The documentation site should be available at + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/espanol/moderator-handbook.md b/docs/i18n/espanol/moderator-handbook.md index 34154809d49..55fd6c53bae 100644 --- a/docs/i18n/espanol/moderator-handbook.md +++ b/docs/i18n/espanol/moderator-handbook.md @@ -39,7 +39,7 @@ Puedes ayudarnos a organizar y clasificar los reportes de problemas mediante la Por favor, presta especial atención a las etiquetas `"help wanted"` y `"first timers only"`. Estos se deben agregar a los hilos que creas que se puedan abrir a posibles contribuyentes para realizar una pull request. -Se debe aplicar una etiqueta `"first timer only"` a un problema trivial (por ejemplo, una corrección de errores tipográficos) y debe incluir información adicional. Puedes utilizar esta [plantilla de respuesta](moderator-handbook.md#first-timer-only-issues) para la clasificación. +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### Cierre de solicitudes de extracción y problemas obsoletos, desactualizados e inactivos @@ -49,7 +49,7 @@ Se debe aplicar una etiqueta `"first timer only"` a un problema trivial (por eje - Si el colaborador solicita ayuda adicional o incluso tiempo, lo anterior se puede relajar y revisar después de que se dé una respuesta. En cualquier caso, los mods deben usar su mejor criterio para resolver el estado de PR. -> Le recomendamos que utilice esta lista de [ plantillas de respuesta ](moderator-handbook.md#reply-templates) estándar al evaluar los problemas. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### Moderación de solicitudes de extracción @@ -63,7 +63,7 @@ Las solicitudes de extracción (PRs) es la forma en que los colaboradores envía Puedes revisar las ediciones directamente en GitHub y decidir ahí si aceptar o no los cambios. Aqui debemos ser un poco mas cuidadosos, porque millones de personas leerán estos textos en la medida que vayan completando el programa de freeCodeCamp. ¿El pull request hace más claro el texto sin alargarlo demasiado? ¿Son las recomendaciones relevantes o pedantes en exceso? Recuerda que nuestro objetivo es que los retos sean lo más claro y cortos posibles. No son el lugar para detalles oscuros. Además, los colaboradores podrían intentar añadir enlaces hacia recursos en los desafíos. - Tu puedes cerrar pull requests no válidas y responderlas con estas [ plantillas de respuesta ](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). Si los cambios se ven bien, por favor asegúrese de dejar una aprobación con un comentario "LGTM" (Looks Good To Me). Una vez que un Pull Request recibe al menos dos aprobaciones (incluyendo la tuya) de los moderadores o del equipo de desarrollo, puedes hacer un Merge. @@ -75,7 +75,7 @@ Las solicitudes de extracción (PRs) es la forma en que los colaboradores envía Algunos colaboradores pueden intentar añadir pruebas adicionales para cubrir casos marginales. Debemos tener cuidado de no complicar demasiado el reto. Estos retos y sus pruebas deben ser tan simples e intuitivas como sea posible. Aparte de los desafíos del algoritmo y la sección de preparación de la entrevista, los estudiantes deberían ser capaces de resolver cada desafío en unos 2 minutos. - Tu puedes cerrar pull requests no válidas y responderlas con estas [ plantillas de respuesta ](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with an "LGTM" comment. Una vez que un Pull Request recibe al menos dos aprovaciones (incluyendo la tuya) de los moderadores o del equipo de desarrollo, puedes hacer un Merge. @@ -142,7 +142,7 @@ A menudo, una pull request requiere poco esfuerzo. You can usually tell this imm También hay situaciones en las que el colaborador está tratando de agregar un enlace a su sitio web, incluir una librería que creó o realizar una edición frívola que no ayuda a nadie más que a ellos mismos. -You can close these invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Otras Directrices para Moderadores en GitHub @@ -344,238 +344,3 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
Thanks for reading this, and thanks for helping the developer community! - -## Reply Templates - -These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. - -> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. - -### Thank You - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Thank you and congrats - -> Por dar las gracias y animar a los que han contribuido por primera vez. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Build Error - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Syncing Fork - -> When PR is not up to date with the `main` branch. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Merge Conflicts - -> When PR has merge conflicts that need to be resolved.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. - -### Duplicate - -> When PR is repetitive or a duplicate. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Closing Invalid Pull Requests - -> When PR is invalid. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> When PR adds links to external resources. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adding Comment About Newbie Mistakes - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Closing Invalid Issues - -> When an issue relates to the camper's code. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> When an issue is duplicate of an earlier issue. - -```markdown -Gracias por reportar este problema. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> When an issue is fixed in staging. - -```markdown -Gracias por reportar elproblema. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### `first timer only` Issues - -> When an issue is deemed to be eligible for first-time code contributors. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Requests for Assignment - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/espanol/reply-templates.md b/docs/i18n/espanol/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/espanol/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/espanol/security-hall-of-fame.md b/docs/i18n/espanol/security-hall-of-fame.md index 419c77388e2..810f73b45f2 100644 --- a/docs/i18n/espanol/security-hall-of-fame.md +++ b/docs/i18n/espanol/security-hall-of-fame.md @@ -8,4 +8,4 @@ Si bien no ofrecemos ninguna recompensa o botín en este momento, estamos agrade - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) trabajando con IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Gracias por sus contribuciones :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/german/FAQ.md b/docs/i18n/german/FAQ.md index f41554483d7..3e4fffc912f 100644 --- a/docs/i18n/german/FAQ.md +++ b/docs/i18n/german/FAQ.md @@ -1,64 +1,68 @@ -### GitHub und Open Source sind neu für mich. Wo sollte ich anfangen? +# Frequently Asked Questions -Lies unseren Leitfaden ["How to Contribute to Open Source"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). Es ist ein umfassendes Nachschlagewerk für einsteigerfreundliche Projekte. And it includes a lot of open-source contribution tips. +Answers to common questions. -### Was muss ich wissen, um zur Codebasis beizutragen? +## I am new to GitHub and Open Source. Where should I start? -freeCodeCamp läuft auf einem modernen JavaScript-Stack. Wenn du daran interessiert bist, zu unserer Codebasis beizutragen, solltest du mit JavaScript und einigen der von uns verwendeten Technologien wie Node.js, MongoDB, OAuth 2.0, React, Gatsby und Webpack vertraut sein. +Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### Kann ich die Ressourcen von freeCodeCamp übersetzen? +## What do I need to know to contribute to the codebase? -Ja - du kannst zu jeder der über 30 Sprachen beitragen, die wir auf unserer Übersetzungsplattform aktiviert haben. +freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -In einigen Sprachen haben wir von Nutzern erstellte Übersetzungen online. Wir haben vor, das freeCodeCamp in mehrere wichtige Weltsprachen zu lokalisieren. Du kannst alles darüber in unserer [Ankündigung](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/) lesen. +## Can I translate freeCodeCamp's resources? -Wenn du daran interessiert bist, zu Übersetzungen beizutragen, stelle bitte sicher, dass du zuerst [diesen Leitfaden](how-to-translate-files.md) gelesen hast. +Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. -### Kann ich Artikel für die freeCodeCamp News oder Videos für den YouTube-Kanal von freeCodeCamp beisteuern? +We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). -Ja - du kannst zu unserem Newsblog und unserem YouTube-Kanal beitragen. +If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -Wenn du daran interessiert bist, Artikel für freeCodeCamp News zu schreiben, schau dir bitte diesen [Veröffentlichungsleitfaden](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/) an. Lies außerdem unseren [Stil-Leitfaden](https://www.freecodecamp.org/news/developer-news-style-guide/), denn er wird dir helfen, aussagekräftige und effektive Artikel zu schreiben. +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? -Um uns zu helfen, Lehrvideos für unseren YouTube-Kanal zu erstellen, kannst du den [YouTube-Kanal-Leitfaden](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/) hier einsehen. +Yes - you can contribute to our publication blog and YouTube channel. -### Wie kann ich einen neuen Fehler melden? +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. -Wenn du glaubst, einen Fehler gefunden zu haben, lies zuerst den Artikel ["Wie melde ich einen Fehler"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) und befolge die darin enthaltenen Anweisungen. +To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -Wenn du sicher bist, dass es sich um einen neuen Fehler handelt, kannst du einen neuen Issue auf GitHub erstellen. Gib so viele Informationen wie möglich an, damit wir den Fehler reproduzieren können. Wir haben eine vorgefertigte Issue-Vorlage, die dir dabei hilft. +## How can I report a new bug? -Bitte beachte, dass diese GitHub Issues für Codebasis-bezogene Probleme und Diskussionen gedacht sind - nicht um Hilfe beim Programmieren zu bekommen. Im Zweifelsfall solltest du [Hilfe im Forum suchen](https://forum.freecodecamp.org), bevor du ein GitHub Issue erstellst. +If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -### Wie kann ich ein Sicherheitsproblem melden? +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -Bitte erstelle keine GitHub Issues für Sicherheitsprobleme. Bitte beachte stattdessen [unsere Sicherheitsrichtlinien](https://contribute.freecodecamp.org/#/security). +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### Ich bin ein Student. Kann ich für akademische Credits an einem Feature arbeiten? +## How can I report a security issue? -Ja. Bitte beachte, dass wir nicht in der Lage sind, uns an Fristen oder Papierkram zu halten, die von deiner Hochschule oder Universität vorgeschrieben werden könnten. Wir erhalten viele Pull-Requests und Code-Beiträge von freiwilligen Entwicklern, und wir respektieren ihre Zeit und ihren Einsatz. Aus Respekt vor allen anderen Beiträgen werden wir keinen PR eine besondere Priorität einräumen, nur weil sie einen Schulbezug haben. +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -Wir bitten dich, vorausschauend zu planen und deine Beiträge zum Code in diesem Sinne zu gestalten. +## I am a student. Can I work on a feature for academic credits? -### Was bedeuten die verschiedenen Labels, mit denen die Themen versehen sind? +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -Die Code-Maintainer [Sortieren](https://en.wikipedia.org/wiki/Software_bug#Bug_management) Issues und Pull Requests nach ihrer Priorität, Schwere und anderen Faktoren. Du kannst [hier](https://github.com/freecodecamp/freecodecamp/labels) ein komplettes Glossar mit ihren Bedeutungen finden. +We request you to plan ahead and work on code contributions with this in mind. -### Wo fange ich an, wenn ich an einem Issue arbeiten will? +## What do these different labels that are tagged on issues mean? -Du solltest über [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) oder [**`first timers only`**](https://github. com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) Issues gehen, um einen schnellen Überblick darüber zu bekommen, was für dich zur Verfügung steht. +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). + +## Where do I start if I want to work on an issue? + +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] **`help wanted`** Issues sind frei zugänglich und du musst nicht um Erlaubnis bitten, bevor du sie bearbeitest. Issues mit dem **`first timers only`**-Label sind jedoch spezielle Issues, die für Leute gedacht sind, die noch nicht zur freeCodeCamp Codebasis beigetragen haben. -### Ich habe einen Schreibfehler gefunden. Sollte ich ein Issue melden, bevor ich einen Pull Request erstellen kann? +## I found a typo. Should I report an issue before I can make a pull request? -Bei Schreibfehlern und anderen Änderungen am Wortlaut kannst du direkt Pull Requests öffnen, ohne zuerst ein Issue zu erstellen. Bitte vergewissere dich, dass du Details in der Pull Request-Beschreibung angibst, damit wir deinen Beitrag besser verstehen und überprüfen können - selbst wenn es nur eine kleine Änderung ist. +For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. -Bitte erstelle ein Issue, wenn du größere Aspekte der Codebasis oder des Studienplans diskutieren möchtest. +Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### Wie kann ich mir ein Issue zuweisen lassen? +## How can I get an issue assigned to me? -Normalerweise weisen wir die Issues nur langjährigen Mitwirkenden zu. Stattdessen befolgen wir die folgende Richtlinie, um allen gerecht zu werden: +We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: 1. Wir werden höchstwahrscheinlich den ersten Pull Request mergen, der das Problem behebt. 2. Wenn mehrere Mitwirkende etwa zur gleichen Zeit einen Pull Request für dasselbe Problem öffnen, geben wir dem Pull Request den Vorrang, der das Problem am besten löst. Einige der Dinge, die wir berücksichtigen: @@ -69,37 +73,37 @@ Normalerweise weisen wir die Issues nur langjährigen Mitwirkenden zu. Stattdess - Hast du die Checkliste für Pull Requests befolgt? - Hast du deinem Pull Request einen aussagekräftigen Titel gegeben? -### Ich bin daran interessiert, beim freeCodeCamp als Moderator zu mitzuwirken. Wo sollte ich anfangen? +## I am interested in being a moderator at freeCodeCamp. Where should I start? -Unsere Community-Moderatoren sind unsere Helden. Their voluntary contributions make freeCodeCamp a safe and welcoming community. +Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. First and foremost, we would need you to be an active participant in the community, and live by our [code of conduct](https://www.freecodecamp.org/news/code-of-conduct/) (not just enforce it). -Hier sind einige empfohlene Wege für einige unserer Plattformen: +Here are some recommended paths for some of our platforms: - To be a **Discord/Chat** moderator, have an active presence in our chat and have positive engagements with others, while also learning and practicing how to deal with potential conflicts that may arise. - To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information. - To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself). -Sei insgesamt respektvoll gegenüber anderen. Wir sind Menschen aus allen Teilen der Welt. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. -If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open-Source-Arbeit ist freiwillige Arbeit und unsere Zeit ist begrenzt. Wir erkennen an, dass dies wahrscheinlich auch in deiner Situation der Fall ist. So we emphasize being **consistent** rather than engaging in the community 24/7. +If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### Ich komme mit etwas nicht weiter, das in dieser Dokumentation nicht enthalten ist. +## I am stuck on something that is not included in this documentation. -**Frag einfach nach Hilfe in:** +**Feel free to ask for help in:** - der `Contributors` Kategorie von [unserem Community-Forum](https://forum.freecodecamp.org/c/contributors). - dem `#Contributors` Kanal auf [unserem Chatserver](https://discord.gg/PRyKn3Vbay). -Wir freuen uns, dir dabei zu helfen, einen Beitrag zu den Themen zu leisten, an denen du gerne arbeiten möchtest. Wenn du uns in den entsprechenden Issue Threads Fragen stellst, helfen wir dir gerne weiter. Achte darauf, dass du nach deiner Frage suchst, bevor du eine neue stellst. +We are excited to help you contribute to any of the topics that you would like to work on. If you ask us questions on the related issue threads, we will be glad to clarify. Be sure to search for your question before posting a new one. -Vielen Dank im Voraus für deine Höflichkeit und Geduld. Vergiss nicht, dass diese Community hauptsächlich von Freiwilligen betrieben wird. +Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### Zusätzliche Hilfe +## Additional Assistance -Wenn du Fragen zum Stack, zur Architektur der Codebasis, zu Übersetzungen oder zu anderen Themen hast, kannst du dich gerne an unser Team [im Forum](https://forum.freecodecamp.org/g/team) wenden. +If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**Du kannst unserem Entwicklerteam eine E-Mail schicken an: `dev[at]freecodecamp.org`** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/german/_sidebar.md b/docs/i18n/german/_sidebar.md index 46fcd456fe6..fb9d2c1e463 100644 --- a/docs/i18n/german/_sidebar.md +++ b/docs/i18n/german/_sidebar.md @@ -8,7 +8,6 @@ - **Mitwirkung am Code** - [Set up freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Follow best-practices](codebase-best-practices.md) - - [Open a pull request](how-to-open-a-pull-request.md) - [Work on Codebase](how-to-contribute-to-the-codebase.md) - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) - [Work on Component Library](how-to-work-on-the-component-library.md) @@ -19,11 +18,13 @@ - [Work on Cypress tests](how-to-add-cypress-tests.md) - [Work on Video Challenges](how-to-help-with-video-challenges.md) - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Zusätzliche Leitfäden** - [Curriculum-Dateistruktur verstehen](curriculum-file-structure.md) - [Ausgehende E-Mails lokal debuggen](how-to-catch-outgoing-emails-locally.md) - [freeCodeCamp unter Windows einrichten (WSL)](how-to-setup-wsl.md) - - [Benutzer-Token Workflow](user-token-workflow.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) + - [User Token Workflow](user-token-workflow.md) - [Troubleshooting Development Issues](troubleshooting-development-issues.md) - [Authors Analytics Manual](authors-analytics-manual.md) @@ -31,10 +32,11 @@ - **Handbücher** (für Mitarbeiter & Moderatoren) - [Moderatorenhandbuch](moderator-handbook.md) - - [Language Lead Handbuch](language-lead-handbook.md) - - [DevOps-Handbuch](devops.md) - - [Kurse VSCode Erweiterung](courses-vscode-extension.md) - - [Eine neue Sprache aktivieren](how-to-enable-new-languages.md) + - [Reply Templates](reply-templates.md) + - [Language Lead Handbook](language-lead-handbook.md) + - [DevOps Handbook](devops.md) + - [Courses VSCode Extension](courses-vscode-extension.md) + - [Enable New Language](how-to-enable-new-languages.md) --- diff --git a/docs/i18n/german/devops.md b/docs/i18n/german/devops.md index 9695fad4f5f..0795bc6e4ef 100644 --- a/docs/i18n/german/devops.md +++ b/docs/i18n/german/devops.md @@ -203,19 +203,19 @@ Du kannst die genaue Version, die eingesetzt wurde, in den Build- und Deployment Es gibt einige bekannte Einschränkungen und Kompromisse bei der Beta-Version der Plattform. -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Benutzer der Beta-Version haben ein von der Produktionsversion getrenntes Konto.** Die Beta-Version verwendet eine von der Produktionsversion physisch getrennte Datenbank. So können wir versehentliche Datenverluste oder Änderungen verhindern. The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** Es wird erwartet, dass die Deployments häufig und in schnellen Iterationen erfolgen, manchmal mehrmals am Tag. As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### Schicke keine normalen Nutzer auf diese Seite, um eine Korrektur zu bestätigen. +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** Die Beta-Seite ist und war immer dazu da, die lokale Entwicklung und das Testen zu unterstützen, nichts anderes. Es ist kein Versprechen auf das, was kommt, sondern ein Ausblick auf das, woran gearbeitet wird. -- #### Die Anmeldeseite kann anders aussehen als die Produktionsseite +- **Sign in page may look different than production** Wir verwenden einen Test-Mandanten für freeCodeCamp.dev auf Auth0 und haben daher nicht die Möglichkeit, eine benutzerdefinierte Domain einzustellen. Dies führt dazu, dass alle Weiterleitungsaufrufe und die Anmeldeseite auf einer Standarddomain erscheinen, wie z.B.: `https://freecodecamp-dev.auth0.com/`. Dies hat keinen Einfluss auf die Funktionalität und ist so nah an der Produktion, wie wir es nur bekommen können. diff --git a/docs/i18n/german/how-to-enable-new-languages.md b/docs/i18n/german/how-to-enable-new-languages.md index 965c7d8840c..f9cff2316ff 100644 --- a/docs/i18n/german/how-to-enable-new-languages.md +++ b/docs/i18n/german/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Aktivieren von lokalisierten Videos +### Enabling Localized Videos Für die Videoaufgaben musst du ein paar Dinge ändern. First, add the new locale to the GraphQL query in the `client/src/templates/Challenges/video/Show.tsx` file. Zum Beispiel, indem man Dothraki zur Abfrage hinzufügt: @@ -283,7 +283,7 @@ Du musst die folgenden Dateien von `/client/i18n/locales/english` nach `/client/ - `motivation.json` - `trending.json` -## Übersetzungen lokal testen +## Testing Translations Locally Wenn du Übersetzungen lokal testen möchtest, bevor du sie zu unserem main-Repository hinzufügst, kannst du die Änderungen am Crowdin-Workflow überspringen. Folge den Schritten zur Aktivierung einer Sprache, lade dann die Übersetzungen von Crowdin herunter und lade sie in deinen lokalen Code. @@ -303,11 +303,11 @@ Once these are in place, you should be able to run `pnpm run develop` to view yo Um die News für eine neue Sprache bereitzustellen, musst du zwei PRs erstellen. Ein PR geht an das [CDN Repo](https://github.com/freeCodeCamp/cdn) und der andere an das [News Repo](https://github.com/freeCodeCamp/news). -## Bereite das CDN Repo für die neue Sprache vor +## Prep the CDN Repo for the New Language News bezieht während des Builds angesagte Links und Artikeltitel aus unserem CDN und fügt sie in den Footer ein. News holt sich während des Builds auch Day.js-Dateien aus dem CDN, um Datum und Uhrzeit für jede Sprache zu lokalisieren. -### Hinzufügen einer YAML-Datei für angesagte Artikel +### Add a YAML File for Trending Articles Klone das [CDN Repo](https://github.com/freeCodeCamp/cdn) und erstelle einen neuen Zweig. @@ -329,7 +329,7 @@ article3link: ... ... ``` -### Füge eine Day.js Gebietsschemadatei (Locale) für die neue Sprache hinzu +### Add a Day.js Locale File for the New Language Standardmäßig enthält Day.js nur Englisch als Gebietsschema. Damit es mit anderen Sprachen funktioniert, musst du eine neue Day.js Gebietsschemadatei zum CDN hinzufügen. @@ -367,13 +367,13 @@ Kopiere den Code des Gebietsschema aus Day.js von dem neuen Tab in die neue Date Erstelle dann einen PR für das CDN-Repository, um sowohl die YAML- als auch die Day.js-Dateien zur Überprüfung hinzuzufügen. -## Bereite das News Repo auf die neue Sprache vor +## Prep the News Repo for the New Language Das [News Repo](https://github.com/freeCodeCamp/news) zieht die Daten von einer Ghost-Instanz, die Dateien, die du dem CDN hinzugefügt hast, erstellt die News und stellt sie bereit. > [!WARN] Pull requests to the News repo _must_ come from the same repo. Du solltest bei diesem Schritt nicht von einem Fork aus arbeiten. -### Anpassung der Hauptkonfigurationsdatei (Main Config) +### Modify the Main Config File Klone das News-Repository und erstelle einen neuen Zweig. @@ -407,7 +407,7 @@ const algoliaIndices = { }; ``` -### Füge die i18next JSON-Dateien für die neue Sprache hinzu +### Add the i18next JSON Files for the New Language Als nächstes gehst du in das Verzeichnis `config/i18n/locales`, erstellst einen neuen Ordner und gibst ihm den Namen der neuen Sprache, die du hinzufügst. Wenn du zum Beispiel Dothraki News startest, erstelle einen neuen Ordner namens `dothraki`. diff --git a/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md index 7abe9cdeb1a..e526596881f 100644 --- a/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Folge dieser Anleitung, um die freeCodeCamp mobile App lokal auf deinem System e Some of the contribution workflows – like fixing bugs in the codebase – need you to run the freeCodeCamp app locally. -### How to Prepare your Local Machine +## How to Prepare your Local Machine Installiere zunächst die erforderliche Software für dein Betriebssystem. -#### Prerequisites +### Prerequisites | Voraussetzung | Version | Notizen | | --------------------------------------------- | ------- | ------------------------------------------------------------- | @@ -26,7 +26,7 @@ dart --version Sobald du die notwendigen Ressourcen installiert hast, musst du deine Entwicklungsumgebung vorbereiten. Dies ist bei vielen Entwicklungsabläufen üblich, und du musst dies nur einmal tun. -##### Befolge diese Schritte, um deine Entwicklungsumgebung vorzubereiten: +#### Follow these steps to get your development environment ready: 1. Installiere [Git](https://git-scm.com/) oder deinen bevorzugten Git-Client, falls du das nicht schon getan hast. Aktualisiere die neueste Version; die Version, die mit deinem Betriebssystem mitgeliefert wurde, ist möglicherweise veraltet. @@ -361,7 +361,7 @@ Folge diesen Schritten: git push origin branch/name-here ``` -## Einen Pull Request (PR) vorschlagen +## Proposing a Pull Request (PR) Nachdem du deine Änderungen übertragen hast, kannst du hier nachlesen, [wie man einen Pull Request erstellt](how-to-open-a-pull-request.md). @@ -374,7 +374,7 @@ A quick reference to the commands that you will need when working locally. | `npm ci` | Installs / re-install all dependencies and bootstraps the different services. | | `npm run seed` | Parses all the challenge markdown files and inserts them into MongoDB. | --> -## Fehlerbehebung +## Troubleshooting ### Probleme bei der Installation der empfohlenen Voraussetzungen @@ -398,7 +398,7 @@ Wenn du bei der Installation der Abhängigkeiten Fehler erhältst, vergewissere Be patient as the first-time setup can take a while depending on your network bandwidth. -## Hilfe bekommen +## Getting Help Wenn du nicht weiterkommst und Hilfe brauchst, kannst du deine Fragen in der [Kategorie "Contributors" in unserem Forum](https://forum.freecodecamp.org/c/contributors) oder im ["Contributors "Chatraum](https://discord.gg/PRyKn3Vbay) stellen. diff --git a/docs/i18n/german/how-to-work-on-coding-challenges.md b/docs/i18n/german/how-to-work-on-coding-challenges.md index 92b0b4ded5d..2a52e723045 100644 --- a/docs/i18n/german/how-to-work-on-coding-challenges.md +++ b/docs/i18n/german/how-to-work-on-coding-challenges.md @@ -482,13 +482,15 @@ Du kannst eine Aufgabe auch einzeln testen, indem du die folgenden Schritte ausf ``` pnpm run test -- -g challenge-title-goes-here ``` -Sobald du sichergestellt hast, dass jede Aufgabe, an der du gearbeitet hast, die Tests besteht, [erstelle bitte einen Pull-Request](how-to-open-a-pull-request.md). - > [!TIP] Du kannst die Umgebungsvariable `LOCALE` in der `.env` auf die Sprache der Aufgabe(n) setzen, die du testen willst. > > Die derzeit akzeptierten Werte sind `englisch` und `chinesisch`, wobei `englisch` standardmäßig eingestellt ist. -### Nützliche Links +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links Aufgaben erstellen und bearbeiten: diff --git a/docs/i18n/german/how-to-work-on-localized-client-webapp.md b/docs/i18n/german/how-to-work-on-localized-client-webapp.md index 70a384890d7..c8084e32bfc 100644 --- a/docs/i18n/german/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/german/how-to-work-on-localized-client-webapp.md @@ -266,7 +266,11 @@ Es wäre auch schön, wenn die Schlüssel in allen Dateien die gleiche Reihenfol > [!NOTE] The underscore (`_`) is a reserved character for keys in the client-side files. In der [Dokumentation](https://www.i18next.com/translation-function/plurals) erfährst du, wie sie verwendet werden. -## Hilfreiche Dokumentation +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Helpful Documentation - [react-i18next Dokumente](https://react.i18next.com/latest/usetranslation-hook) - [i18next Dokumente](https://www.i18next.com/translation-function/essentials) diff --git a/docs/i18n/german/how-to-work-on-practice-projects.md b/docs/i18n/german/how-to-work-on-practice-projects.md index 2845a6dc287..20d12a9cb94 100644 --- a/docs/i18n/german/how-to-work-on-practice-projects.md +++ b/docs/i18n/german/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ A one-off script that automatically updates the frontmatter in a project's markd ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/german/how-to-work-on-the-component-library.md b/docs/i18n/german/how-to-work-on-the-component-library.md index 58f2e03ea47..428e2c327da 100644 --- a/docs/i18n/german/how-to-work-on-the-component-library.md +++ b/docs/i18n/german/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). - # How to Work on the Component Library +Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > freeCodeCamp has been using Bootstrap components in the UI. However, we are moving away from it and building our own component library, which helps standardize our UX/UI patterns and improve accessibility. The project is tracked in [this GitHub issue](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,6 +91,10 @@ To run tests against the component library, run the following command from the r pnpm run test-ui-components ``` +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Adding Packages to the UI-Component Library We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: @@ -100,7 +104,7 @@ cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Useful Links - [Testing for Accessibility](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Order of priority of React Testing Library's queries](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/german/how-to-work-on-the-docs-theme.md b/docs/i18n/german/how-to-work-on-the-docs-theme.md index 0d040634597..0e3c5c2d472 100644 --- a/docs/i18n/german/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/german/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Typically you would not need to change any configuration or build the site local Install freeCodeCamp locally ([see the local setup guide](how-to-setup-freecodecamp-locally)), we bundled the CLI with the development tools so you can run the command below as needed from the root of the repo: -#### Serve and Launch the Documentation Site - ```console pnpm run docs:serve ``` > The documentation site should be available at + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/german/moderator-handbook.md b/docs/i18n/german/moderator-handbook.md index 68b4cc1c2cc..3f797c6a4f4 100644 --- a/docs/i18n/german/moderator-handbook.md +++ b/docs/i18n/german/moderator-handbook.md @@ -39,7 +39,7 @@ Du kannst uns helfen, die Issues zu ordnen und einzuteilen, indem du Labels aus Bitte achte besonders auf die Label `"help wanted"` und `"first timers only"`. Diese sollen zu Threads hinzugefügt werden, von denen du denkst, dass sie für potenzielle Mitwirkende geöffnet werden können, um einen Pull-Request zu erstellen. -A `"first timers only"` label should be applied to a trivial issue (ie a typo fix) and should include additional information. Du kannst diese [Antwortvorlage](moderator-handbook.md#first-timer-only-issues) für die Triage verwenden. +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### Schließen veralteter, inaktiver Issues und Pull-Requests @@ -49,7 +49,7 @@ A `"first timers only"` label should be applied to a trivial issue (ie a typo fi - Wenn der Beitragende um zusätzliche Hilfe oder sogar Zeit bittet, kann das oben Gesagte gelockert und nach einer Antwort erneut überprüft werden. In jedem Fall sollten die Moderatoren nach bestem Wissen und Gewissen den Status der ausstehenden PR klären. -> [!TIP] Wir empfehlen dir, diese Liste von standardisierten [Antwortvorlagen](moderator-handbook.md#reply-templates) zu verwenden, wenn du Issues bearbeitest. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### Pull-Requests moderieren @@ -63,7 +63,7 @@ Pull Requests (PRs) sind die Art und Weise, wie Mitwirkende Änderungen an das f Du kannst sie auch direkt auf GitHub überprüfen und entscheiden, ob du sie zusammenführen möchtest. Wir müssen hier etwas vorsichtiger sein, denn Millionen von Menschen werden diesem Text begegnen, wenn sie den freeCodeCamp-Studienplan durcharbeiten. Macht der Pull-Request den Text klarer, ohne ihn viel länger zu machen? Sind die Änderungen relevant und nicht übermäßig pedantisch? Denke daran, dass unser Ziel ist, dass die Aufgaben so deutlich und so kurz wie möglich sind. Sie sind nicht der Ort für unklare Details. Die Mitwirkenden könnten versuchen, Links zu Ressourcen zu den Aufgaben hinzuzufügen. - Mit diesen [Antwortvorlagen](moderator-handbook.md#closing-invalid-pull-requests) kannst du ungültige Pull-Requests schließen und darauf antworten. + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with a "LGTM" (Looks Good To Me) comment. Sobald ein Pull Request mindestens zwei Genehmigungen (einschließlich deiner) von den Moderatoren oder dem Entwicklungsteam erhält, kannst du ihn zusammenführen. @@ -75,7 +75,7 @@ Pull Requests (PRs) sind die Art und Weise, wie Mitwirkende Änderungen an das f Einige Mitwirkende werden versuchen, zusätzliche Tests hinzuzufügen, um spitzfindige Sonderfälle abzudecken. Wir müssen aufpassen, dass wir die Aufgabe nicht zu kompliziert machen. Diese Aufgaben und ihre Tests sollten so einfach und intuitiv wie möglich sein. Abgesehen von den Algorithmusaufgaben und dem Abschnitt zur Interviewvorbereitung sollten die Teilnehmer/innen in der Lage sein, jede Aufgabe innerhalb von etwa 2 Minuten zu lösen. - Mit diesen [Antwortvorlagen](moderator-handbook.md#closing-invalid-pull-requests) kannst du ungültige Pull-Requests schließen und darauf antworten. + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with an "LGTM" comment. Sobald ein Pull-Request mindestens zwei Genehmigungen (einschließlich deiner) von den Moderatoren oder dem Entwicklungsteam erhält, kannst du ihn zusammenführen. @@ -142,7 +142,7 @@ Oft ist ein Pull-Request mit wenig Aufwand verbunden. You can usually tell this Es gibt auch Situationen, in denen der/die Mitwirkende versucht, einen Link zu seiner/ihrer Website hinzuzufügen, eine von ihm/ihr erstellte Bibliothek einzubinden oder eine unseriöse Bearbeitung vorzunehmen, die niemandem außer ihm/ihr selbst hilft. -You can close these invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Other Guidelines for Moderators on GitHub @@ -344,238 +344,3 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
Thanks for reading this, and thanks for helping the developer community! - -## Reply Templates - -These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. - -> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. - -### Thank You - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Thank you and congrats - -> For thanking and encouraging first-time contributors. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Build Error - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Syncing Fork - -> When PR is not up to date with the `main` branch. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Merge Conflicts - -> When PR has merge conflicts that need to be resolved.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. - -### Duplicate - -> When PR is repetitive or a duplicate. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Closing Invalid Pull Requests - -> When PR is invalid. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> When PR adds links to external resources. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adding Comment About Newbie Mistakes - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Closing Invalid Issues - -> When an issue relates to the camper's code. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> When an issue is duplicate of an earlier issue. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> When an issue is fixed in staging. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### `first timer only` Issues - -> When an issue is deemed to be eligible for first-time code contributors. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Requests for Assignment - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/german/reply-templates.md b/docs/i18n/german/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/german/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/german/security-hall-of-fame.md b/docs/i18n/german/security-hall-of-fame.md index b6175d3a3b5..195ea34cb29 100644 --- a/docs/i18n/german/security-hall-of-fame.md +++ b/docs/i18n/german/security-hall-of-fame.md @@ -8,4 +8,4 @@ Auch wenn wir im Moment keine Belohnungen oder Swags anbieten, sind wir diesen g - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) arbeitet mit IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Vielen Dank für eure Beiträge :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/italian/FAQ.md b/docs/i18n/italian/FAQ.md index a439717fa90..1b6ec97bc6a 100644 --- a/docs/i18n/italian/FAQ.md +++ b/docs/i18n/italian/FAQ.md @@ -1,64 +1,68 @@ -### Sono nuovo in GitHub e nel mondo Open Source. Da dove dovrei iniziare? +# Frequently Asked Questions -Leggi la nostra guida ["Come contribuire all'Open Source"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). È un compendio completo per progetti adatti ai neofiti. And it includes a lot of open-source contribution tips. +Answers to common questions. -### Cosa devo sapere per contribuire al codebase? +## I am new to GitHub and Open Source. Where should I start? -freeCodeCamp è basato su uno stack JavaScript moderno. Se hai interesse a contribuire, dovrai avere un po' di familiarità con JavaScript e alcune delle tecnologie che usiamo come Node.js, MongoDB, OAuth 2.0, React, Gatsby e Webpack. +Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### Posso tradurre le risorse di freeCodeCamp? +## What do I need to know to contribute to the codebase? -Sì, puoi contribuire a ognuna delle oltre 30 lingue abilitate sulla nostra piattaforma di traduzione. +freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -Abbiamo le traduzioni fatte dagli utenti live in alcune lingue. Abbiamo intenzione di localizzare freeCodeCamp nelle lingue più usate nel mondo. Puoi leggere tutto su questo argomento in questo [articolo](https://www.freecodecamp.org/italian/news/come-aiutare-a-tradurre-freecodecamp-nella-tua-lingua/). +## Can I translate freeCodeCamp's resources? -Se sei interessato a contribuire alla traduzione, per favore assicurati di [leggere questa guida](how-to-translate-files.md) prima di tutto. +Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. -### Posso contribuire agli articoli alla pubblicazione di freeCodeCamp o ai video del canale YouTube? +We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). -Sì, puoi contribuire alla nostra pubblicazione e al canale YouTube. +If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -Se vuoi scrivere articoli per la pubblicazione di freeCodeCamp, per favore visita la nostra [guida di pubblicazione](https://www.freecodecamp.org/italian/news/how-to-write-for-freecodecamp-news/). In aggiunta, per favore leggi la nostra [guida allo stile](https://www.freecodecamp.org/italian/news/la-guida-allo-stile-di-pubblicazione-di-freecodecamp/) che ti aiuterà a scrivere articoli migliori e più efficaci. +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? -Per aiutarci a fare video educativi sul nostro canale YouTube, puoi seguire la [guida al canale YouTube qui](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). +Yes - you can contribute to our publication blog and YouTube channel. -### Come posso segnalare un nuovo bug? +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. -Se pensi di avere trovato un bug, prima leggi l'articolo ["How to report a bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) e segui le istruzioni. +To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -Se sei certo che sia un nuovo bug, vai avanti e crea una issue su GitHub. Assicurati di includere quante più informazioni possibili in modo che sia possibile riprodurre il bug. Abbiamo un modello predefinito per aiutarti con la creazione di un'issue. +## How can I report a new bug? -Per favore nota che queste issue in GitHub sono per problemi e discussioni sul codebase, non per chiedere aiuto mentre impari a programmare. Se hai dubbi, dovresti [chiedere assistenza sul forum](https://forum.freecodecamp.org) prima di creare un'issue su GitHub. +If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -### Come posso segnalare un problema di sicurezza? +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -Per favore non creare issue su GitHub per problemi di sicurezza. Invece, per favore [segui la nostra politica di sicurezza](https://contribute.freecodecamp.org/#/security). +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### Sono uno studente. Posso lavorare su una funzionalità ottenendo crediti accademici? +## How can I report a security issue? -Sì. Per favore nota che non siamo in grado di impegnarci in alcun modo per limiti di tempo o questioni burocratiche che possono essere richiesti dal tuo college o dalla tua università. Riceviamo molte pull request e contributi al codice da sviluppatori volontari e rispettiamo il loro tempo e i loro sforzi. Per rispetto di tutti gli altri nostri contributori, non daremo delle priorità particolari ad alcuna PR solo perché è legata a impegni accademici. +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -Ti chiediamo di pianificare in anticipo e lavorare sui contributi al codice tenendolo a mente. +## I am a student. Can I work on a feature for academic credits? -### Cosa significano le diverse etichette che vengono associate alle issue? +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -I manutentori del codice [smistano](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issue e pull request a seconda della loro priorità, gravità e altri fattori. Puoi trovare [un glossario dei loro significati qui.](https://github.com/freecodecamp/freecodecamp/labels). +We request you to plan ahead and work on code contributions with this in mind. -### Da dove comincio se voglio lavorare su una issue? +## What do these different labels that are tagged on issues mean? -Dovresti guardare le issue taggate con [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) o [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) per una veloce overview di cosa è disponibile per lavorarci su. +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). + +## Where do I start if I want to work on an issue? + +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] Le issue **`help wanted`** sono a disposizione e non devi chiedere permessi per poterci lavorare. Tuttavia, le issue con l'etichetta **`first timers only`** sono problemi speciali che sono stati progettati per le persone che non hanno contribuito al codice di freeCodeCamp prima d'ora. -### Ho trovato un errore di ortografia. Dovrei creare un'issue prima di poter fare una pull request? +## I found a typo. Should I report an issue before I can make a pull request? -Per errori di ortografia e altre modifiche di parole, puoi aprire direttamente una pull request senza prima creare un'issue. Per favore assicurati di scrivere dettagli nella descrizione della pull request per aiutarci a capire e rivedere il tuo contributo, anche se è un piccolo cambiamento. +For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. -Per favore crea un'issue se vuoi discutere aspetti più ampi del codebase o del curriculum. +Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### Come posso farmi assegnare un'issue? +## How can I get an issue assigned to me? -In genere non assegnamo issue se non a contributori esperti. Invece, seguiamo la seguente politica per essere giusti nei confronti di tutti: +We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: 1. Abbiamo maggiori probabilità di fare il merge della prima pull request che affronta il problema. 2. Nel caso di più contributori che aprono una pull request per lo stesso problema all'incirca allo stesso tempo, daremo la priorità alla pull request che affronta al meglio la questione. Alcune delle cose che consideriamo: @@ -69,37 +73,37 @@ In genere non assegnamo issue se non a contributori esperti. Invece, seguiamo la - Hai seguito la checklist delle pull request? - Hai dato alla tua pull request un titolo esplicativo? -### Sono interessato a essere moderatore per freeCodeCamp. Da dove dovrei iniziare? +## I am interested in being a moderator at freeCodeCamp. Where should I start? -I moderatori della nostra community sono i nostri eroi. Il loro contributo volontario rende freeCodeCamp una community sicura e accogliente. +Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. -Prima di tutto, avremmo bisogno che tu sia un partecipate attivo della nostra community e segua il nostro [codice di condotta](https://www.freecodecamp.org/italian/news/codice-di-condotta/) (non solo che tu lo faccia rispettare). +First and foremost, we would need you to be an active participant in the community, and live by our [code of conduct](https://www.freecodecamp.org/news/code-of-conduct/) (not just enforce it). -Ecco alcuni percorsi consigliati per alcune delle nostre piattaforme: +Here are some recommended paths for some of our platforms: - Per essere un moderatore per **Discord/Chat**, abbi una presenza attiva nella nostra chat e interazioni positive con gli altri, e intanto impara come gestire i potenziali conflitti che possono verificarsi. - Per essere un moderatore del **Forum**, in maniera simile ai moderatori della chat, abbi una presenza attiva e interagisci con gli utenti, supportando gli altri nel loro percorso di crescita e dando feedback quando richiesto. Dai un occhiata al [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) per maggiori informazioni. - Per essere un moderatore su **GitHub**, aiuta a processare le issue create su GitHub per vedere se sono valide e (idealmente) prova a proporre soluzioni per queste issue che possono essere applicate da altri (o da te stesso). -Nel complesso, rispetta gli altri. Siamo tutti umani. Con questo in mente, per favore considera anche l'uso di un linguaggio incoraggiante e supportivo e tieni a mente la comunicazione tra culture diverse. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. -Se metti in pratica quando sopra **con costanza** e i nostri moderatori ti raccomandano, un membro dello staff si farà avanti e ti darà il benvenuto nel team dei moderatori. Il lavoro open source è un lavoro volontario e il nostro tempo è limitato. Riconosciamo che questo è probabilmente vero anche nel tuo caso. Quindi sottolineiamo di essere **consistenti** piuttosto che impegnarsi nella comunità 24/7. +If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. -Dai un'occhiata al [Manuale per moderatori](moderator-handbook.md) per una lista più esaustiva di altre responsabilità e aspettative che abbiamo del nostro team di moderatori. +Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### Sono bloccato su qualcosa che non è incluso in questa documentazione. +## I am stuck on something that is not included in this documentation. -**Se hai bisogno chiedi liberamente aiuto in:** +**Feel free to ask for help in:** - La categoria `Contributors` del [forum della nostra community](https://forum.freecodecamp.org/c/contributors). - Il canale `#Contributors` sul nostro [chat server](https://discord.gg/PRyKn3Vbay). -Siamo entusiasti di aiutarti a contribuire in ognuno degli ambiti su cui vorresti lavorare. Se fai domande sul relativo thread di un'issue, saremo lieti di rispondere. Assicurati di fare una ricerca per la tua domanda prima di porne una nuova. +We are excited to help you contribute to any of the topics that you would like to work on. If you ask us questions on the related issue threads, we will be glad to clarify. Be sure to search for your question before posting a new one. -Ti ringraziamo in anticipo per essere educato e paziente. Ricordati che questa comunità è gestita principalmente da volontari. +Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### Assistenza aggiuntiva +## Additional Assistance -Se hai domande sullo stack, sull'architettura del database, sulle traduzioni o su qualsiasi altra cosa, sentiti libero di rivolgerti al nostro team dello staff [sul forum](https://forum.freecodecamp.org/g/team). +If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**Puoi scrivere una mail allo staff di sviluppo a: `dev[at]freecodecamp.org`** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/italian/_sidebar.md b/docs/i18n/italian/_sidebar.md index 16d26b5de22..872b9ceef5e 100644 --- a/docs/i18n/italian/_sidebar.md +++ b/docs/i18n/italian/_sidebar.md @@ -8,33 +8,35 @@ - **Contribuire al codice** - [Impostare freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Seguire le migliori pratiche](codebase-best-practices.md) - - [Aprire una pull request](how-to-open-a-pull-request.md) - - [Lavorare sul codebase](how-to-contribute-to-the-codebase.md) - - [Lavorare sulle sfide di programmazione](how-to-work-on-coding-challenges.md) - - [Lavorare sulla libreria dei componenti](how-to-work-on-the-component-library.md) - - [Lavorare sui progetti di pratica](how-to-work-on-practice-projects.md) - - [Lavorare sull'app mobile](how-to-setup-freecodecamp-mobile-app-locally.md) - - [Lavorare sui tutorial con CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) - - [Lavorare sull'app web localizzata](how-to-work-on-localized-client-webapp.md) - - [Lavorare sui test Cypress ](how-to-add-cypress-tests.md) - - [Lavorare sulle sfide video](how-to-help-with-video-challenges.md) - - [Lavorare sulla documentazione](how-to-work-on-the-docs-theme.md) + - [Work on Codebase](how-to-contribute-to-the-codebase.md) + - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) + - [Work on Component Library](how-to-work-on-the-component-library.md) + - [Work on Practice Projects](how-to-work-on-practice-projects.md) + - [Work on Mobile app](how-to-setup-freecodecamp-mobile-app-locally.md) + - [Work on tutorials with CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) + - [Work on Localized Web App](how-to-work-on-localized-client-webapp.md) + - [Work on Cypress tests](how-to-add-cypress-tests.md) + - [Work on Video Challenges](how-to-help-with-video-challenges.md) + - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Guide aggiuntive** - [Capire la struttura dei file del curriculum](curriculum-file-structure.md) - [Fare il debug delle email in uscita localmente](how-to-catch-outgoing-emails-locally.md) - [Settare freeCodeCamp su Windows (WSL)](how-to-setup-wsl.md) - - [Workflow con il Token Utente](user-token-workflow.md) - - [Risolvere i Problemi di Sviluppo](troubleshooting-development-issues.md) - - [Manuale Analytics per gli autori](authors-analytics-manual.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) + - [User Token Workflow](user-token-workflow.md) + - [Troubleshooting Development Issues](troubleshooting-development-issues.md) + - [Authors Analytics Manual](authors-analytics-manual.md) --- - **Manuali di volo** (per membri dello staff & moderatori) - [Manuale del moderatore](moderator-handbook.md) - - [Manuale del Leader di lingua](language-lead-handbook.md) - - [Manuale di DevOps](devops.md) - - [Estensione di VSCode per i corsi](courses-vscode-extension.md) - - [Attivare una nuova lingua](how-to-enable-new-languages.md) + - [Reply Templates](reply-templates.md) + - [Language Lead Handbook](language-lead-handbook.md) + - [DevOps Handbook](devops.md) + - [Courses VSCode Extension](courses-vscode-extension.md) + - [Enable New Language](how-to-enable-new-languages.md) --- diff --git a/docs/i18n/italian/devops.md b/docs/i18n/italian/devops.md index 41800bc5bd7..fe91346dff4 100644 --- a/docs/i18n/italian/devops.md +++ b/docs/i18n/italian/devops.md @@ -203,19 +203,19 @@ Il team di sviluppo fa un merge dei cambiamenti dal ramo `prod-staging` a `prod- Ci sono alcune limitazioni e compromessi noti quando si utilizza la versione beta della piattaforma. -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Gli utenti nella versione beta avranno un account separato dalla produzione.** La versione beta utilizza un database fisicamente separato dalla produzione. Questo ci dà la possibilità di prevenire qualsiasi perdita accidentale di dati o modifiche. The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** Il deploy dovrebbe essere frequente e in iterazioni rapide, talvolta più volte al giorno. As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### Non inviare utenti regolari a questo sito come misura per confermare una correzione +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** Il sito beta ha il solo scopo di supportare lo sviluppo locale e il testing, nient'altro. Non è una promessa di ciò che sta arrivando, ma un assaggio di ciò a cui si sta lavorando. -- #### La pagina di iscrizione può essere diversa da quella di produzione +- **Sign in page may look different than production** Usiamo un test tenant per freeCodeCamp.dev su Auth0, e quindi non abbiamo l'abilità di impostare un dominio personalizzato. Questo fa sì che tutte le callback di reindirizzamento e la pagina di login appaiano su un dominio predefinito come: `https://freecodecamp-dev.auth0.com/`. Questo non ha effetto sulle funzionalità ed è quanto più vicino possiamo arrivare alla produzione. diff --git a/docs/i18n/italian/how-to-enable-new-languages.md b/docs/i18n/italian/how-to-enable-new-languages.md index 9afe5526c40..b45e5b61e11 100644 --- a/docs/i18n/italian/how-to-enable-new-languages.md +++ b/docs/i18n/italian/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Attivare video localizzati +### Enabling Localized Videos Per le sfide video, devi cambiare alcune cose. First, add the new locale to the GraphQL query in the `client/src/templates/Challenges/video/Show.tsx` file. Per esempio, in questo modo aggiungeresti Dothraki alla query: @@ -270,7 +270,7 @@ videoLocaleIds: Joi.when('challengeType', { }), ``` -## Interfaccia utente client +## Client UI Dovrai fare un ulteriore passo per gestire le traduzioni dell'interfaccia utente client. @@ -283,7 +283,7 @@ Dovrai copiare i seguenti file da `/client/i18n/locales/english` a `/client/i18n - `motivation.json` - `trending.json` -## Testare traduzioni in locale +## Testing Translations Locally Se desideri testare le traduzioni localmente, prima di aggiungerle al nostro repository principale - salta i cambiamenti delle procedure di Crowdin. Segui i passaggi per abilitare una lingua, quindi scarica le traduzioni da Crowdin e caricale nel tuo codice locale. @@ -303,11 +303,11 @@ Una volta che questi saranno in posizione, dovresti essere in grado di eseguire Per distribuire News per una nuova lingua, dovrai creare due PR. Una Pr sarà al [repo CDN](https://github.com/freeCodeCamp/cdn), e l'altra sarà al [repo News](https://github.com/freeCodeCamp/news). -## Preparare il Repo CDN per la nuova lingua +## Prep the CDN Repo for the New Language News ottiene i link di tendenza e i titoli degli articoli dal nostro CDN durante il build e li aggiunge al piè di pagina. News recupera anche i file Day.js dal CDN durante il build per localizzare date e orari per ogni lingua. -### Aggiungere un file YAML per gli articoli di tendenza +### Add a YAML File for Trending Articles Clona il [repo CDN](https://github.com/freeCodeCamp/cdn) e crea un nuovo branch. @@ -329,7 +329,7 @@ article3link: ... ... ``` -### Aggiungere un file Day.js locale per la nuova lingua +### Add a Day.js Locale File for the New Language Per impostazione predefinita, Day.js include solo l'inglese come locale. Per abilitarlo a lavorare con altre lingue, è necessario aggiungere un nuovo file locale Day.js al CDN. @@ -367,13 +367,13 @@ Copia il codice locale Day.js dalla nuova scheda nel nuovo file che hai creato. Quindi apri una PR al repo CDN per aggiungere i file YAML e Day.js per la revisione. -## Preparare il Repo News per la nuova lingua +## Prep the News Repo for the New Language Il [repo News](https://github.com/freeCodeCamp/news) prende i dati da un'istanza di Ghost, i file che hai aggiunto al CDN, fa il build di News e il deployment. > [!WARN] Pull requests to the News repo _must_ come from the same repo. Non dovresti lavorare da un fork per questo passaggio. -### Modificare il file di configurazione principale +### Modify the Main Config File Clona il repo News e crea un nuovo branch. @@ -407,7 +407,7 @@ const algoliaIndices = { }; ``` -### Aggiungere il file JSON i18next per la nuova lingua +### Add the i18next JSON Files for the New Language Successivamente, vai nella cartella `config/i18n/locales`, crea una nuova cartella e dalle il nome della nuova lingua che stai aggiungendo. Ad esempio, se stai lanciando le News in Dothraki, crea una nuova cartella chiamata `dothraki`. diff --git a/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md index 452d1c8a6d1..d7e5e0b844a 100644 --- a/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Segui questa guida per impostare l'app mobile di freeCodeCamp localmente sul tuo Some of the contribution workflows – like fixing bugs in the codebase – need you to run the freeCodeCamp app locally. -### How to Prepare your Local Machine +## How to Prepare your Local Machine Inizia installando i prerequisiti software per il tuo sistema operativo. -#### Prerequisites +### Prerequisites | Prerequisito | Versione | Note | | --------------------------------------------- | -------- | -------------------------------------------- | @@ -26,7 +26,7 @@ dart --version Una volta che avrai installato i prerequisiti, dovrai preparare il tuo ambiente di sviluppo. Questo è comune a molti flussi di lavoro di sviluppo, e si dovrà fare solo una volta. -##### Segui questi passaggi per preparare il tuo ambiente di sviluppo: +#### Follow these steps to get your development environment ready: 1. Installa [Git](https://git-scm.com/) o il tuo client Git preferito, se non lo hai già. Aggiorna alla versione più recente; la versione fornita con il tuo sistema operativo potrebbe essere obsoleta. @@ -361,7 +361,7 @@ Segui questi passaggi: git push origin branch/name-here ``` -## Proporre una Pull Request (PR) +## Proposing a Pull Request (PR) Dopo aver fatto il commit delle tue modifiche, controlla qui per [come aprire una Pull Request](how-to-open-a-pull-request.md). @@ -374,7 +374,7 @@ A quick reference to the commands that you will need when working locally. | `npm ci` | Installs / re-install all dependencies and bootstraps the different services. | | `npm run seed` | Parses all the challenge markdown files and inserts them into MongoDB. | --> -## Risoluzione Dei Problemi +## Troubleshooting ### Problemi con l'installazione dei prerequisiti raccomandati @@ -398,7 +398,7 @@ Se incontri degli errori durante l'installazione delle dipendenze, assicurati di Be patient as the first-time setup can take a while depending on your network bandwidth. -## Ottenere Aiuto +## Getting Help Se sei bloccato e hai bisogno di aiuto, poni liberamente le tue domande nella [categoria 'Contributors' sul nostro forum](https://forum.freecodecamp.org/c/contributors) o [nella chat room per i contributori](https://discord.gg/PRyKn3Vbay). diff --git a/docs/i18n/italian/how-to-work-on-coding-challenges.md b/docs/i18n/italian/how-to-work-on-coding-challenges.md index f8ec9f67619..c79e6350656 100644 --- a/docs/i18n/italian/how-to-work-on-coding-challenges.md +++ b/docs/i18n/italian/how-to-work-on-coding-challenges.md @@ -483,13 +483,15 @@ Puoi anche testare una sfida singola con i seguenti step: ``` pnpm run test -- -g titolo-sfida-qui ``` -Una volta che avrai verificato che ogni sfida su cui hai lavorato passi i test, [per favore crea una pull request](how-to-open-a-pull-request.md). - > [!TIP] Puoi impostare la variabile d'ambiente `LOCALE` nel file `.env` alla lingua usata nelle sfide che devi testare. > > I valori attualmente accettati sono `english` (inglese) e `chinese` (cinese), con `english` come valore di default. -### Link utili +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links Creare e modificare sfide: diff --git a/docs/i18n/italian/how-to-work-on-localized-client-webapp.md b/docs/i18n/italian/how-to-work-on-localized-client-webapp.md index e41763db8f1..0af34fe3e24 100644 --- a/docs/i18n/italian/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/italian/how-to-work-on-localized-client-webapp.md @@ -266,7 +266,11 @@ Sarebbe utile anche tenere tutte le chiavi nello stesso ordine in tutti i file. > [!NOTE] The underscore (`_`) is a reserved character for keys in the client-side files. Vedi [la documentazione](https://www.i18next.com/translation-function/plurals) per il suo utilizzo. -## Documentazione utile +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Helpful Documentation - [Documentazione react-i18next ](https://react.i18next.com/latest/usetranslation-hook) - [Documentazione i18next](https://www.i18next.com/translation-function/essentials) diff --git a/docs/i18n/italian/how-to-work-on-practice-projects.md b/docs/i18n/italian/how-to-work-on-practice-projects.md index 5bb7f0e989c..4f29309a10b 100644 --- a/docs/i18n/italian/how-to-work-on-practice-projects.md +++ b/docs/i18n/italian/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ Uno script una tantum che aggiorna automaticamente il frontmatter nei file di ma ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/italian/how-to-work-on-the-component-library.md b/docs/i18n/italian/how-to-work-on-the-component-library.md index 7338fd559c4..07a43f5b3ad 100644 --- a/docs/i18n/italian/how-to-work-on-the-component-library.md +++ b/docs/i18n/italian/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Benvenuti nella libreria `ui-components` di freeCodeCamp. I componenti sono principalmente creati da zero con elementi HTML base e [Tailwind CSS](https://tailwindcss.com/). - # Come lavorare sulla libreria dei componenti +Benvenuti nella libreria `ui-components` di freeCodeCamp. I componenti sono principalmente creati da zero con elementi HTML base e [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > freeCodeCamp stava utilizzando componeti Bootstrap nell'UI. Ma, ci stiamo pian piano allontanando da ciò e creando la nostra libreria componenti, il che aiuta a standardizzare i pattern UI/UX e a migliorare l'accessibilità. Teniamo traccia del progetto in [questa issue su GitHub](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,16 +91,20 @@ Per eseguire i test sulla libreria componenti, esegui il seguente comando dalla pnpm run test-ui-components ``` +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Adding Packages to the UI-Component Library -Limitiamo l'aggiunta di nuovi pacchetti ai Componenti UI per facilitare la manutenzione del progetto. Nel raro caso in cui pensi che sia necessaria una dipendenza, per favore, fai prima una verifica con i manutentori e quindi utilizza il seguente comando per aggiungere un pacchetto: +We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: ```bash cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Useful Links - [Testare per accessibilità](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Ordine di priorità delle query di React Testing Library](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/italian/how-to-work-on-the-docs-theme.md b/docs/i18n/italian/how-to-work-on-the-docs-theme.md index d12172c6c2a..2fd7f3ebf75 100644 --- a/docs/i18n/italian/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/italian/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ In genere non è necessario modificare alcuna configurazione o costruire il sito Install freeCodeCamp locally ([see the local setup guide](how-to-setup-freecodecamp-locally)), we bundled the CLI with the development tools so you can run the command below as needed from the root of the repo: -#### Serve and Launch the Documentation Site - ```console pnpm run docs:serve ``` > Il sito di documentazione dovrebbe essere disponibile su + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/italian/moderator-handbook.md b/docs/i18n/italian/moderator-handbook.md index f86913978d3..cbd74eab425 100644 --- a/docs/i18n/italian/moderator-handbook.md +++ b/docs/i18n/italian/moderator-handbook.md @@ -39,7 +39,7 @@ Puoi aiutarci ad organizzare e fare lo smistamento delle issue riportate applica Per favore, fai particolare attenzione alle etichette `"help wanted"` e `"first timers only"`. Queste devono essere aggiunte ai thread che pensi possano essere aperti a potenziali contributori per creare una pull request. -Un'etichetta `"first timer only"` dovrebbe essere applicata per problemi banali (es. un refuso) e dovrebbe includere informazioni addizionali. Puoi usare questo [modello di risposta](moderator-handbook.md#first-timer-only-issues) per lo smistamento. +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### Chiudere issues e pull request stantii, obsoleti e inattivi @@ -49,7 +49,7 @@ Un'etichetta `"first timer only"` dovrebbe essere applicata per problemi banali - Se il contributore chiede ulteriore assistenza o anche del tempo, quanto sopra può essere rilassato e rivisitato dopo che è stata data una risposta. In ogni caso, i moderatori dovrebbero usare il loro buon senso per prendere una decisione sullo status in sospeso della PR. -> [!TIP] Ti consigliamo di usare questa lista di [modelli di risposta](moderator-handbook.md#reply-templates) mentre smisti le issue. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### Moderare le pull request @@ -63,7 +63,7 @@ Le pull request (PR) sono il modo in cui i contributori sottopongono cambiamenti Puoi anche farne la revisione direttamente su GitHub e decidere se fare il merge. Dobbiamo fare un po' attenzione su questo perché milioni di persone incontreranno questo testo lavorando sul curriculum di freeCodeCamp. La pull request rende il testo più chiaro senza allungarlo troppo? Le modifiche sono rilevanti e non troppo pedanti? Ricorda che il nostro obbiettivo è che le sfide siano più chiare e più corte possibile. Non sono il luogo per dettagli incomprensibili. I contributori possono provare ad aggiungere link e risorse alle sfide. - Puoi chiudere le pull request non valide e rispondervi con questi [modelli di risposta](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). Se la modifica va bene, assicurati di lasciare un'approvazione con un commento "LGTM" (Looks Good To Me). Una volta che una pull request riceve almeno due approvazioni (inclusa la tua) dai moderatori o dal dev-team, puoi procedere e farne il merge. @@ -75,7 +75,7 @@ Le pull request (PR) sono il modo in cui i contributori sottopongono cambiamenti Alcuni contributori potrebbero provare ad aggiungere test addizionali per coprire casi limite pedanti. Dobbiamo fare attenzione a non rendere le sfide troppo complicate. Queste sfide e i loro test dovrebbero essere più semplici e intuitivi possibile. Ad eccezione delle sfide sugli algoritmi e della sezione di preparazione al colloquio di lavoro, gli studenti dovrebbero essere in grado di risolvere ogni sfida entro due minuti. - Puoi chiudere le pull request non valide e rispondervi con questi [modelli di risposta](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with an "LGTM" comment. Una volta che una pull request ha ricevuto almeno due approvazioni (inclusa la tua) dai moderatori o dal dev-team, puoi procedere e farne il merge. @@ -142,7 +142,7 @@ Spesso una pull request avrà richiesto uno sforzo minimo. Puoi capirlo immediat Ci sono anche situazioni in cui il contributore sta cercando di aggiungere un collegamento al proprio sito Web, includere una libreria che ha creato o apportare una modifica frivola che non aiuta nessuno tranne se stesso. -Puoi chiudere le pull request non valide e rispondervi con questi [modelli di risposta](moderator-handbook.md#chiudere-le-pull-request-non-valide). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Altre linee guida per i Moderatori su GitHub @@ -344,238 +344,3 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
Thanks for reading this, and thanks for helping the developer community! - -## Reply Templates - -These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. - -> Puoi creare le tue con la feature integrata di GitHub [saved replies](https://github.com/settings/replies/) oppure utilizzare quelle qui sotto. - -### Ringraziamenti - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Ringraziamenti e congratulazioni - -> Per ringraziare e incoraggiare chi contribuisce per la prima volta. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Errore di compilazione - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Sincronizzare il fork - -> Quando la PR non è allineata con il branch `main`. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Merge Conflicts - -> When PR has merge conflicts that need to be resolved.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. - -### Duplicati - -> Quando la pull request è una ripetizione o un duplicato. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Chiudere le pull request non valide - -> Quando una pull request non è valida. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> Quando una PR aggiunge link a risorse esterne. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adding Comment About Newbie Mistakes - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Chiudere le issue non valide - -> Quando una issue è inerente al codice del camper. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> Quando un'issue è il duplicato di un'issue precedente. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> Quando una issue viene risolta durante lo staging. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Issue `first timer only` - -> Quando un'issue è ritenuta idonea per chi contribuisce al codice per la prima volta. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Richieste di assegnazione - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/italian/reply-templates.md b/docs/i18n/italian/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/italian/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/italian/security-hall-of-fame.md b/docs/i18n/italian/security-hall-of-fame.md index f5170472b8d..19dfa2664c5 100644 --- a/docs/i18n/italian/security-hall-of-fame.md +++ b/docs/i18n/italian/security-hall-of-fame.md @@ -8,4 +8,4 @@ Anche se al momento non offriamo ricomplete, siamo grati a queste fantastiche pe - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) lavorando con IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Grazie per i vostri contributi :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/japanese/FAQ.md b/docs/i18n/japanese/FAQ.md index 37181a190ae..aa686594a0d 100644 --- a/docs/i18n/japanese/FAQ.md +++ b/docs/i18n/japanese/FAQ.md @@ -1,64 +1,68 @@ -### GitHub とオープンソースは初めてです。 どこから始めればいいですか？ +# Frequently Asked Questions -[「オープンソースに貢献する方法ガイド」](https://github.com/freeCodeCamp/how-to-contribute-to-open-source) をご覧ください。 これは、初心者にも優しいプロジェクトのための包括的な参照です。 And it includes a lot of open-source contribution tips. +Answers to common questions. -### コードベースに貢献するために知っておくべきことは何ですか？ +## I am new to GitHub and Open Source. Where should I start? -freeCodeCamp は、モダンな JavaScript スタック上で動作します。 コードベースで貢献することにご興味がある場合は、JavaScript および Node.js、MongoDB、OAuth 2.0、React、Gatsby、Webpack のようなテクノロジーに精通している必要があります。 +Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### freeCodeCamp のリソースを翻訳できますか？ +## What do I need to know to contribute to the codebase? -はい。翻訳プラットフォームで有効になっている 30 以上の言語を貢献できます。 +freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -ユーザーが行った翻訳が既に存在する言語もあります。 freeCodeCamp を世界の主要な言語にローカライズしていく予定です。 You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). +## Can I translate freeCodeCamp's resources? + +Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. + +We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -### freeCodeCamp ニュースの記事や、freeCodeCamp YouTube チャンネルの動画に貢献することはできますか？ +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? -はい。ニュースブログや YouTube チャンネルに貢献することができます。 +Yes - you can contribute to our publication blog and YouTube channel. -freeCodeCamp ニュースの記事を書くことにご興味がありましたら、[執筆ガイド](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/) をご覧ください。 より力強い、より効果的な記事を書くために、[スタイルガイド](https://www.freecodecamp.org/news/developer-news-style-guide/) をお読みください。 +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. -YouTube チャンネル用の動画講座を作成するには、[YouTube チャンネルガイド](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/) をお読みください。 +To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -### 新しいバグはどのように報告すればいいですか？ +## How can I report a new bug? If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -新しいバグだという確信がある場合は、GitHub Issue を作成してください。 バグを再現できるように、できるだけ多くの情報を含めるようにしてください。 これをサポートするために、事前に定義された Issue 用テンプレートがあります。 +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -これらの GitHub Issue は、コードベース関連の問題や議論のためのものであり、コードを学習するための助けを得るためのものではありません。 疑わしい場合は GitHub Issue を作成する前に、[フォーラム](https://forum.freecodecamp.org) で支援を求めます。 +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### セキュリティ問題はどのように報告すればいいですか？ +## How can I report a security issue? -セキュリティ問題のために GitHub Issue を作成しないでください。 代わりに、[こちらのセキュリティポリシー](https://contribute.freecodecamp.org/#/security)に従ってください。 +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -### 私は学生です。 単位取得を目的として、機能に関して貢献することはできますか？ +## I am a student. Can I work on a feature for academic credits? -はい。 ただし、大学での要件となるような時間軸や書類に関与することはできませんのでご注意ください。 私たちはボランティア開発者から多くのプルリクエストやコードの貢献を受けており、皆さんの時間と努力を尊重しています。 すべての貢献者に対して敬意を払っているため、学校関連だからと言って PR 特別優先事項を与えることはありません。 +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -これを念頭におき、事前にご自身で計画を立てたうえで、コードの貢献に取り組むようお願いいたします。 +We request you to plan ahead and work on code contributions with this in mind. -### GitHub Issue にタグ付けされた様々なラベルはどのような意味ですか？ +## What do these different labels that are tagged on issues mean? -コードメンテナーは、優先度、重大度、およびその他の要因に基づいて、Issue とプルリクエストを [トリアージ](https://en.wikipedia.org/wiki/Software_bug#Bug_management) します。 [ラベルの意味の用語集](https://github.com/freecodecamp/freecodecamp/labels) をご覧ください。 +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). -### Issue の作業に貢献するには、何から始めたらいいですか？ +## Where do I start if I want to work on an issue? -貢献可能な作業にどのようなものがあるか把握するため、まずは [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) または [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) のラベルが付いた Issue を確認してください。 +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] **`help wanted`** の Issue は誰でも作業が可能であり、作業前に許可を求める必要はありません。 ただし、 **`first timers only`** ラベルが付けられた Issue は、初めて freeCodeCamp コードベースに貢献する人用の特別な Issue です。 -### タイプミスを見つけました。 プルリクエストを行う前に Issue を作成すべきですか？ +## I found a typo. Should I report an issue before I can make a pull request? -タイプミスや文言変更の場合、Issue を作成せずに、直接プルリクエストをオープンして構いません。 些細な変更であっても、プルリクエストの説明には詳しい情報を記載してください。皆様の貢献を理解しレビューする際に役立ちます。 +For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. -コードベースやカリキュラムの大きな側面について議論したい場合は、Issue を作成してください。 +Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### Issue を割り当て (アサイン) してもらうにはどうすればいいですか？ +## How can I get an issue assigned to me? -通常、長期的なコントリビューター以外には Issue を割り当てません。 その代わりに、以下の方針に従い、すべての人対して公平であるようにしています。 +We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: 1. Issue に対処する最初のプルリクエストをマージする可能性が最も高いです。 2. 複数のコントリビューターが同じ Issue に対してプルリクエストを同時にオープンした場合、 最善の対処をするプルリクエストを優先します。 考慮事項: @@ -69,37 +73,37 @@ If you think you've found a bug, first read the ["How to Report a Bug"](https:// - プルリクエストのチェックリストに従って確認しましたか？ - プルリクエストに意味のあるタイトルを付けましたか？ -### freeCodeCamp のモデレーターになりたいです。 何から始めればいいですか？ +## I am interested in being a moderator at freeCodeCamp. Where should I start? -コミュニティモデレーターは、私たちのヒーローです。 Their voluntary contributions make freeCodeCamp a safe and welcoming community. +Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. First and foremost, we would need you to be an active participant in the community, and live by our [code of conduct](https://www.freecodecamp.org/news/code-of-conduct/) (not just enforce it). -いくつかのプラットフォームで推奨されるパスを以下に示します。 +Here are some recommended paths for some of our platforms: - To be a **Discord/Chat** moderator, have an active presence in our chat and have positive engagements with others, while also learning and practicing how to deal with potential conflicts that may arise. - To be a **Forum** moderator, similar to a chat moderator, have an active presence and engage with other forum posters, supporting others in their learning journey, and even giving feedback when asked. Take a look at [The Subforum Leader Handbook](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) for more information. - To be a **GitHub** moderator, help process GitHub issues that are brought up to see if they are valid and (ideally) try to propose solutions for these issues to be picked up by others (or yourself). -つまり、他の人に敬意を払ってください。 We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. -If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. オープンソース作業はボランティアであり、私たちの時間は限られています。 皆様も、おそらく同じだと思います。 So we emphasize being **consistent** rather than engaging in the community 24/7. +If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### このドキュメントに記載されていない問題で困っています。 +## I am stuck on something that is not included in this documentation. -**以下に、お気軽にお問い合わせください。** +**Feel free to ask for help in:** - [コミュニティフォーラム](https://forum.freecodecamp.org/c/contributors) の `Contributors` カテゴリ - [チャットサーバーの ](https://discord.gg/PRyKn3Vbay) `#Contributors` チャンネル -取り組みたいトピックに貢献するお手伝いをさせていただけることを嬉しく思います。 関連する問題のスレッドについて質問をいただいた場合は、喜んで明確にします。 新しい質問を投稿する前に、必ずその質問を検索してください。 +We are excited to help you contribute to any of the topics that you would like to work on. If you ask us questions on the related issue threads, we will be glad to clarify. Be sure to search for your question before posting a new one. -礼儀正しく忍耐強い対応を、お願いいたします。 このコミュニティは主にボランティアによって運営されていることをご理解ください。 +Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### その他の支援 +## Additional Assistance If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**`dev[at]freecodecamp.org` にて、開発者スタッフにメールでお問い合わせいただけます。** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/japanese/_sidebar.md b/docs/i18n/japanese/_sidebar.md index 0eed7a21fae..2b2353a6122 100644 --- a/docs/i18n/japanese/_sidebar.md +++ b/docs/i18n/japanese/_sidebar.md @@ -8,7 +8,6 @@ - **コードのコントリビューション** - [Set up freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Follow best-practices](codebase-best-practices.md) - - [Open a pull request](how-to-open-a-pull-request.md) - [Work on Codebase](how-to-contribute-to-the-codebase.md) - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) - [Work on Component Library](how-to-work-on-the-component-library.md) @@ -19,10 +18,12 @@ - [Work on Cypress tests](how-to-add-cypress-tests.md) - [Work on Video Challenges](how-to-help-with-video-challenges.md) - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **その他のガイド** - [Understand the curriculum file structure](curriculum-file-structure.md) - [Debug outgoing emails locally](how-to-catch-outgoing-emails-locally.md) - [Set up freeCodeCamp on Windows (WSL)](how-to-setup-wsl.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) - [User Token Workflow](user-token-workflow.md) - [Troubleshooting Development Issues](troubleshooting-development-issues.md) - [Authors Analytics Manual](authors-analytics-manual.md) @@ -31,9 +32,10 @@ - **マニュアル** (スタッフ & モデレーター用) - [モデレーターハンドブック](moderator-handbook.md) - - [ランゲージリードハンドブック](language-lead-handbook.md) - - [DevOps ハンドブック](devops.md) - - [VSCode 拡張機能「Courses」](courses-vscode-extension.md) + - [Reply Templates](reply-templates.md) + - [Language Lead Handbook](language-lead-handbook.md) + - [DevOps Handbook](devops.md) + - [Courses VSCode Extension](courses-vscode-extension.md) - [Enable New Language](how-to-enable-new-languages.md) --- diff --git a/docs/i18n/japanese/devops.md b/docs/i18n/japanese/devops.md index b463b729d4f..e91786a8720 100644 --- a/docs/i18n/japanese/devops.md +++ b/docs/i18n/japanese/devops.md @@ -203,19 +203,19 @@ Currently, a public beta testing version is available at: プラットフォームのベータ版を使用する場合、いくつかの既知の制限とトレードオフがあります。 -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **ベータ版のユーザーは本番とは異なるアカウントを持つことになります。** ベータ版は本番と物理的に分離されたデータベースを使用します。 これにより、偶発的なデータ損失や変更を防ぐことができます。 The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** デプロイは頻繁に行われ、時には非常に速いペースで 1 日に複数回行われることになります。 As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### 修正を確認する手段として、このサイトに一般ユーザーを送らないでください。 +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** ベータサイトは、ローカルの開発とテストを強化するためのものでしたし、今もそうです。 それはこれから起こることを約束するものではありませんが、取り組まれていることを垣間見るものです。 -- #### サインインページが本番環境とは異なる場合があります。 +- **Sign in page may look different than production** Auth0 上で freeCodeCamp.dev にはテストテナントを使用しているため、カスタムドメインを設定することはできません。 そのため、すべてのリダイレクトコールバックとログインページが `https://freecodecamp-dev.auth0.com/` のようなデフォルトドメインに表示されます。 これが機能に影響を与えることはありませんし、本番環境に近いものです。 diff --git a/docs/i18n/japanese/how-to-enable-new-languages.md b/docs/i18n/japanese/how-to-enable-new-languages.md index a3ecabcd186..1f03dc1259b 100644 --- a/docs/i18n/japanese/how-to-enable-new-languages.md +++ b/docs/i18n/japanese/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Enabling Localized Videos +### Enabling Localized Videos For the video challenges, you need to change a few things. First, add the new locale to the GraphQL query in the `client/src/templates/Challenges/video/Show.tsx` file. For example, adding Dothraki to the query: diff --git a/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md index 9deae099e21..2ee38da1b31 100644 --- a/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Follow this guide for setting up the freeCodeCamp mobile app locally on your sys Some of the contribution workflows – like fixing bugs in the codebase – need you to run the freeCodeCamp app locally. -### How to Prepare your Local Machine +## How to Prepare your Local Machine Start by installing the prerequisite software for your operating system. -#### Prerequisites +### Prerequisites | Prerequisite | Version | Notes | | --------------------------------- | ------- | ---------------------------------------- | @@ -26,7 +26,7 @@ dart --version Once you have the prerequisites installed, you need to prepare your development environment. This is common for many development workflows, and you will only need to do this once. -##### Follow these steps to get your development environment ready: +#### Follow these steps to get your development environment ready: 1. Install [Git](https://git-scm.com/) or your favorite Git client, if you haven't already. Update to the latest version; the version that came bundled with your OS may be outdated. diff --git a/docs/i18n/japanese/how-to-work-on-coding-challenges.md b/docs/i18n/japanese/how-to-work-on-coding-challenges.md index 0f9f1eb2f8c..9dc0b50a937 100644 --- a/docs/i18n/japanese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/japanese/how-to-work-on-coding-challenges.md @@ -483,13 +483,15 @@ FCC_SUPERBLOCK='responsive-web-design' pnpm run test:curriculum ``` pnpm run test -- -g challenge-title-goes-here ``` -各チャレンジがテストに合格したことを確認したら、[プルリクエストを作成](how-to-open-a-pull-request.md) してください。 - > [!TIP] `.env` にある環境変数 `LOCALE` で、テストするチャレンジの言語を設定できます。 > > 現在受け入れられている値は、`english` と `chinese`で、デフォルトは `english` です。 -### 役立つリンク +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links チャレンジの作成および編集 diff --git a/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md b/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md index 0b32bfb18bb..61a124ede90 100644 --- a/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md @@ -266,7 +266,11 @@ const email = 'team@freecodecamp.org'; > [!NOTE] The underscore (`_`) is a reserved character for keys in the client-side files. 使用方法については、 [ドキュメント](https://www.i18next.com/translation-function/plurals) を参照してください。 -## 参考ドキュメント +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Helpful Documentation - [react-i18next docs](https://react.i18next.com/latest/usetranslation-hook) - [i18next docs](https://www.i18next.com/translation-function/essentials) diff --git a/docs/i18n/japanese/how-to-work-on-practice-projects.md b/docs/i18n/japanese/how-to-work-on-practice-projects.md index 563d43c65ca..e585a6b8424 100644 --- a/docs/i18n/japanese/how-to-work-on-practice-projects.md +++ b/docs/i18n/japanese/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ A one-off script that automatically updates the frontmatter in a project's markd ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/japanese/how-to-work-on-the-component-library.md b/docs/i18n/japanese/how-to-work-on-the-component-library.md index 58f2e03ea47..428e2c327da 100644 --- a/docs/i18n/japanese/how-to-work-on-the-component-library.md +++ b/docs/i18n/japanese/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). - # How to Work on the Component Library +Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > freeCodeCamp has been using Bootstrap components in the UI. However, we are moving away from it and building our own component library, which helps standardize our UX/UI patterns and improve accessibility. The project is tracked in [this GitHub issue](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,6 +91,10 @@ To run tests against the component library, run the following command from the r pnpm run test-ui-components ``` +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + ## Adding Packages to the UI-Component Library We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: @@ -100,7 +104,7 @@ cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Useful Links - [Testing for Accessibility](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Order of priority of React Testing Library's queries](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/japanese/how-to-work-on-the-docs-theme.md b/docs/i18n/japanese/how-to-work-on-the-docs-theme.md index 1f12deabfac..9439c803b30 100644 --- a/docs/i18n/japanese/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/japanese/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Typically you would not need to change any configuration or build the site local Install freeCodeCamp locally ([see the local setup guide](how-to-setup-freecodecamp-locally)), we bundled the CLI with the development tools so you can run the command below as needed from the root of the repo: -#### Serve and Launch the Documentation Site - ```console pnpm run docs:serve ``` > The documentation site should be available at + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/japanese/moderator-handbook.md b/docs/i18n/japanese/moderator-handbook.md index 39dab3802b4..77502272aaf 100644 --- a/docs/i18n/japanese/moderator-handbook.md +++ b/docs/i18n/japanese/moderator-handbook.md @@ -39,7 +39,7 @@ We use our main [`freeCodeCamp/freeCodeCamp`](https://github.com/freeCodeCamp/fr `"help wanted"` と `"first timers only"` のラベルに特に注意してください。 これらは、プルリクエストを行う潜在的なコントリビューターが入る可能性があるスレッドに追加されます。 -A `"first timers only"` label should be applied to a trivial issue (ie a typo fix) and should include additional information. この [返信テンプレート](moderator-handbook.md#初回者用の-issue) をトリアージに使用できます。 +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### 古く、期限切れで、不活発な Issue とプルリクエストをクローズする @@ -49,7 +49,7 @@ A `"first timers only"` label should be applied to a trivial issue (ie a typo fi - コントリビューターから支援もしくは時間の追加要求があった場合、それに対する回答を返し、該当する Issue または PR を後日改めて確認することができます。 いずれの場合でも、モデレーターは、未解決の PR を解決するために最善の判断を下す必要があります。 -> [!TIP] Issue をトリアージする際には、この標準の [返信テンプレート](moderator-handbook.md#返信テンプレート) リストを使用することをお勧めします。 +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### プルリクエストをモデレートする @@ -63,7 +63,7 @@ A `"first timers only"` label should be applied to a trivial issue (ie a typo fi GitHub で確認し、マージするかどうかを決定することもできます。 しかし、これについては少し注意する必要があります。 なぜなら、freeCodeCamp カリキュラムを通して何百万人もの方がこのテキストを見るからです。 テキストは、プルリクエストにより、冗長になることなく明確になっていますか？ 編集内容は、過度に知識をひけらかすものではなく、関連性の高いものになっていますか？ 可能な限り明確かつ短文のチャレンジにすることが目標であることを忘れないでください。 曖昧であってはなりません。 コントリビューターが、チャレンジにリソースへのリンクを追加しようとする場合もあります。 - 無効なプルリクエストをクローズして、この [返信テンプレート](moderator-handbook.md#無効なプルリクエストをクローズする-1) で返信します。 + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with a "LGTM" (Looks Good To Me) comment. プルリクエストがモデレーターまたは開発チームから少なくとも 2 つの承認 (あなたを含む) を得たら、マージすることができます。 @@ -75,7 +75,7 @@ A `"first timers only"` label should be applied to a trivial issue (ie a typo fi コントリビューターの中には、衒学的で厄介なケースも網羅するために、追加テストを含めようとする人もいるかもしれません。 チャレンジがあまり複雑にならないように注意しなければなりません。 チャレンジとそのテストは可能な限りシンプルで直感的なものにします。 アルゴリズムチャレンジとインタビュー準備セクションは別として、学習者は約 2 分以内に各チャレンジを解決する必要があります。 - 無効なプルリクエストをクローズして、この [返信テンプレート](moderator-handbook.md#無効なプルリクエストをクローズする-1) で返信します。 + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). If the changes look good, please ensure to leave an approval with an "LGTM" comment. プルリクエストがモデレーターまたは開発チームから少なくとも 2 つの承認 (あなたを含む) を得たら、マージすることができます。 @@ -142,7 +142,7 @@ Sometimes there will be a merge conflict. コントリビューターが Web サイトへのリンクを追加しようとしたり、彼らが作成したライブラリを含めようとしたり、彼ら以外の誰にも役に立たない自由な編集をしようとする状況もあります。 -You can close these invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Other Guidelines for Moderators on GitHub @@ -344,238 +344,3 @@ This XKCD comic summarizes perfectly most communities' thoughts on free speech.
Thanks for reading this, and thanks for helping the developer community! - -## Reply Templates - -These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. - -> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. - -### Thank You - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Thank you and congrats - -> For thanking and encouraging first-time contributors. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Build Error - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Syncing Fork - -> When PR is not up to date with the `main` branch. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Merge Conflicts - -> When PR has merge conflicts that need to be resolved.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. - -### Duplicate - -> When PR is repetitive or a duplicate. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Closing Invalid Pull Requests - -> When PR is invalid. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> When PR adds links to external resources. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adding Comment About Newbie Mistakes - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Closing Invalid Issues - -> When an issue relates to the camper's code. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> When an issue is duplicate of an earlier issue. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> When an issue is fixed in staging. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### `first timer only` Issues - -> When an issue is deemed to be eligible for first-time code contributors. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Requests for Assignment - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/japanese/reply-templates.md b/docs/i18n/japanese/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/japanese/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/japanese/security-hall-of-fame.md b/docs/i18n/japanese/security-hall-of-fame.md index e1ddbc8bccc..b50ce37d17b 100644 --- a/docs/i18n/japanese/security-hall-of-fame.md +++ b/docs/i18n/japanese/security-hall-of-fame.md @@ -8,4 +8,4 @@ - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) working with IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Thank you for your contributions :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/portuguese/FAQ.md b/docs/i18n/portuguese/FAQ.md index 0cc045a9c59..241ad55267e 100644 --- a/docs/i18n/portuguese/FAQ.md +++ b/docs/i18n/portuguese/FAQ.md @@ -1,64 +1,68 @@ -### Eu sou novo no GitHub e em código aberto. Por onde devo começar? +# Frequently Asked Questions -Leia nosso ["Guia de como contribuir com código aberto"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). É uma referência ampla para quem contribui com projetos pela primeira vez. E inclui muitas dicas de como contribuir para código aberto. +Answers to common questions. -### O que eu preciso saber para contribuir com a base de código? +## I am new to GitHub and Open Source. Where should I start? -O freeCodeCamp é executado em uma stack de JavaScript moderna. Se estiver interessado em contribuir com a nossa base de código, você precisará ter alguma familiaridade com JavaScript e com algumas das tecnologias que usamos como o Node.js, MongoDB, OAuth 2.0, React, Gatsby e Webpack. +Read our ["How to Contribute to Open Source Guide"](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). It's a comprehensive reference for first-timer-friendly projects. And it includes a lot of open-source contribution tips. -### Posso traduzir os recursos do freeCodeCamp? +## What do I need to know to contribute to the codebase? -Sim. Você pode contribuir com qualquer um dos mais de 30 idiomas disponíveis em nossa plataforma de tradução. +freeCodeCamp runs on a modern JavaScript stack. If you're interested in contributing to our codebase, you will need some familiarity with JavaScript and some of the technologies we use like Node.js, MongoDB, OAuth 2.0, React, Gatsby, and Webpack. -Temos traduções enviadas por usuários ao vivo em alguns idiomas. Pretendemos traduzir o freeCodeCamp para vários idiomas. Você pode ler mais sobre isso em nosso [anúncio aqui](https://www.freecodecamp.org/portuguese/news/como-ajudar-a-traduzir-o-freecodecamp-para-seu-idioma/). +## Can I translate freeCodeCamp's resources? -Se você está interessado em contribuir com as traduções, certifique-se de [ler este guia](how-to-translate-files.md) primeiro. +Yes - You can contribute to any of the 30+ languages we have enabled on our translation platform. -### Posso contribuir com artigos para o editorial do freeCodeCamp ou com vídeos para o canal do YouTube do CodeCamp? +We have user-contributed translations live in some languages. We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/help-translate-freecodecamp-language/). -Sim - você pode contribuir com o nosso blog de publicação e com o canal do YouTube. +If you are interested in contributing to translations please make sure you [read this guide](how-to-translate-files.md) first. -Se estiver interessado em escrever artigos para o editorial do freeCodeCamp, visite este [guia de publicação](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). Além disso, leia nosso [guia de estilo](https://www.freecodecamp.org/news/developer-news-style-guide/) pois ele ajudará você a escrever artigos mais sólidos e eficazes. +## Can I contribute articles to freeCodeCamp News or videos to freeCodeCamp's YouTube channel? -Para nos ajudar a fazer vídeos educacionais para nosso canal do YouTube, você pode seguir o [guia do canal do YouTube aqui](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). +Yes - you can contribute to our publication blog and YouTube channel. -### Como posso relatar um novo erro? +If you're interested in writing articles for freeCodeCamp News, please visit this [publication guide](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). In addition, please read our [style guide](https://www.freecodecamp.org/news/developer-news-style-guide/) as this will help you write stronger and more effective articles. -Se você acha que encontrou um erro, primeiro leia o artigo ["Como relatar um erro"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) e siga suas instruções. +To help us make educational videos for our YouTube channel, you can follow the [YouTube channel guide here](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -Se você está confiante de que é um novo erro, vá em frente e crie uma nova issue no GitHub. Certifique-se de incluir o máximo de informações possível para que possamos reproduzir o erro. Temos um modelo predefinido de issue para ajudar você. +## How can I report a new bug? -Observe que essas issues do GitHub são para discussões e questões relacionadas ao código – não para obter ajuda sobre como aprender a programar. Sempre que houver dúvidas, você deve [procurar por assistência no fórum](https://forum.freecodecamp.org) antes de criar uma issue no GitHub. +If you think you've found a bug, first read the ["How to Report a Bug"](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) article and follow its instructions. -### Como posso relatar um problema de segurança? +If you're confident it's a new bug, go ahead and create a new GitHub issue. Be sure to include as much information as possible so that we can reproduce the bug. We have a pre-defined issue template to help you through this. -Não crie issues no GitHub para problemas de segurança. Em vez disso, [siga nossa política de segurança](https://contribute.freecodecamp.org/#/security). +Please note that these GitHub issues are for codebase-related issues and discussions – not for getting help with learning to code. Whenever in doubt, you should [seek assistance on the forum](https://forum.freecodecamp.org) before creating a GitHub issue. -### Eu sou estudante. Posso trabalhar em um recurso para créditos acadêmicos? +## How can I report a security issue? -Sim. Note, porém, que não podemos nos comprometer com nenhum cronograma ou documentação que possa ser um requisito da sua faculdade ou universidade. Recebemos muitos pull-requests e contribuições em código de desenvolvedores voluntários e respeitamos o tempo e esforço deles. Em respeito a todos os outros contribuidores, não daremos nenhuma prioridade especial a nenhum PR só por ser relacionado à escola. +Please don't create GitHub issues for security issues. Instead, please [follow our security policy](https://contribute.freecodecamp.org/#/security). -Pedimos que você planeje com antecedência e que trabalhe em suas contribuições de código tendo isso em mente. +## I am a student. Can I work on a feature for academic credits? -### O que significam estas etiquetas diferentes marcadas nas issues? +Yes. Please note we are unable to commit to any timelines or paperwork that may be a requirement by your college or university. We receive many pull-requests and code contributions from volunteer developers, and we respect their time and efforts. Out of respect for all of our other contributors, we will not give any PR special priority just because it happens to be school-related. -Os responsáveis pelo código fazem a [triagem](https://en.wikipedia.org/wiki/Software_bug#Bug_management) das issues e pull requests tendo como base a prioridade, importância e outros fatores. Você pode [encontrar um glossário completo dos significados aqui](https://github.com/freecodecamp/freecodecamp/labels). +We request you to plan ahead and work on code contributions with this in mind. -### Por onde começar se quero ajudar em uma issue? +## What do these different labels that are tagged on issues mean? -Você deve consultar issues [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) ou [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) para saber o que está disponível para ajuda. +The code maintainers [triage](https://en.wikipedia.org/wiki/Software_bug#Bug_management) issues and pull requests based on their priority, severity, and other factors. You can [find a complete glossary of their meanings here](https://github.com/freecodecamp/freecodecamp/labels). + +## Where do I start if I want to work on an issue? + +You should go through [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) or [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22) issues for a quick overview of what is available for you to work on. > [!TIP] Você não precisa pedir permissão para ajudar com issues marcadas como **`help wanted`**. No entanto, issues com a etiqueta **`first timers only`** são issues especiais projetadas para pessoas que não contribuíram antes para a base de código freeCodeCamp. -### Encontrei um erro de digitação. Devo relatar uma issue antes de poder fazer um pull request? +## I found a typo. Should I report an issue before I can make a pull request? -Para erros de digitação e outras mudanças em palavras, você pode diretamente abrir pull requests sem criar uma issue antes. Certifique-se de mencionar detalhes na descrição do pull request para nos ajudar a entender e revisar sua contribuição – mesmo se for uma mudança pequena. +For typos and other wording changes, you can directly open pull requests without creating an issue first. Please be sure to mention details in the pull request description to help us understand and review your contribution – even if it's just a minor change. -Crie uma issue se quiser discutir grandes aspectos da base do código ou currículo. +Please do create an issue if you want to discuss bigger aspects of the codebase or curriculum. -### Como posso receber uma issue atribuída a mim? +## How can I get an issue assigned to me? -Tipicamente, não atribuímos issues para ninguém além de contribuidores de longo prazo. Ao invés disso, seguimos a política abaixo para sermos justos com todos: +We typically do not assign issues to anyone other than long-time contributors. Instead, we follow the below policy to be fair to everyone: 1. É muito provável que façamos o merge do primeiro pull request que resolve a issue. 2. No caso de vários colaboradores abrindo um pull request para a mesma issue, ao mesmo tempo, daremos prioridade ao pull request que melhor resolve a issue. Algumas coisas que consideramos: @@ -69,37 +73,37 @@ Tipicamente, não atribuímos issues para ninguém além de contribuidores de lo - Você seguiu a checklist do pull request? - Você deu um título significativo ao seu pull request? -### Tenho interesse em ser um moderador no freeCodeCamp. Por onde devo começar? +## I am interested in being a moderator at freeCodeCamp. Where should I start? -Os moderadores da nossa comunidade são nossos heróis. Suas contribuições voluntárias fazem do freeCodeCamp uma comunidade segura e receptiva. +Our community moderators are our heroes. Their voluntary contributions make freeCodeCamp a safe and welcoming community. -Primeiro e mais importante, precisamos que você seja um participante ativo da comunidade e que siga à risca o nosso [código de conduta](https://www.freecodecamp.org/news/code-of-conduct/) (não se limite apenas a aplicá-lo). +First and foremost, we would need you to be an active participant in the community, and live by our [code of conduct](https://www.freecodecamp.org/news/code-of-conduct/) (not just enforce it). -Aqui estão alguns caminhos recomendados para algumas de nossas plataformas: +Here are some recommended paths for some of our platforms: - Para ser um moderador do **Discord/Chat**, tenha uma presença ativa em nosso chat e compromissos positivos com os outros, ao mesmo tempo em que aprende e pratica como lidar com conflitos em potencial que possam surgir. - Para ser um moderador do **fórum**, similar a um moderador de chat, tenha uma presença ativa e interaja com as outras pessoas que publicam no fórum, apoie-os em sua jornada de aprendizado e dê feedback quando perguntarem. Dê uma olhada no [Manual do líder do subfórum](https://forum.freecodecamp.org/t/the-subforum-leader-handbook/326326) para obter mais informações. - Para ser um moderador do **GitHub**, ajude a processar as issues levantadas no GitHub para ver se elas são válidas e (idealmente) tente propor soluções para essas issues a serem resolvidas por outras pessoas (ou por você mesmo). -No conjunto, seja respeitoso com os outros. Somos seres humanos de todo o mundo. Tendo isso em mente, considere também usar uma linguagem de incentivo ou de apoio e esteja atento à comunicação intercultural. +Altogether, be respectful to others. We are humans from all around the world. With that in mind, please also consider using encouraging or supportive language and be mindful of cross-cultural communication. -Se você praticar o que foi dito acima **consistentemente por algum tempo** e se nossos companheiros moderadores recomendarem você, um membro da equipe entrará em contato e fará sua inclusão na equipe de moderadores. O trabalho em código aberto é trabalho voluntário e nosso tempo é limitado. Reconhecemos que isso é provavelmente também é verdade no seu caso. Por isso, enfatizamos a importância de ser **consistente** em vez de se envolver na comunidade em tempo integral. +If you practice the above **consistently for a while** and our fellow moderator members recommend you, a staff member will reach out and onboard you to the moderators' team. Open source work is voluntary work and our time is limited. We acknowledge that this is probably true in your case as well. So we emphasize being **consistent** rather than engaging in the community 24/7. -Dê uma olhada no nosso [Manual do Moderador](moderator-handbook.md) para obter uma lista mais completa de outras responsabilidades e expectativas que temos nossos moderadores. +Take a look at our [Moderator Handbook](moderator-handbook.md) for a more exhaustive list of other responsibilities and expectations we have of our moderators. -### Estou com dificuldade em algo que não está incluído na documentação. +## I am stuck on something that is not included in this documentation. -**Fique à vontade para pedir ajuda em:** +**Feel free to ask for help in:** - A categoria `Contributors` do [fórum da nossa comunidade](https://forum.freecodecamp.org/c/contributors). - O canal `#Contributors` em nosso [servidor](https://discord.gg/PRyKn3Vbay). -Estamos animados em ajudar você a contribuir com qualquer tópico que desejar. Se você nos perguntar algo relacionado às issues, vamos ficar felizes em esclarecer. Certifique-se de pesquisar sua pergunta antes de postar uma nova. +We are excited to help you contribute to any of the topics that you would like to work on. If you ask us questions on the related issue threads, we will be glad to clarify. Be sure to search for your question before posting a new one. -Agradecemos antecipadamente por ser educado(a) e paciente. Lembre-se – esta comunidade é feita principalmente de voluntários. +Thanks in advance for being polite and patient. Remember – this community is run mainly by volunteers. -### Assistência adicional +## Additional Assistance -Se você tiver dúvidas sobre a stack, a arquitetura do código, as traduções ou qualquer outra coisa, pode entrar em contato com nossa equipe [no fórum](https://forum.freecodecamp.org/g/team). +If you have queries about the stack, architecture of the codebase, translations, or anything else, feel free to reach out to our staff team [on the forum](https://forum.freecodecamp.org/g/team). -**Você pode enviar um e-mail para nossa equipe de desenvolvimento: `dev[at]freecodecamp.org`** +**You can email our developer staff at: `dev[at]freecodecamp.org`** diff --git a/docs/i18n/portuguese/_sidebar.md b/docs/i18n/portuguese/_sidebar.md index a145cec7f05..41fd3c44599 100644 --- a/docs/i18n/portuguese/_sidebar.md +++ b/docs/i18n/portuguese/_sidebar.md @@ -8,33 +8,35 @@ - **Contribuição de código** - [Configurar o freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Seguir as melhores práticas](codebase-best-practices.md) - - [Abrir um pull request](how-to-open-a-pull-request.md) - - [Trabalhar na base de código](how-to-contribute-to-the-codebase.md) - - [Trabalhar em desafios de programação](how-to-work-on-coding-challenges.md) - - [Trabalhar na biblioteca de componentes](how-to-work-on-the-component-library.md) - - [Trabalhar em projetos práticos](how-to-work-on-practice-projects.md) - - [Trabalhar na aplicação para dispositivos móveis](how-to-setup-freecodecamp-mobile-app-locally.md) - - [Trabalhar nos tutoriais com o CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) - - [Trabalhar na aplicação para a web localizada](how-to-work-on-localized-client-webapp.md) - - [Trabalhar em testes do Cypress](how-to-add-cypress-tests.md) - - [Trabalhar nos desafios em vídeo](how-to-help-with-video-challenges.md) - - [Trabalhar com a documentação](how-to-work-on-the-docs-theme.md) + - [Work on Codebase](how-to-contribute-to-the-codebase.md) + - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) + - [Work on Component Library](how-to-work-on-the-component-library.md) + - [Work on Practice Projects](how-to-work-on-practice-projects.md) + - [Work on Mobile app](how-to-setup-freecodecamp-mobile-app-locally.md) + - [Work on tutorials with CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) + - [Work on Localized Web App](how-to-work-on-localized-client-webapp.md) + - [Work on Cypress tests](how-to-add-cypress-tests.md) + - [Work on Video Challenges](how-to-help-with-video-challenges.md) + - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Guias adicionais** - [Compreender a estrutura do arquivo do currículo](curriculum-file-structure.md) - [Depurar e-mails enviados localmente](how-to-catch-outgoing-emails-locally.md) - [Configurar freeCodeCamp no Windows (WSL)](how-to-setup-wsl.md) - - [Fluxo de trabalho do token de usuário](user-token-workflow.md) - - [Solucionar problemas de desenvolvimento](troubleshooting-development-issues.md) - - [Manual de análise dos autores](authors-analytics-manual.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) + - [User Token Workflow](user-token-workflow.md) + - [Troubleshooting Development Issues](troubleshooting-development-issues.md) + - [Authors Analytics Manual](authors-analytics-manual.md) --- - **Manuais de Voo** (para Equipe & Moderadores) - [Manual do Moderador](moderator-handbook.md) - - [Manual do líder do idioma](language-lead-handbook.md) - - [Manual do DevOps](devops.md) - - [Extensão do VSCode Courses](courses-vscode-extension.md) - - [Habilitar um novo um idioma ](how-to-enable-new-languages.md) + - [Reply Templates](reply-templates.md) + - [Language Lead Handbook](language-lead-handbook.md) + - [DevOps Handbook](devops.md) + - [Courses VSCode Extension](courses-vscode-extension.md) + - [Enable New Language](how-to-enable-new-languages.md) --- diff --git a/docs/i18n/portuguese/devops.md b/docs/i18n/portuguese/devops.md index 76a8801e164..898c87fb146 100644 --- a/docs/i18n/portuguese/devops.md +++ b/docs/i18n/portuguese/devops.md @@ -203,19 +203,19 @@ Você pode identificar a versão exata implantada visitando os registros de comp Existem algumas limitações e desvantagens conhecidas ao usar a versão beta da plataforma. -- #### Todos os dados/progresso pessoal nessas plataformas beta NÃO serão salvos ou transferidos para a produção +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Os usuários na versão beta terão uma conta separada da produção.** A versão beta usa um banco de dados fisicamente separado da produção. Isso nos dá a capacidade de evitar qualquer perda acidental de dados ou modificações. A equipe de desenvolvimento pode limpar o banco de dados nesta versão beta conforme necessário. -- #### Não há garantias na disponibilidade e confiabilidade das plataformas beta +- **The beta platforms do not provide any assurances regarding uptime and reliability** Espera-se que a implantação seja frequente e em iterações rápidas, às vezes várias vezes ao dia. Como resultado, haverá tempos de inatividade inesperados ou funcionalidades quebradas na versão beta. -- #### Não envie usuários regulares para este site como uma medida de confirmar uma correção +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** O site beta é e sempre foi para melhorar o desenvolvimento e os testes locais, nada mais. Não é uma promessa do que está por vir, mas um vislumbre do que está sendo trabalhado. -- #### O login na página pode parecer diferente da produção +- **Sign in page may look different than production** Nós utilizamos um locatário de teste para o freeCodeCamp.dev no Auth 0 e, portanto, não temos a capacidade de definir um domínio personalizado. Isso faz com que todas as callbacks de redirecionamento e a página de login apareçam em um domínio padrão como: `https://freecodecamp-dev.auth0.com/`. Isso não afeta a funcionalidade e é o mais próximo da produção que conseguimos. diff --git a/docs/i18n/portuguese/how-to-enable-new-languages.md b/docs/i18n/portuguese/how-to-enable-new-languages.md index 56a6b15f8bf..b40ab720107 100644 --- a/docs/i18n/portuguese/how-to-enable-new-languages.md +++ b/docs/i18n/portuguese/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Ativando vídeos localizados +### Enabling Localized Videos Para os desafios em vídeo, você precisa fazer algumas alterações. Primeiro, adicione o novo idioma (locale) à consulta do GraphQL no arquivo `client/src/templates/Challenges/video/Show.tsx`. Por exemplo, para adicionar Dothraki à consulta: @@ -270,7 +270,7 @@ videoLocaleIds: Joi.when('challengeType', { }), ``` -## Interface do client +## Client UI Você precisará dar um passo adicional para lidar com as traduções da interface do client. @@ -283,7 +283,7 @@ Você vai querer copiar os seguintes arquivos de `/client/i18n/locales/english` - `motivation.json` - `trending.json` -## Testar traduções localmente +## Testing Translations Locally Se quiser testar as traduções localmente, antes de adicioná-las ao nosso repositório principal - pule as alterações de fluxo de trabalho do Crowdin. Siga as etapas para habilitar um idioma e, em seguida, baixe as traduções do Crowdin e as carregue em seu código local. @@ -303,11 +303,11 @@ Quando estes arquivos estiverem no local certo, você deve poder usar `pnpm run Para implantar novos idiomas em News, você precisa criar dois PRs. Um PR será para o [repositório do CDN](https://github.com/freeCodeCamp/cdn), enquanto o outro será para o [repositório News](https://github.com/freeCodeCamp/news). -## Preparação do repositório do CDN para o novo idioma +## Prep the CDN Repo for the New Language News busca os links de tendências e títulos de artigos do nosso CDN durante a build e adiciona-os ao rodapé. News também busca os arquivos Day.js do CDN durante a build para fazer a localização das datas e horários para cada idioma. -### Adicionar um Arquivo YAML para os artigos populares +### Add a YAML File for Trending Articles Faça a clonagem do repositório [CDN](https://github.com/freeCodeCamp/cdn) e crie um branch. @@ -329,7 +329,7 @@ article3link: ... ... ``` -### Adicionar um arquivo de localização Day.js para o novo idioma +### Add a Day.js Locale File for the New Language Por padrão, Day.js só inclui inglês como local. Para habilitá-lo para funcionar com outros idiomas, você precisa adicionar um novo arquivo de locale Day.js ao CDN. @@ -367,13 +367,13 @@ Copie o código de local de Day.js da nova aba para o novo arquivo que você cri Em seguida, abra um PR para o repositório do CDN para adicionar os arquivos YAML e Day.js para revisão. -## Preparação do repositório do CDN para o novo idioma +## Prep the News Repo for the New Language O [repositório de News](https://github.com/freeCodeCamp/news) puxa dados de uma instância do Ghost, os arquivos que você adicionou ao CDN, faz a build de News e o implementa. > [!WARN] Pull requests para o repositório News _precisam_ vir do mesmo repositório. Você não deve trabalhar a partir de um fork nesse passo. -### Modificar o arquivo de configuração principal +### Modify the Main Config File Clonar o repositório News e criar uma branch. @@ -407,7 +407,7 @@ const algoliaIndices = { }; ``` -### Adicionar os arquivos em JSON do i18next para o novo idioma +### Add the i18next JSON Files for the New Language Em seguida, vá para o diretório `config/i18n/locales`, crie uma pasta e informe o nome do novo idioma que você está adicionando. Por exemplo, se você estiver lançando News em dothraki, crie uma pasta chamada `dothraki`. diff --git a/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md b/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md index 550fab6e5cc..b2b3e304b28 100644 --- a/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md @@ -71,7 +71,7 @@ Apoiamos principalmente o desenvolvimento em sistemas Linux e Unix, como o Ubunt | [pnpm](https://pnpm.io/installation) | `8.x` | - | | [Servidor da Comunidade MongoDB](https://docs.mongodb.com/manual/administration/install-community/) | `5.0.x` | - | -> [!ATTENTION] Se você tem uma versão diferente, instale a versão recomendada. Só podemos suportar problemas de instalação para versões recomendadas. See [troubleshooting section](troubleshooting-development-issues.md) for details. +> [!ATTENTION] Se você tem uma versão diferente, instale a versão recomendada. Só podemos suportar problemas de instalação para versões recomendadas. Veja [a seção de solução de problemas](troubleshooting-development-issues.md) para detalhes. Se o Node.js já estiver instalado em sua máquina, execute os seguintes comandos para validar as versões: diff --git a/docs/i18n/portuguese/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/portuguese/how-to-setup-freecodecamp-mobile-app-locally.md index 3e40cf08156..885d387643a 100644 --- a/docs/i18n/portuguese/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/portuguese/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Siga este guia para configurar a aplicação para dispositivos móveis do freeCo Alguns dos fluxos de trabalho de contribuição — como a correção de erros na base de código — necessitam que você execute a aplicação do freeCodeCamp localmente. -### Como preparar sua máquina local +## How to Prepare your Local Machine Comece instalando o software pré-requisito para seu sistema operacional. -#### Pré-requisitos +### Prerequisites | Pré-requisito | Versão | Observações | | ------------------------------- | ------ | -------------------------------------------- | @@ -26,7 +26,7 @@ dart --version Depois de ter os pré-requisitos instalados, você precisa preparar seu ambiente de desenvolvimento. Isto é comum para muitos fluxos de trabalho de desenvolvimento, e você só precisará fazer isso uma vez. -##### Siga estas etapas para deixar seu ambiente de desenvolvimento pronto: +#### Follow these steps to get your development environment ready: 1. Instale o [Git](https://git-scm.com/) ou seu cliente Git favorito, se você ainda não fez isso. Atualize para a versão mais recente. A versão que veio com seu SO pode estar desatualizada. @@ -40,7 +40,7 @@ Depois de ter os pré-requisitos instalados, você precisa preparar seu ambiente Nós recomendamos muito usar o [Visual Studio Code](https://code.visualstudio.com/) ou o Android Studio. Também recomendamos instalar as [extensões](https://docs.flutter.dev/get-started/editor?tab=vscode) oficiais. -## Faça o fork do repositório no GitHub +## Fork the Repository on GitHub [Forking](https://help.github.com/articles/about-forks/) é uma etapa onde você obtém sua própria cópia do repositório (vulgo _repo_) no GitHub. @@ -58,7 +58,7 @@ Isso é essencial, pois permite que você trabalhe em sua própria cópia da apl 3. Depois que o repositório recebeu um fork, você será redirecionado para a cópia do repositório em `https://github.com/YOUR_USER_NAME/mobile` (`YOUR_USER_NAME` será substituído pelo seu nome de usuário do GitHub). -## Clonar o seu fork no GitHub +## Clone your Fork from GitHub [Clonar](https://help.github.com/articles/cloning-a-repository/) é onde ** você faz o download de uma cópia** de um repositório de um local `remoto` que pertence a você ou a outra pessoa. No seu caso, este local remoto é o seu `fork` do repositório freeCodeCamp que deve estar disponível em `https://github.com/YOUR_USER_NAME/mobile`. (`YOUR_USER_NAME` será substituído pelo seu nome de usuário do GitHub.) @@ -78,7 +78,7 @@ Isto vai baixar todo o repositório da aplicação do freeCodeCamp para disposit Nota: `--depth=1` cria um clone raso do seu fork, com apenas o histórico mais recente. -## Configurar sincronização a partir do pai +## Set up Syncing from Parent Agora que você baixou uma cópia do seu fork, será necessário configurar um remote `upstream` para o repositório pai. @@ -113,7 +113,7 @@ Agora que você baixou uma cópia do seu fork, será necessário configurar um r upstream https://github.com/freeCodeCamp/mobile.git (push) ``` -## Executar a aplicação do freeCodeCamp para dispositivos móveis localmente +## Running freeCodeCamp Mobile App Locally Agora que você tem uma cópia local da aplicação do freeCodeCamp para dispositivos móveis, você pode seguir estas instruções para executá-la localmente. @@ -172,7 +172,7 @@ flutter run > [!TIP] Se estiver usando o VSCode ou o Android Studio, poderá iniciar a aplicação facilmente sem ter de executar os comandos no terminal. Mais informações [aqui](https://docs.flutter.dev/get-started/test-drive). -## Fazer alterações localmente +## Making Changes Locally Agora você pode fazer alterações nos arquivos e fazer commit das suas alterações no clone local do seu fork. @@ -361,7 +361,7 @@ Siga estes passos: git push origin branch/nome-aqui ``` -## Propondo um Pull Request (PR) +## Proposing a Pull Request (PR) Após ter feito as alterações, veja [como abrir um Pull Request](how-to-open-a-pull-request.md). @@ -374,7 +374,7 @@ A quick reference to the commands that you will need when working locally. | `npm ci` | Installs / re-install all dependencies and bootstraps the different services. | | `npm run seed` | Parses all the challenge markdown files and inserts them into MongoDB. | --> -## Solução de problemas +## Troubleshooting ### Problemas com a instalação dos pré-requisitos recomendados @@ -398,7 +398,7 @@ Se você receber erros durante a instalação das dependências, certifique-se d Seja paciente, pois a primeira configuração pode demorar um pouco, dependendo da largura de banda da sua rede. -## Obter ajuda +## Getting Help Se você está com dificuldades e precisa de ajuda, fique à vontade em perguntar na categoria ['Contributors' (colaboradores) em nosso fórum](https://forum.freecodecamp.org/c/contributors) ou [na sala de bate-papo dos colaboradores](https://discord.gg/PRyKn3Vbay). diff --git a/docs/i18n/portuguese/how-to-work-on-coding-challenges.md b/docs/i18n/portuguese/how-to-work-on-coding-challenges.md index ca699f33a28..760bb262a2a 100644 --- a/docs/i18n/portuguese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/portuguese/how-to-work-on-coding-challenges.md @@ -486,13 +486,15 @@ Você também é capaz de testar um desafio individualmente seguindo as seguinte ``` pnpm run test -- -g challenge-title-goes-here ``` -Quando você verificar que cada desafio modificado passou nos testes, [crie um pull request](how-to-open-a-pull-request.md). - > [!TIP] Você pode definir a variável de ambiente `LOCALE` no `.env` no idioma do(s) desafio(s) que precisa testar. > > Os valores atualmente aceitos são `english` e `chinese`, com `english` sendo o padrão. -### Links úteis +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Useful Links Criação e edição de desafios: diff --git a/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md b/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md index 921531887da..7ae9759c4fe 100644 --- a/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md @@ -266,7 +266,11 @@ Seria bom manter as chaves na mesma ordem entre todos os arquivos também. Além > [!NOTE] O underscore (`_`) é um caractere reservado para chaves dos arquivos que ficam do lado do client. Veja [a documentação](https://www.i18next.com/translation-function/plurals) para saber como são usados. -## Documentação útil +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Helpful Documentation - [documentação react-i18next](https://react.i18next.com/latest/usetranslation-hook) - [documentação i18next](https://www.i18next.com/translation-function/essentials) diff --git a/docs/i18n/portuguese/how-to-work-on-practice-projects.md b/docs/i18n/portuguese/how-to-work-on-practice-projects.md index a5ac6e771fc..ed98f66140f 100644 --- a/docs/i18n/portuguese/how-to-work-on-practice-projects.md +++ b/docs/i18n/portuguese/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ Um script único que atualiza automaticamente a frontmatter nos arquivos markdow ```bash pnpm run update-step-titles ``` + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/portuguese/how-to-work-on-the-component-library.md b/docs/i18n/portuguese/how-to-work-on-the-component-library.md index f14d2dca1d6..1a5bb5c73a7 100644 --- a/docs/i18n/portuguese/how-to-work-on-the-component-library.md +++ b/docs/i18n/portuguese/how-to-work-on-the-component-library.md @@ -1,7 +1,7 @@ -Bem-vindo à biblioteca `ui-components` do freeCodeCamp. Os componentes são construídos, em grande parte, do zero, com elementos HTML básicos e [Tailwind CSS](https://tailwindcss.com/). - # Como trabalhar na biblioteca de componentes +Bem-vindo à biblioteca `ui-components` do freeCodeCamp. Os componentes são construídos, em grande parte, do zero, com elementos HTML básicos e [Tailwind CSS](https://tailwindcss.com/). + > [!NOTE] > > O freeCodeCamp tem usado componentes do Bootstrap na interface do usuário. No entanto, estamos nos afastando disso e construindo nossa própria biblioteca de componentes, o que ajuda a padronizar nossos padrões de UX/UI e melhorar a acessibilidade. O projeto é acompanhado [nesta issue do GitHub](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). @@ -91,16 +91,20 @@ Para executar testes contra a biblioteca de componentes, execute o seguinte coma pnpm run test-ui-components ``` -## Adicionar pacotes à biblioteca de componentes da UI +## Proposing a Pull Request (PR) -Restringimos a adição de novos pacotes aos componentes da UI para ajudar com a manutenção do projeto. Na hipótese de você achar que uma dependência é necessária, consulte os gestores primeiro e use o seguinte comando para adicionar um pacote: +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). + +## Adding Packages to the UI-Component Library + +We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: ```bash cd tools/ui-components pnpm add package_name ``` -### Links úteis +## Useful Links - [Testes de acessibilidade](https://testing-library.com/docs/dom-testing-library/api-accessibility) - [Ordem de prioridade das consultas da biblioteca de testes do React](https://testing-library.com/docs/queries/about/#priority) diff --git a/docs/i18n/portuguese/how-to-work-on-the-docs-theme.md b/docs/i18n/portuguese/how-to-work-on-the-docs-theme.md index 797d9d91b5c..93b6fd32516 100644 --- a/docs/i18n/portuguese/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/portuguese/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Normalmente, você não precisaria alterar nenhuma configuração ou compilar o Instale o freeCodeCamp localmente ([veja o guia de instalação local](how-to-setup-freecodecamp-locally)). Nós empacotamos a CLI com as ferramentas de desenvolvimento para que você possa executar o comando abaixo, conforme necessário, a partir da raiz do repositório: -#### Veicular e iniciar apenas o site da documentação - ```console pnpm run docs:serve ``` > O site da documentação deve estar disponível em + +## Proposing a Pull Request (PR) + +After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). diff --git a/docs/i18n/portuguese/moderator-handbook.md b/docs/i18n/portuguese/moderator-handbook.md index 7b15017564e..ba45e4dd826 100644 --- a/docs/i18n/portuguese/moderator-handbook.md +++ b/docs/i18n/portuguese/moderator-handbook.md @@ -39,7 +39,7 @@ Você pode nos ajudar a organizar e moderar issues usando etiquetas [dessa lista Preste atenção especial às etiquetas `"help wanted"` e `"first timers only"`. Elas devem ser adicionadas aos tópicos que você considere que possam ser abertos aos potenciais contribuidores para realizar um "pull request". -Uma etiqueta `"first timers only"` deve ser aplicada a uma issue trivial (ex.: consertar um erro de digitação) e deve incluir informações adicionais. Você pode usar esse [modelo de resposta](moderator-handbook.md#first-timer-only-issues) para a triagem. +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### Fechando issues e pull requests parados, desatualizados ou inativos @@ -49,7 +49,7 @@ Uma etiqueta `"first timers only"` deve ser aplicada a uma issue trivial (ex.: c - Se o criador do PR pedir assistência adicional ou mais tempo, as regras acima podem ser revistas após uma resposta. Em todo caso, os moderadores devem usar o melhor julgamento para resolverem o estado do PR. -> [!TIP] Recomendamos usar essa lista de [modelos de resposta](moderator-handbook.md#reply-templates) padrão enquanto estiver monitorando issues. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### Moderando pull requests @@ -63,7 +63,7 @@ Pull Requests (PRs) são como os colaboradores enviam alterações para o reposi Você também pode revisar isso diretamente no GitHub e decidir fazer merge ou não. Precisamos ter um pouco mais de cuidado com relação a isso, pois milhões de pessoas encontrarão este texto enquanto usam o currículo do freeCodeCamp. O pull request deixa o texto mais claro sem deixá-lo muito mais longo? As edições são relevantes e não são excessivamente pedantes? Lembre-se que nosso objetivo é que os desafios sejam mais claros e curtos dentro do possível. Não são o lugar para detalhes obscuros. Os contribuidores talvez tentem adicionar links para recursos dos desafios. - Você pode fechar pull requests inválidos e respondê-los com esses [modelos de resposta](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). Se as mudanças parecem boas, por favor aprove-as comentando "LGTM" (Looks Good To Me - me parece bom, em inglês). Uma vez que um pull request tiver pelo menos duas aprovações (incluindo a sua) dos moderadores ou equipe de desenvolvedores, você pode fazer o merge. @@ -75,7 +75,7 @@ Pull Requests (PRs) são como os colaboradores enviam alterações para o reposi Alguns contribuidores podem tentar adicionar mais testes para cobrir casos confusos pedantes. Precisamos ter cuidado para não deixarmos o desafio muito complicado. Esses desafios e seus testes devem ser simples e intuitivos na medida do possível. Além dos desafios de algoritmo e a seção de preparação para entrevistas, os estudantes devem ser capazes de resolver cada desafio em aproximadamente 2 minutos. - Você pode fechar pull requests inválidos e respondê-los com esses [modelos de resposta](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). Se as mudanças parecem boas, por favor aprove-as comentando "LGTM". Uma vez que um pull request tiver pelo menos duas aprovações (incluindo a sua) dos moderadores ou equipe de desenvolvedores, você pode fazer o merge. @@ -142,7 +142,7 @@ Muitas vezes, um pull request será obviamente de baixo esforço. Muitas vezes, Há também situações em que o colaborador está tentando adicionar um link para o seu próprio site, incluir uma biblioteca que criou, ou tem uma edição frívola que não serve para ajudar ninguém, exceto a si mesmo. -Você pode fechar pull requests inválidos e respondê-los com esses [modelos de resposta](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Outras diretrizes para moderadores no GitHub @@ -344,238 +344,3 @@ Essa tirinha da XKDC resume perfeitamente o pensamento da maioria das comunidade
Obrigado por ler isto, e obrigado por ajudar a comunidade de desenvolvedores! - -## Modelos de resposta - -Esses são alguns dos modelos de resposta que você talvez use enquanto estiver revisando issues/pull requests. - -> Você pode fazer seu próprio modelo com a funcionalidade embutida do GitHub chamada [saved replies](https://github.com/settings/replies/) ou usar as citadas abaixo. - -### Obrigado - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Obrigado e parabéns - -> Para agradecer e encorajar colaboradores de primeira viagem. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Erro de compilação - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Sincronização de forks - -> Quando um PR não está atualizado com a branch `main`. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. - -Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 -```` - -### Conflitos de merge - -> Quando um PR tem conflitos de merge isso precisa ser resolvido.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ Se é a primeira vez de um colaborador e se ele tem um conflito de merge, os mantenedores resolverão o conflito para ele. - -### PR duplicado - -> Quando um PR é duplo ou repetitivo. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Fechando pull requests inválidos - -> Quando um PR é inválido. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> Quando o PR adiciona links para recursos externos. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Adicionando comentário sobre erros de iniciante - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Fechando issues inválidas - -> Quando uma issue se refere ao código do usuário do freeCodeCamp. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> Quando uma issue é a mesma que uma issue anterior. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> Quando uma issue foi resolvida na fase de preparo. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Issues de `first timer only` - -> Quando uma issue é considerada eligível pela primeira vez como contribuição ao código. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Solicitações de atribuição - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/portuguese/reply-templates.md b/docs/i18n/portuguese/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/portuguese/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/portuguese/security-hall-of-fame.md b/docs/i18n/portuguese/security-hall-of-fame.md index 64658bcb5bb..c0bc3c12153 100644 --- a/docs/i18n/portuguese/security-hall-of-fame.md +++ b/docs/i18n/portuguese/security-hall-of-fame.md @@ -8,4 +8,4 @@ Embora não possamos oferecer nenhuma recompensa ou troca no momento, agradecemo - Peter Samir https://www.linkedin.com/in/peter-samir/ - Laurence Tennant ([@hyperreality](https://github.com/hyperreality)) trabalhando com IncludeSecurity.com - [GHSA-cc3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Agradecemos por suas contribuições :pray: +> **Thank you for your contributions :pray:** diff --git a/docs/i18n/ukrainian/FAQ.md b/docs/i18n/ukrainian/FAQ.md index 836bb732dda..8afda08cafc 100644 --- a/docs/i18n/ukrainian/FAQ.md +++ b/docs/i18n/ukrainian/FAQ.md @@ -1,12 +1,16 @@ -### Я лише починаю ознайомлення з GitHub та відкритим вихідним кодом. З чого мені варто почати? +# Поширені питання + +Відповіді на часті питання. + +## Я лише починаю ознайомлення з GitHub та відкритим вихідним кодом. З чого мені варто почати? Прочитайте [«Як зробити внесок до відкритого вихідного коду»](https://github.com/freeCodeCamp/how-to-contribute-to-open-source). Там є вичерпні вказівки для тих, хто вперше стикається з такими проєктами. Там також є багато порад для роботи з відкритим вихідним кодом. -### Що мені потрібно знати, щоб зробити внесок до кодової бази? +## Що мені потрібно знати, щоб зробити внесок до кодової бази? freeCodeCamp працює на сучасному стеку JavaScript. Якщо ви хочете зробити внесок до нашої кодової бази, ви повинні бути ознайомленими із JavaScript та іншими технологіями, якими ми користуємось: Node.js, MongoDB, OAuth 2.0, React, Gatsby та Webpack. -### Чи можу я перекладати ресурси freeCodeCamp? +## Чи можу я перекладати ресурси freeCodeCamp? Так! Ви можете почати перекладати на будь-яку з 30+ мов, які доступні на нашій локалізаційній платформі. @@ -14,15 +18,15 @@ freeCodeCamp працює на сучасному стеку JavaScript. Якщ Якщо ви хочете зробити внесок до перекладу, будь ласка, спочатку [прочитайте цей довідник](how-to-translate-files.md). -### Чи можу я писати публікації або знімати відео для freeCodeCamp? +## Чи можу я писати публікації або знімати відео для freeCodeCamp? -Так! Ви можете зробити внесок до новин та ютуб-каналу. +Так! Ви можете зробити внесок до новин та каналу на YouTube. Якщо ви зацікавлені в написанні публікацій, відвідайте цей [посібник з публікацій](https://www.freecodecamp.org/news/how-to-write-for-freecodecamp/). А ще прочитайте нашу [інструкцію зі стилістичного оформлення](https://www.freecodecamp.org/news/developer-news-style-guide/); вона допомагає в написанні кращих публікацій. -Щоб допомогти у створенні навчальних відео, слідуйте [посібнику з ютуб-каналу](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). +Щоб допомогти у створенні навчальних відео, слідуйте [посібнику з каналу на YouTube](https://www.freecodecamp.org/news/how-to-contribute-to-the-freecodecamp-community-youtube-channel-b86bce4c865/). -### Як повідомити про нову помилку? +## Як повідомити про нову помилку? Якщо ви вважаєте, що знайшли помилку, то спершу прочитайте публікацію [«Як повідомити про помилку»](https://www.freecodecamp.org/news/how-to-report-a-bug-to-freecodecamp/) та виконайте її вказівки. @@ -30,33 +34,33 @@ freeCodeCamp працює на сучасному стеку JavaScript. Якщ Будь ласка, зверніть увагу на те, що завдання на GitHub стосуються лише проблем щодо кодової бази та не мають ніякого відношення до допомоги з програмування. Якщо у вас є сумніви, то варто [звернутися за допомогою на форум](https://forum.freecodecamp.org), а вже потім створювати завдання на GitHub. -### Як повідомити про проблему з безпекою? +## Як повідомити про проблему з безпекою? Будь ласка, не створюйте завдань на GitHub щодо питань безпеки. Натомість [слідуйте нашій політиці безпеки](https://contribute.freecodecamp.org/#/security). -### Я здобуваю освіту. Чи може робота на платформі зараховуватися мені в залікові кредити? +## Я здобуваю освіту. Чи може робота на платформі зараховуватися мені в залікові кредити? Так. Але зверніть, будь ласка, увагу, що ми не можемо надати жодних графіків чи документів, які вимагатиме ваш коледж або університет. Ми отримуємо багато запитів на злиття та внесків до коду від розробників-волонтерів і ми поважаємо їхні час та зусилля. Ми поважаємо усіх наших користувачів, а тому не надаємо жодним запитам особливого пріоритету лише через те, що вони пов’язані з навчанням у закладах освіти. Ми просимо вас враховувати це та відповідно планувати свій час заздалегідь під час роботи над кодом. -### Чому на завданнях бувають різні позначки? +## Чому на завданнях бувають різні позначки? Техпідтримка, що відповідає за код, [сортує](https://en.wikipedia.org/wiki/Software_bug#Bug_management) завдання та запити на злиття залежно від пріоритету, складності та інших факторів. [Тут ви можете ознайомитися з усіма їхніми значеннями](https://github.com/freecodecamp/freecodecamp/labels). -### Звідки почати, якщо я хочу працювати над завданням? +## Звідки почати, якщо я хочу працювати над завданням? Вам варто переглянути [**`help wanted`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) або [**`first timers only`**](https://github.com/freeCodeCamp/freeCodeCamp/issues?q=is%3Aopen+is%3Aissue+label%3A%22first+timers+only%22), щоб швидко ознайомитись з доступними завданнями. > [!TIP] Завдання в **`help wanted`** загальнодоступні, тож вам не треба отримувати дозволи на роботу з ними. А ось завдання з позначкою **`first timers only`** — це спеціальні завдання для людей, які ще не робили внесок до кодової бази freeCodeCamp. -### Знайшлась друкарська помилка. Чи потрібно повідомляти про цю проблему, перш ніж зробити запит на злиття? +## Знайшлась друкарська помилка. Чи потрібно повідомляти про цю проблему, перш ніж зробити запит на злиття? Для друкарських та орфографічних помилок можна відразу відкрити запит на злиття без створення завдання. Не забудьте вказати деталі в описі запиту на злиття, щоб допомогти нам переглянути ваш внесок (навіть якщо там незначна зміна). Створюйте завдання, якщо ви хочете обговорити глобальніші аспекти кодової бази або навчальної програми. -### Яким чином можна отримати доручене завдання? +## Яким чином можна отримати доручене завдання? Зазвичай ми доручаємо завдання лише тим користувачам, які вже давно нам допомагають. Натомість ми дотримуємось такої політики, щоб бути справедливими до кожного: @@ -69,7 +73,7 @@ freeCodeCamp працює на сучасному стеку JavaScript. Якщ - Чи дотримано списку запитів на злиття? - Чи змістовна назва у вашого запиту на злиття? -### Я хочу бути модератором freeCodeCamp. З чого мені варто почати? +## Я хочу бути модератором freeCodeCamp. З чого мені варто почати? Модератори нашої спільноти — наші герої. Їхні добровільні внески роблять freeCodeCamp безпечною та гостинною спільнотою. @@ -83,11 +87,11 @@ freeCodeCamp працює на сучасному стеку JavaScript. Якщ Коротко: поважайте інших. Ми — люди з усього світу. Зважаючи на це, будь ласка, слідкуйте за своїм спілкуванням із людьми інших культур. -Якщо ви практикували вищезгадане **деякий час** та хтось із модераторів рекомендує вас, з вами зв’яжеться співробітник та залучить до команди модераторів. Робота над відкритим кодом є волонтерською, і наш час обмежений. Ми розуміємо, що в вашому випадку це правда. Тому ми наголошуємо на тому, щоб бути **послідовними**, а не взаємодіяти у спільноті 24/7. +Якщо ви практикували вищезгадане **деякий час** та хтось із модераторів рекомендує вас, з вами зв’яжеться співробітник та залучить до команди модераторів. Робота над відкритим кодом є волонтерською, і наш час обмежений. Ми розуміємо, що у вашому випадку це правда. Тому ми наголошуємо на тому, щоб бути **послідовними**, а не взаємодіяти у спільноті 24/7. Див. наш [довідник модератора](moderator-handbook.md) для детальнішого списку обов’язків модератора та наших очікувань від них. -### Моя проблема не висвітлена у цій документації. +## Моя проблема не висвітлена у цій документації. **Не соромтеся звертатися за допомогою до:** @@ -98,7 +102,7 @@ freeCodeCamp працює на сучасному стеку JavaScript. Якщ Заздалегідь дякуємо за ваші ввічливість та терпіння. Пам'ятайте, що ця спільнота здебільшого складається з волонтерів. -### Додаткова допомога +## Додаткова допомога Якщо у вас є запитання щодо стека, архітектури коду, перекладів чи будь-чого іншого, зв’яжіться з нашою командою [на форумі](https://forum.freecodecamp.org/g/team). diff --git a/docs/i18n/ukrainian/_sidebar.md b/docs/i18n/ukrainian/_sidebar.md index 6b89ec5570a..71826c88fa5 100644 --- a/docs/i18n/ukrainian/_sidebar.md +++ b/docs/i18n/ukrainian/_sidebar.md @@ -8,33 +8,35 @@ - **Внесок до коду** - [Налаштування freeCodeCamp](how-to-setup-freecodecamp-locally.md) - [Передові практики написання коду](codebase-best-practices.md) - - [Відкриття запиту на злиття](how-to-open-a-pull-request.md) - - [Робота над кодовою базою](how-to-contribute-to-the-codebase.md) - - [Робота над завданнями з кодом](how-to-work-on-coding-challenges.md) - - [Робота над компонентною бібліотекою](how-to-work-on-the-component-library.md) - - [Робота над практичними проєктами](how-to-work-on-practice-projects.md) - - [Робота над мобільним застосунком](how-to-setup-freecodecamp-mobile-app-locally.md) - - [Робота над туторіалами з CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) - - [Робота над локалізованим вебзастосунком](how-to-work-on-localized-client-webapp.md) - - [Робота над тестами Cypress](how-to-add-cypress-tests.md) - - [Робота над відеозавданнями](how-to-help-with-video-challenges.md) - - [Робота над документацією](how-to-work-on-the-docs-theme.md) + - [Work on Codebase](how-to-contribute-to-the-codebase.md) + - [Work on Coding Challenges](how-to-work-on-coding-challenges.md) + - [Work on Component Library](how-to-work-on-the-component-library.md) + - [Work on Practice Projects](how-to-work-on-practice-projects.md) + - [Work on Mobile app](how-to-setup-freecodecamp-mobile-app-locally.md) + - [Work on tutorials with CodeRoad](how-to-work-on-tutorials-that-use-coderoad.md) + - [Work on Localized Web App](how-to-work-on-localized-client-webapp.md) + - [Work on Cypress tests](how-to-add-cypress-tests.md) + - [Work on Video Challenges](how-to-help-with-video-challenges.md) + - [Work on Documentation](how-to-work-on-the-docs-theme.md) + - [Open a pull request](how-to-open-a-pull-request.md) - **Додаткові інструкції** - [Структура файлів навчальної програми](curriculum-file-structure.md) - [Налагодження вихідних е-листів локально](how-to-catch-outgoing-emails-locally.md) - [Встановлення freeCodeCamp на Windows (WSL)](how-to-setup-wsl.md) - - [Робочий процес токенів користувача](user-token-workflow.md) - - [Розв'язання проблем розробки](troubleshooting-development-issues.md) - - [Керівництво з аналітики](authors-analytics-manual.md) + - [Use Docker on Windows Home](how-to-use-docker-on-windows-home.md) + - [User Token Workflow](user-token-workflow.md) + - [Troubleshooting Development Issues](troubleshooting-development-issues.md) + - [Authors Analytics Manual](authors-analytics-manual.md) --- - **Посібники** (для персоналу & модераторів) - [Довідник модератора](moderator-handbook.md) - - [Довідник мовного керівника](language-lead-handbook.md) - - [Довідник DevOps](devops.md) - - [Розширення курсів VSCode](courses-vscode-extension.md) - - [Додавання нової мови](how-to-enable-new-languages.md) + - [Reply Templates](reply-templates.md) + - [Language Lead Handbook](language-lead-handbook.md) + - [DevOps Handbook](devops.md) + - [Courses VSCode Extension](courses-vscode-extension.md) + - [Enable New Language](how-to-enable-new-languages.md) --- diff --git a/docs/i18n/ukrainian/courses-vscode-extension.md b/docs/i18n/ukrainian/courses-vscode-extension.md index ce2fa8279db..2254c052a8b 100644 --- a/docs/i18n/ukrainian/courses-vscode-extension.md +++ b/docs/i18n/ukrainian/courses-vscode-extension.md @@ -1,6 +1,6 @@ -# Courses VSCode Extension +# Розширення VSCode Courses -This details the maintenance guidelines for the [freeCodeCamp/courses-vscode-extension](https://github.com/freeCodeCamp/courses-vscode-extension) repository which contains the source code for the [freeCodeCamp - Courses](https://marketplace.visualstudio.com/items?itemName=freeCodeCamp.freecodecamp-courses) extension. +Тут детально описано інструкції з обслуговування репозиторію [freeCodeCamp/courses-vscode-extension](https://github.com/freeCodeCamp/courses-vscode-extension), який містить вихідний код для розширення [freeCodeCamp - Courses](https://marketplace.visualstudio.com/items?itemName=freeCodeCamp.freecodecamp-courses). ## Публікування розширення @@ -21,21 +21,21 @@ git commit -am "(): " git push ``` -Optionally, you can push directly to `upstream/main`, but opening a new PR is recommended for a sanity check. +За бажанням, ви можете надіслати її одразу до `upstream/main`, але ми рекомендуємо створити новий PR для перевірки працездатності. -3. Create a new GitHub Release using the GitHub UI: +3. Створіть новий GitHub Release, використовуючи GitHub UI: -- Correctly increment the version number, when creating a new tag. -- Upload the `.vsix` file with the release. -- Publish the release, and confirm the action succeeded. +- Правильно збільште номер версії під час створення нового тегу. +- Завантажте файл `.vsix` із випуском. +- Опублікуйте випуск та підтвердьте успішність дії. -> [!NOTE] Creating a release requires write access to the `freeCodeCamp/courses-vscode-extension` repository. +> [!NOTE] Для створення випуску потрібен письмовий доступ до репозиторію `freeCodeCamp/courses-vscode-extension`. -## Manually Publishing the Extension +## Публікування розширення вручну -A manual upload to the Visual Studio Marketplace can be achieved, by following these steps: +Завантаження до Visual Studio Marketplace можна здійснити вручну, дотримуючись таких дій: -1. Visit https://marketplace.visualstudio.com/ and sign in -2. Navigate to the [freeCodeCamp Publisher page](https://marketplace.visualstudio.com/manage/publishers/freecodecamp) -3. Select the relevant extension, and select `Update` -4. Upload the file from your local files +1. Відвідайте https://marketplace.visualstudio.com/ та увійдіть +2. Перейдіть на [сторінку freeCodeCamp Publisher](https://marketplace.visualstudio.com/manage/publishers/freecodecamp) +3. Виберіть відповідне розширення та оберіть `Update` +4. Завантажте файл зі своїх локальних файлів diff --git a/docs/i18n/ukrainian/devops.md b/docs/i18n/ukrainian/devops.md index 44756ff360e..a1f0d06e88a 100644 --- a/docs/i18n/ukrainian/devops.md +++ b/docs/i18n/ukrainian/devops.md @@ -10,15 +10,15 @@ This repository is continuously built, tested, and deployed to **separate sets o This involves three steps to be followed in sequence: -1. Нові зміни (виправлення і функціонал) зливаються у нашу основну гілку розробки (`main`) через pull запити. -2. Ці зміни проходять через ряд автоматизованих тестів. +1. New changes (both fixes and features) are merged into our primary development branch (`main`) via pull requests. +2. These changes are run through a series of automated tests. 3. Once the tests pass we release the changes (or update them if needed) to deployments on our infrastructure. ### Building the codebase - Mapping Git Branches to Deployments Typically, [`main`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main) (the default development branch) is merged into the [`prod-staging`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) branch once a day and is released into an isolated infrastructure. -This is an intermediate release for our developers and volunteer contributors. Він також відомий як наш "staging" або "бета" реліз. +This is an intermediate release for our developers and volunteer contributors. It is also known as our "staging" or "beta" release. It is identical to our live production environment at `freeCodeCamp.org`, other than it using a separate set of databases, servers, web-proxies, etc. This isolation lets us test ongoing development and features in a "production" like scenario, without affecting regular users of freeCodeCamp.org's main platforms. @@ -28,7 +28,7 @@ This is the final release that moves changes to our production platforms on free ### Testing changes - Integration and User Acceptance Testing -We employ various levels of integration and acceptance testing to check on the quality of the code. Всі наші тести виконуються за допомогою таких програм, як [Github Actions CI](https://github.com/freeCodeCamp/freeCodeCamp/actions) та [Azure pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp). +We employ various levels of integration and acceptance testing to check on the quality of the code. All our tests are done through software like [GitHub Actions CI](https://github.com/freeCodeCamp/freeCodeCamp/actions) and [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp). We have unit tests for testing our challenge solutions, Server APIs, and Client User interfaces. These help us test the integration between different components. @@ -38,9 +38,9 @@ Together these tests help in preventing issues from repeating themselves and ens ### Deploying Changes - Pushing changes to servers -Ми налаштували безперервне програмне забезпечення доставки для внесення змін до наших серверів розробки і виробництва. +We have configured continuous delivery software to push changes to our development and production servers. -Після того, як зміни будуть відправлені в захищені гілки релізу, конвеєр збірки автоматично запускається для гілки. Гарбопроводи відповідають за будівництво артефактів та збереження їх у холодному сховищі для подальшого використання. +Once the changes are pushed to the protected release branches, a build pipeline is automatically triggered for the branch. The build pipelines are responsible for building artifacts and keeping them in a cold storage for later use. The build pipeline goes on to trigger a corresponding release pipeline if it completes a successful run. The release pipelines are responsible for collecting the build artifacts, moving them to the servers, and going live. @@ -154,68 +154,68 @@ For staff use: Once one of the staff members approves a release, the pipeline will push the changes live to freeCodeCamp.org's production CDN and API servers. -## Build, Test and Deployment Status +## Збірка, тест та статус розгортання -Here is the current test, build and deployment status of the codebase. +Ось поточний тест, збірка та статус розгортання кодової бази. -| Branch | Unit Tests | Integration Tests | Builds & Deployments | +| Гілка | Модульні тести | Інтеграційні тести | Збірки та розгортання | |:-------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:--------------------------------------------------------------------------------------------------------------------------------- | | [`main`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main) | [![Node.js CI](https://github.com/freeCodeCamp/freeCodeCamp/workflows/Node.js%20CI/badge.svg?branch=main)](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22) | [![Cypress E2E Tests](https://img.shields.io/endpoint?url=https://dashboard.cypress.io/badge/simple/ke77ns/main&style=flat&logo=cypress)](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | - | | [`prod-staging`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [![Node.js CI](https://github.com/freeCodeCamp/freeCodeCamp/workflows/Node.js%20CI/badge.svg?branch=prod-staging)](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-staging) | [![Cypress E2E Tests](https://img.shields.io/endpoint?url=https://dashboard.cypress.io/badge/simple/ke77ns/prod-staging&style=flat&logo=cypress)](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) | | [`prod-current`](https://github.com/freeCodeCamp/freeCodeCamp/tree/prod-staging) | [![Node.js CI](https://github.com/freeCodeCamp/freeCodeCamp/workflows/Node.js%20CI/badge.svg?branch=prod-current)](https://github.com/freeCodeCamp/freeCodeCamp/actions?query=workflow%3A%22Node.js+CI%22+branch%3Aprod-current) | [![Cypress E2E Tests](https://img.shields.io/endpoint?url=https://dashboard.cypress.io/badge/simple/ke77ns/prod-current&style=flat&logo=cypress)](https://dashboard.cypress.io/projects/ke77ns/analytics/runs-over-time) | [Azure Pipelines](https://dev.azure.com/freeCodeCamp-org/freeCodeCamp/_dashboards/dashboard/d59f36b9-434a-482d-8dbd-d006b71713d4) | -| `prod-next` (experimental, upcoming) | - | - | - | +| `prod-next` (експериментальне, майбутнє) | - | - | - | -## Early Access and Beta Testing +## Ранній доступ та бета-тестування -We welcome you to test these releases in a **"public beta testing"** mode and get early access to upcoming features to the platforms. Sometimes these features/changes are referred to as **next, beta, staging,** etc. interchangeably. +Ми вітаємо вас протестувати ці випуски в режимі **публічного бета-тестування** та отримати ранній доступ до майбутніх функціональностей платформи. Іноді ці функціональності/зміни також називають **наступними, бета, проміжними** тощо. -Your contributions via feedback and issue reports will help us in making the production platforms at `freeCodeCamp.org` more **resilient**, **consistent**, and **stable** for everyone. +Ваші внески у вигляді зворотного зв’язку та повідомлень про проблеми допоможуть нам зробити платформу `freeCodeCamp.org` більш **стійкою**, **послідовною** та **стабільною** для кожного. -We thank you for reporting bugs that you encounter and help in making freeCodeCamp.org better. You rock! +Ми вдячні за повідомлення про помилки, з якими ви стикаєтесь. Це допомагає покращити freeCodeCamp.org. Ви круті! -### Identifying the Upcoming Version of the Platforms +### Ідентифікація майбутньої версії платформ -Currently, a public beta testing version is available at: +Наразі публічне бета-тестування доступне на: -| Application | Language | URL | -|:----------- |:-------- |:---------------------------------------- | -| Learn | English | | -| | Espanol | | -| | Chinese | | -| News | English | | -| Forum | English | | -| | Chinese | | -| API | - | `https://api.freecodecamp.dev` | +| Програма | Мова | URL | +|:-------- |:---------- |:---------------------------------------- | +| Навчання | Англійська | | +| | Іспанська | | +| | Китайська | | +| Новини | Англійська | | +| Форум | Англійська | | +| | Китайська | | +| API | - | `https://api.freecodecamp.dev` | -> [!NOTE] The domain name is different than **`freeCodeCamp.org`**. This is intentional to prevent search engine indexing and avoid confusion for regular users of the platform. +> [!NOTE] Назва домену відрізняється від **`freeCodeCamp.org`**. Це є навмисним, щоб відвернути індексацію пошукової системи і запобігти непорозумінь для користувачів платформи. > -> The above list is not exhaustive of all the applications that we provision. Also, not all language variants are deployed in staging to conserve resources. +> Наведений вище список не є повним списком усіх програм, які ми забезпечуємо. Також не всі мовні варіанти розгорнуті у проміжній версії, щоб зберегти ресурси. -### Identifying the Current Version of the Platforms +### Ідентифікація поточної версії платформ -**The current version of the platform is always available at [`freeCodeCamp.org`](https://www.freecodecamp.org).** +**Поточна версія платформи завжди доступна на [`freeCodeCamp.org`](https://www.freecodecamp.org).** -The dev-team merges changes from the `prod-staging` branch to `prod-current` when they release changes. The top commit should be what you see live on the site. +Команда розробників об’єднує зміни з гілки `prod-staging` до `prod-current`, коли вони випускають зміни. Верхнім затвердженням має бути те, що ви побачите на сайті. -You can identify the exact version deployed by visiting the build and deployment logs available in the status section. Alternatively, you can also ping us in the [contributors chat room](https://discord.gg/PRyKn3Vbay) for a confirmation. +Ви можете ідентифікувати точну розгорнуту версію, відвідавши збірку та журнали розгортання, доступні в розділі статусу. Або ж ви можете написати нам у [чаті](https://discord.gg/PRyKn3Vbay) для підтвердження. ### Known Limitations There are some known limitations and tradeoffs when using the beta version of the platform. -- #### All data / personal progress on these beta platforms will NOT be saved or carried over to production +- **All data / personal progress on these beta platforms will NOT be saved or carried over to production** **Users on the beta version will have a separate account from the production.** The beta version uses a physically separate database from production. This gives us the ability to prevent any accidental loss of data or modifications. The dev-team may purge the database on this beta version as needed. -- #### There are no guarantees on the uptime and reliability of the beta platforms +- **The beta platforms do not provide any assurances regarding uptime and reliability** Deployment is expected to be frequent and in rapid iterations, sometimes multiple times a day. As a result, there will be unexpected downtime at times or broken functionality on the beta version. -- #### Do not send regular users to this site as a measure of confirming a fix +- **To ensure the effectiveness of the fix, it is advised not to direct regular users to this site for verification purposes.** The beta site is and always has been to augment local development and testing, nothing else. It's not a promise of what’s coming, but a glimpse of what is being worked upon. -- #### Sign in page may look different than production +- **Sign in page may look different than production** We use a test tenant for freeCodeCamp.dev on Auth0, and hence do not have the ability to set a custom domain. This makes it so that all the redirect callbacks and the login page appear at a default domain like: `https://freecodecamp-dev.auth0.com/`. This does not affect the functionality and is as close to production as we can get. @@ -736,7 +736,7 @@ Config changes to our NGINX instances are maintained on GitHub, these should be nginx -s reload ``` -**Docker Cluster:** +**Кластер Docker:** 1. SSH into the instance and navigate to the chat config path diff --git a/docs/i18n/ukrainian/how-to-enable-new-languages.md b/docs/i18n/ukrainian/how-to-enable-new-languages.md index 6f95ac951e9..c8610b4e59a 100644 --- a/docs/i18n/ukrainian/how-to-enable-new-languages.md +++ b/docs/i18n/ukrainian/how-to-enable-new-languages.md @@ -216,7 +216,7 @@ const algoliaIndices = { }; ``` -## Додавання локалізованих відео +### Enabling Localized Videos Вам потрібно дещо змінити стосовно відеозавдань. Спочатку додайте нову локаль до запиту GraphQL у файлі `client/src/templates/Challenges/video/Show.tsx`. Ось так додається дотракійська мова: @@ -270,7 +270,7 @@ videoLocaleIds: Joi.when('challengeType', { }), ``` -## Інтерфейс клієнта +## Client UI Вам потрібно здійснити додатковий крок для роботи з перекладами інтерфейсу клієнта. @@ -283,7 +283,7 @@ videoLocaleIds: Joi.when('challengeType', { - `motivation.json` - `trending.json` -## Тестування перекладів локально +## Testing Translations Locally Якщо ви хочете перевірити переклади локально, перш ніж додати їх до нашого основного репозиторію, то пропустіть зміни робочого процесу на Crowdin. Виконайте кроки для додавання мови, а потім завантажте переклади з Crowdin і додайте їх до свого локального коду. @@ -303,11 +303,11 @@ videoLocaleIds: Joi.when('challengeType', { Щоб започаткувати новини новою мовою, потрібно створити два PR. Один PR буде для [репозиторію CDN](https://github.com/freeCodeCamp/cdn), а інший — для [репозиторію News](https://github.com/freeCodeCamp/news). -## Приготуйте репозиторій CDN для нової мови +## Prep the CDN Repo for the New Language News отримує популярні посилання й назви статей із нашого CDN під час збірки та додає їх у нижній колонтитул. News також отримує файли Day.js із CDN під час збірки, щоб локалізувати дати та час кожної мови. -### Додайте файл YAML для популярних статей +### Add a YAML File for Trending Articles Клонуйте [репозиторій CDN](https://github.com/freeCodeCamp/cdn) та створіть нову гілку. @@ -329,7 +329,7 @@ article3link: ... ... ``` -### Додайте файл локалі Day.js для нової мови +### Add a Day.js Locale File for the New Language Day.js містить лише англійську локаль за замовчуванням. Щоб дозволити роботу з іншими мовами, потрібно додати новий файл локалі Day.js до CDN. @@ -367,13 +367,13 @@ Day.js містить лише англійську локаль за замов Потім відкрийте PR до репозиторію CDN, щоб додати файли YAML та Day.js для перегляду. -## Приготуйте репозиторій News для нової мови +## Prep the News Repo for the New Language [Репозиторій News](https://github.com/freeCodeCamp/news) отримує дані з екземпляра Ghost, файли, додані до CDN, будує News та розробляє їх. > [!WARN] PR для репозиторію News _повинні_ надходити з одного репозиторію. Не працюйте над цим кроком з розгалуження. -### Змініть головний файл конфігурації +### Modify the Main Config File Клонуйте репозиторій News та створіть нову гілку. @@ -407,7 +407,7 @@ const algoliaIndices = { }; ``` -### Додайте файли JSON i18next для нової мови +### Add the i18next JSON Files for the New Language Перейдіть до каталогу `config/i18n/locales`, створіть нову папку та надайте їй назву мови, яку додаєте. Наприклад, якщо ви додаєте новини дотракійською мовою, створіть папку під назвою `dothraki`. diff --git a/docs/i18n/ukrainian/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/ukrainian/how-to-setup-freecodecamp-mobile-app-locally.md index 54783937799..92a398b3ae7 100644 --- a/docs/i18n/ukrainian/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/ukrainian/how-to-setup-freecodecamp-mobile-app-locally.md @@ -2,11 +2,11 @@ Деякі з робочих процесів (наприклад, виправлення помилок у кодовій базі) вимагають локального запуску freeCodeCamp. -### Як підготувати локальну машину +## Як підготувати локальну машину Для початку встановіть передумовне програмне забезпечення для своєї операційної системи. -#### Передумови +### Передумови | Передумова | Версія | Примітки | | ------------------------------- | ------ | --------------------------------------------- | @@ -26,7 +26,7 @@ dart --version Як тільки ви встановили передумови, потрібно підготувати середовище розробки. Це характерно для багатьох робочих процесів розробки, і це потрібно зробити лише один раз. -##### Виконайте наступні дії, щоб підготувати середовище розробки: +#### Виконайте наступні дії, щоб підготувати середовище розробки: 1. Встановіть [Git](https://git-scm.com/) або інший клієнт Git, якщо ви досі цього не зробили. Оновіть його до останньої версії; версія, яка пов’язана з вашою ОС, може бути застарілою. diff --git a/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md b/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md index 7b09527aebc..186cd41550a 100644 --- a/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md +++ b/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md @@ -483,13 +483,15 @@ FCC_SUPERBLOCK='responsive-web-design' pnpm run test:curriculum ``` pnpm run test -- -g challenge-title-goes-here ``` -Як тільки ви переконались, що кожне змінене завдання проходить тести, [відкрийте запит на злиття](how-to-open-a-pull-request.md). - > [!TIP] Ви можете встановити змінну середовища ` LOCALE ` у `.env ` на мову завдань, які потрібно перевірити. > > Наразі прийнятними значеннями є `english` та `chinese` (`english` за замовчуванням). -### Корисні посилання +## Запропонуйте запит на злиття (PR) + +Як тільки ви затвердили свої зміни, див. [як відкрити запит на злиття](how-to-open-a-pull-request.md). + +## Корисні посилання Створення і редагування завдань: diff --git a/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md b/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md index 2eaf96b5842..571f09a906a 100644 --- a/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/ukrainian/how-to-work-on-localized-client-webapp.md @@ -266,6 +266,10 @@ const email = 'team@freecodecamp.org'; > [!NOTE] Підкреслення (`_`) є зарезервованим знаком для ключів у файлах клієнтської частини. Див. [документацію](https://www.i18next.com/translation-function/plurals) про те, як вони використовуються. +## Запропонуйте запит на злиття (PR) + +Як тільки ви затвердили свої зміни, див. [як відкрити запит на злиття](how-to-open-a-pull-request.md). + ## Корисна документація - [Документація react-i18next](https://react.i18next.com/latest/usetranslation-hook) diff --git a/docs/i18n/ukrainian/how-to-work-on-practice-projects.md b/docs/i18n/ukrainian/how-to-work-on-practice-projects.md index 68222908ba6..d460cf4107c 100644 --- a/docs/i18n/ukrainian/how-to-work-on-practice-projects.md +++ b/docs/i18n/ukrainian/how-to-work-on-practice-projects.md @@ -134,3 +134,7 @@ pnpm run delete-step X # де X є номером кроку, який потр ```bash pnpm run update-step-titles ``` + +## Запропонуйте запит на злиття (PR) + +Як тільки ви затвердили свої зміни, див. [як відкрити запит на злиття](how-to-open-a-pull-request.md). diff --git a/docs/i18n/ukrainian/how-to-work-on-the-component-library.md b/docs/i18n/ukrainian/how-to-work-on-the-component-library.md index 58f2e03ea47..748d30293d8 100644 --- a/docs/i18n/ukrainian/how-to-work-on-the-component-library.md +++ b/docs/i18n/ukrainian/how-to-work-on-the-component-library.md @@ -1,31 +1,31 @@ -Welcome to freeCodeCamp's `ui-components` library. The components are built mostly from scratch with basic HTML elements and [Tailwind CSS](https://tailwindcss.com/). +# Як працювати над компонентною бібліотекою -# How to Work on the Component Library +Ласкаво просимо до бібліотеки freeCodeCamp `ui-components`. Переважно компоненти побудовані з нуля завдяки базовим елементам HTML та [Tailwind CSS](https://tailwindcss.com/). > [!NOTE] > -> freeCodeCamp has been using Bootstrap components in the UI. However, we are moving away from it and building our own component library, which helps standardize our UX/UI patterns and improve accessibility. The project is tracked in [this GitHub issue](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). +> freeCodeCamp використовує компоненти Bootstrap в UI. Однак ми віддаляємось від цього та будуємо власну компонентну бібліотеку, яка допоможе стандартизувати наші шаблони UX/UI та покращити доступність. Проєкт відстежується у [цьому завданні на GitHub](https://github.com/freeCodeCamp/freeCodeCamp/issues/44668). -The following steps are recommended when working on a new component: +Для роботи над новим компонентом рекомендовані наступні кроки: -- Research and planning -- Implement the component -- Display the use cases on Storybook -- Write unit tests +- Дослідження та планування +- Реалізація компонента +- Показ сценаріїв використання на Storybook +- Написання модульних тестів -## Researching and Planning +## Дослідження та планування -Before building a component, you need to research and document on how the existing version behaves and looks, to ensure that the new one has matching styles and supports all the current usages. In order to meet the web accessibility requirements, you should also pay attention to the accessibility aspect of the component, see which HTML elements and ARIA attributes are used under the hood. +Перед побудовою компонента вам потрібно дослідити та задокументувати поведінку й вигляд поточної версії, щоб переконатись, що нова версія відповідатиме стилю та підтримуватиме усі поточні використання. Щоб відповідати вимогам доступності мережі, також звертайте увагу на аспекти доступності компонента, перегляньте, які елементи HTML та атрибути ARIA використовуються під капотом. -Once you have gathered enough information about the component, you can start thinking about the props interface. Ideally, the interface should be as similar to the current version as possible, to ease the adoption later on. Since we are using Bootstrap components, the simplest approach is to mimic [their implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src). +Як тільки ви зібрали достатньо інформації про компонент, можна почати думати про інтерфейс властивостей. В ідеалі інтерфейс повинен бути максимально схожим до поточної версії, щоб полегшити майбутнє впровадження. Оскільки ми використовуємо компоненти Bootstrap, найпростіший спосіб — імітувати [їхню реалізацію](https://github.com/react-bootstrap/react-bootstrap/tree/master/src). -We prefer smaller pull requests rather than a large one, because they speed up the review time and reduce cognitive overload for the reviewers. For that reason, you should think about how you would break down the implementation and come up with a delivery plan. +Ми надаємо перевагу коротким запитам на злиття, оскільки вони пришвидшують час на перегляд та зменшують когнітивне навантаження на рецензентів. З цієї причини подумайте, як би ви розбили реалізацію та розробили план доставки. -We recommend opening a separate GitHub issue for each component and include all the notes in the issue description. It can be used as a place to host all of your working notes, as well as a way to communicate the approach with the reviewers. We will use the issue thread for further discussion if needed. [The issue for Button component](https://github.com/freeCodeCamp/freeCodeCamp/issues/45357) can be used as a reference. +Ми рекомендуємо відкривати окреме завдання на GitHub для кожного компонента та додавати всі нотатки в опис завдання. Його можна використовувати як місце для розміщення всіх робочих нотаток, а також як спосіб донести свій підхід до рецензентів. За потреби ми використаємо тред завдання для подальшого обговорення. [Завдання для компонента Button](https://github.com/freeCodeCamp/freeCodeCamp/issues/45357) можна використати як зразок. -## Implementing the Component +## Реалізація компонента -A new component can be created using the following command from the root directory: +Новий компонент можна створити за допомогою наступної команди з кореневого каталогу: ```bash cd tools/ui-components @@ -33,75 +33,79 @@ cd tools/ui-components pnpm run gen-component MyComponent ``` -The command will generate a new folder inside the `ui-components` directory, with the following files: +Всередині каталогу `ui-components` команда згенерує папку з наступними файлами: -| File name | Purpose | +| Назва файлу | Призначення | | -------------------------- | ---------------------------------------------------------- | -| `index.ts` | It is used for exporting the component and its types. | -| `my-component.stories.tsx` | It is used for demoing the component on Storybook. | -| `my-component.test.tsx` | It is a test file. | -| `my-component.tsx` | It is where we implement the component. | -| `types.ts` | It is where we locate the component's interface and types. | +| `index.ts` | Використовується для експорту компонента та його типів. | +| `my-component.stories.tsx` | Використовується для демонстрації компонента на Storybook. | +| `my-component.test.tsx` | Тестовий файл. | +| `my-component.tsx` | Місце реалізації компонента. | +| `types.ts` | Місце розташування інтерфейсу та типів компонента. | -Each component is different, but in general, a component should: +Кожен компонент відрізняється, але загалом він повинен: -- Support forwarding ref -- Be styled for both light and dark themes -- Be styled internally based on their props (the consumers should not need to restyle the component with the `className` prop) -- Utilize the built-in styling system from Tailwind instead of having custom styles +- Підтримувати перенаправлення ref +- Бути стилізованим для світлої та темної тем +- Бути внутрішньо стилізованим на основі своїх властивостей (споживачам не знадобиться ще раз стилізувати компонент за допомогою властивості `className`) +- Використовувати вбудовану систему стилізації з Tailwind замість власних стилів -### Using Colors +### Використання кольорів -There are two color "layers" in the component library: +У компонентній бібліотеці є два «шари» кольорів: -- The base layer, where the color names describe what the colors are, e.g. `gray00`, `blue50` -- The semantic layer, where the color names describe what the colors are for, e.g. `foreground-primary`, `background-danger` +- Базовий шар, де назви кольорів описують колір, тобто `gray00`, `blue50` +- Семантичний шар, де назви кольорів описують для чого використані кольори, тобто `foreground-primary`, `background-danger` -Generally, when using colors in a component, you should choose semantic variables over the base ones. There are exceptions, however, specifically when you are styling the component's states such as hover, active, disabled, etc. In these cases, we recommend using the base variables directly instead of creating new semantic variables, since each component can have different styles for its states. +Під час використання кольору в компоненті варто надавати перевагу семантичним змінним. Однак бувають винятки, особливо коли ви стилізуєте стани компонента (hover, active, disabled тощо). У таких випадках ми рекомендуємо використовувати базові змінні, а не створювати семантичні змінні, оскільки кожен компонент може мати різні стилі для своїх станів. -> [!NOTE] Color definition can be found in the [`colors.css` file](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/tools/ui-components/src/colors.css). A color is only available for use if it is added to the [`tailwind.config.js` file](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/tools/ui-components/tailwind.config.js) under the `colors` property. +> [!NOTE] Визначення кольору можна знайти у файлі [`colors.css`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/tools/ui-components/src/colors.css). Колір доступний для використання лише якщо його додано до [ файлу `tailwind.config.js`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/tools/ui-components/tailwind.config.js) під властивістю `colors`. -### Useful Links +### Корисні посилання -- [Tailwind CSS Configuration](https://tailwindcss.com/docs/configuration) -- [React Bootstrap v0.33 Docs](https://react-bootstrap-v3.netlify.app) -- [Bootstrap 3.3.7 stylesheet](https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.css) -- [React Bootstrap current implementation](https://github.com/react-bootstrap/react-bootstrap/tree/master/src) -- [React Bootstrap current tests](https://github.com/react-bootstrap/react-bootstrap/tree/master/test) +- [Конфігурація CSS Tailwind](https://tailwindcss.com/docs/configuration) +- [Документація React Bootstrap v0.33](https://react-bootstrap-v3.netlify.app) +- [Таблиця стилів Bootstrap 3.3.7](https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.3.7/css/bootstrap.css) +- [Поточне впровадження React Bootstrap](https://github.com/react-bootstrap/react-bootstrap/tree/master/src) +- [Поточні тести React Bootstrap](https://github.com/react-bootstrap/react-bootstrap/tree/master/test) -## Displaying the Use Cases on Storybook +## Показ сценаріїв використання на Storybook -Use cases of the component should be added to the Storybook file (`.stories.tsx`). +Сценарії використання компонентів потрібно додати до файлу Storybook (`.stories.tsx`). -To start Storybook, run the following command from the root directory: +Щоб запустити Storybook, виконайте наступну команду з кореневого каталогу: ```bash pnpm run storybook ``` -The Storybook page is available on [http://localhost:6006](http://localhost:6006). +Сторінка Storybook доступна на [http://localhost:6006](http://localhost:6006). -## Writing Unit Tests +## Написання модульних тестів -We use [React Testing Library](https://testing-library.com/docs/react-testing-library/intro/) to write unit tests. The tests should assert that the components behave as expected and are accessible. +Ми використовуємо [React Testing Library](https://testing-library.com/docs/react-testing-library/intro/) для написання модульних тестів. Тести повинні підтверджувати, що компоненти поводяться як потрібно та є доступними. -To run tests against the component library, run the following command from the root directory: +Щоб запустити тести компонентної бібліотеки, виконайте наступну команду з кореневого каталогу: ```bash pnpm run test-ui-components ``` -## Adding Packages to the UI-Component Library +## Запропонуйте запит на злиття (PR) -We restrict adding new packages to the UI Components to help with the project's maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package: +Як тільки ви затвердили свої зміни, див. [як відкрити запит на злиття](how-to-open-a-pull-request.md). + +## Додавання пакетів до компонентної бібліотеки UI + +Ми обмежуємо додавання нових пакетів до компонентів UI, щоб допомогти з обслуговуванням проєкту. За рідкісних випадків, якщо на вашу думку потрібна залежність, будь ласка, обговоріть це зі спеціалістом з обслуговування та використайте наступну команду, щоб додати пакет: ```bash cd tools/ui-components pnpm add package_name ``` -### Useful Links +## Корисні посилання -- [Testing for Accessibility](https://testing-library.com/docs/dom-testing-library/api-accessibility) -- [Order of priority of React Testing Library's queries](https://testing-library.com/docs/queries/about/#priority) -- [Common mistakes with React Testing Library](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library) +- [Тестування доступності](https://testing-library.com/docs/dom-testing-library/api-accessibility) +- [Черговість запитів React Testing Library](https://testing-library.com/docs/queries/about/#priority) +- [Часті помилки при роботі з React Testing Library](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library) diff --git a/docs/i18n/ukrainian/how-to-work-on-the-docs-theme.md b/docs/i18n/ukrainian/how-to-work-on-the-docs-theme.md index a6c95ced7f8..ede8e6ef3a4 100644 --- a/docs/i18n/ukrainian/how-to-work-on-the-docs-theme.md +++ b/docs/i18n/ukrainian/how-to-work-on-the-docs-theme.md @@ -47,10 +47,12 @@ Налаштуйте freeCodeCamp локально ([див. посібник з локального налаштування](how-to-setup-freecodecamp-locally)). Ми зібрали CLI з інструментами веброзробки, щоб ви могли запустити будь-яку з наведених нижче команд з кореня репозиторію: -#### Обслужити та запустити лише документаційний сайт - ```console pnpm run docs:serve ``` > Сайт документації повинен бути доступним на + +## Запропонуйте запит на злиття (PR) + +Як тільки ви затвердили свої зміни, див. [як відкрити запит на злиття](how-to-open-a-pull-request.md). diff --git a/docs/i18n/ukrainian/moderator-handbook.md b/docs/i18n/ukrainian/moderator-handbook.md index df5bc22c4c9..809c529e35a 100644 --- a/docs/i18n/ukrainian/moderator-handbook.md +++ b/docs/i18n/ukrainian/moderator-handbook.md @@ -39,7 +39,7 @@ Зверніть увагу на позначки `"help wanted"` та `"first timers only"`. Їх потрібно додавати до тредів, які підійдуть потенційним помічникам для створення запиту на злиття. -Використовуйте позначку `"first timers only"` для простих завдань (наприклад, граматичної помилки) та вказуйте додаткову інформацію. Ви можете використовувати [цей шаблон відповіді](moderator-handbook.md#first-timer-only-issues) для сортування. +For triaging a trivial issue such as a typo fix, it is recommended to apply a "first timers only" label along with additional information. You can utilize the [reply template](reply-templates.md#first-timer-only-issues) provided for this purpose. #### Закриті, застарілі, неактивні завдання та запити на злиття @@ -49,7 +49,7 @@ - Якщо помічнику потрібні допомога або час, ми повернемося до нього після отримання відповіді. У будь-якому випадку, модератори повинні розсудливо вирішувати спірні статуси запитів. -> [!TIP] Рекомендуємо використовувати список стандартних [шаблонів відповідей](moderator-handbook.md#reply-templates) під час сортування завдань. +> [!TIP] We recommend you use this list of standard [reply templates](reply-templates.md) while triaging issues. ### Модерація запитів на злиття @@ -63,7 +63,7 @@ Це можна зробити одразу на GitHub та вирішити, чи потрібно їх об’єднувати. Нам потрібно подбати про мільйони людей, які працюють з цим текстом під час навчання на freeCodeCamp. Чи дійсно текст буде зрозумілішим, але не стане більшим? Чи доречні ці зміни? Пам’ятайте, що наша ціль — зробити завдання зрозумілими та короткими. Зайві деталі лише відволікають. Можна додати посилання на ресурс, який стосується теми завдання. - Ви можете закрити недійсний PR та відповісти на нього за допомогою [шаблона](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). Якщо зміни позитивні, залиште коментар «LGTM» (Looks Good To Me). Як тільки запит отримає принаймні два схвалення від модераторів чи розробників (включно з вашим), ви можете об’єднати його. @@ -75,7 +75,7 @@ Деякі помічники можуть спробувати додати додаткові тести, щоб покрити всі можливі випадки. Важливо, аби завдання не виявилось занадто складним. Завдання та їх тести повинні бути максимально простими для розуміння. Окрім алгоритмічних завдань та розділу з інтерв’ю, учні повинні вирішити кожне завдання протягом двох хвилин. - Ви можете закрити недійсний PR та відповісти на нього за допомогою [шаблона](moderator-handbook.md#closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). Якщо зміни позитивні, залиште коментар «LGTM». Як тільки запит отримає принаймні два схвалення від модераторів чи розробників (включно з вашим), ви можете об’єднати його. @@ -142,7 +142,7 @@ Бувають і ситуації, коли помічник додає посилання на свій вебсайт, включно зі створеною ним бібліотекою, або вносить поверхневі зміни, які на користь лише йому. -Такі запити потрібно закрити та відповісти на них [шаблоном](moderator-handbook.md#closing-invalid-pull-requests). +You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests). #### Інші вказівки для модераторів на GitHub @@ -344,238 +344,3 @@ http://suicide.org/international-suicide-hotlines.html
Дякуємо за увагу та допомогу спільноті розробників! - -## Зразки відповідей - -Це зразки відповідей, які можна використовувати під час розгляду PR та їх сортування. - -> Ви можете створити власний список збережених відповідей за допомогою вбудованої функції [збережені відповіді](https://github.com/settings/replies/) на GitHub або використовувати подані нижче. - -### Подяка - -```markdown -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 🎉 -``` - -### Подяка та вітання - -> Подяка та заохочення помічників-початківців. - -```markdown -Hi @username. Congrats on your first pull request (PR)! 🎉 - -Thank you for your contribution to the page! 👍 -We are happy to accept these changes and look forward to future contributions. 📝 -``` - -### Помилка збірки - -```markdown -Hey @username - -We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ - -Once you resolve these issues, we will be able to review your PR and merge it. 😊 - ---- - -Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ -``` - -### Синхронізація розгалуження - -> Якщо PR не відповідає даті гілки `main`. - -````markdown -Hey @username - -We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ - -To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. - -Using the command line, you can do this in three easy steps: - -```bash -git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git - -git fetch upstream - -git pull upstream main -```` - -Якщо ви використовуєте графічний інтерфейс користувача, просто виконайте команду `Add a new remote...` та використайте посилання `git://github.com/freeCodeCamp/freeCodeCamp.git`. - -Як тільки ви синхронізували розгалуження і звірили всі файли, ми зможемо переглянути ваш PR і об’єднати його. 😊 - ---- - -Див. публікацію [«Syncing a fork»](https://help.github.com/articles/syncing-a-fork/) на GitHub для детальнішої інформації щодо того, як зберігати розгалуження актуальним за допомогою віддаленого репозиторію. 🔄 -```` - -### Об’єднання конфліктів - -> Якщо запит має конфлікти об’єднання, які потрібно вирішити.¹ - -```markdown -Hey @username - -We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ - -Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 - ---- - -If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ - -Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 -```` - -¹ Якщо у новачка виникає конфлікт злиття, то спеціалісти розв’яжуть цю проблему замість нього. - -### Дублікат - -> Якщо PR повторюється або є дублікатом. - -```markdown -Hey @username - -This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. - -If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. - -Thanks again! 😊 - ---- - -If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). -``` - -### Закриття недійсних запитів на злиття - -> Якщо PR недійсний. - -```markdown -Hey @username - -Thank you for opening this pull request. - -This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. - -Thank you and happy coding. -``` - -> Якщо PR містить посилання на зовнішні джерела. - -```markdown -Thank you for your pull request. - -We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Додавання коментарів про помилки новачків - -```markdown -Hi there, - -Thanks for creating this pull request. - -Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) - -Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. - -
-Here are some examples (expand) - -1. Do not edit files directly on GitHub – while you can, it's not a good idea. - - Typos and formatting errors can break the tests. - -2. Use the correct way to link issues. - - Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. - -4. Keep mentions and review requests to a minimum. - - We understand you are excited about contributing, and our maintainers will get back to you when they can. - -5. Do not work directly off your `main` branch. - - You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. - -
- -Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. - -We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! - -Happy Contributing. -``` - -### Закриття недійсних завдань - -> Якщо завдання стосується коду користувача. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. - -If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. - -Thank you and happy coding. -``` - -> Якщо завдання повторює вже наявне. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -> Якщо завдання вирішено на проміжній версії. - -```markdown -Thank you for reporting this issue. - -This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. - -If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. -``` - -### Завдання `first timer only` - -> Якщо завдання вважається прийнятним для тих, хто робить внесок до коду вперше. - -```markdown -Thanks for opening this issue. - -This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: - -List of files: - -1. ... -2. ... -3. ... - -Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. - -Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. - -Happy contributing. -``` - -### Запити на призначення - -```md -We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. - -Issues labelled with `help wanted` or `first timers only` are open for contributions. - -Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. -``` diff --git a/docs/i18n/ukrainian/reply-templates.md b/docs/i18n/ukrainian/reply-templates.md new file mode 100644 index 00000000000..ff89332be54 --- /dev/null +++ b/docs/i18n/ukrainian/reply-templates.md @@ -0,0 +1,232 @@ +# Reply Templates + +These are some of the standard reply templates that you may use while reviewing pull requests and triaging issues/pull requests. + +> You can make your own saved replies with GitHub's built-in [saved replies](https://github.com/settings/replies/) feature or use the ones below. + +## Thank You + +```markdown +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 🎉 +``` + +## Thank you and congrats + +> For thanking and encouraging first-time contributors. + +```markdown +Hi @username. Congrats on your first pull request (PR)! 🎉 + +Thank you for your contribution to the page! 👍 +We are happy to accept these changes and look forward to future contributions. 📝 +``` + +## Build Error + +```markdown +Hey @username + +We would love to be able to merge your changes but it looks like there is an error with the CI build. ⚠️ + +Once you resolve these issues, we will be able to review your PR and merge it. 😊 + +--- + +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ +``` + +## Syncing Fork + +> When PR is not up to date with the `main` branch. + +````markdown +Hey @username + +We would love to be able to merge your changes, but it looks like the branch is not up to date. ⚠️ + +To resolve this error, you will have to sync the latest changes from the `main` branch of the `freeCodeCamp/freeCodeCamp` repo. + +Using the command line, you can do this in three easy steps: + +```bash +git remote add upstream git://github.com/freeCodeCamp/freeCodeCamp.git + +git fetch upstream + +git pull upstream main +``` + +If you're using a GUI, you can simply `Add a new remote...` and use the link `git://github.com/freeCodeCamp/freeCodeCamp.git` from above. + +Once you sync your fork and pass the build, we will be able to review your PR and merge it. 😊 + +---==crwdHRulesLBB_2_BBsuleRHdwrc== + +Feel free to reference the ["Syncing a fork"](https://help.github.com/articles/syncing-a-fork/) article on GitHub for more insight on how to keep your fork up-to-date with the upstream repository. 🔄 +```` +## Merge Conflicts +> When PR has merge conflicts that need to be resolved.¹ + +```markdown +Hey @username + +We would love to be able to merge your changes, but it looks like you have some merge conflicts. ⚠️ + +Once you resolve these conflicts, we will be able to review your PR and merge it. 😊 + +--- + +If you're not familiar with the merge conflict process, feel free to look over GitHub's guide on ["Resolving a merge conflict"](https://help.github.com/articles/resolving-a-merge-conflict-on-github/). 🔍️ + +Also, it's good practice on GitHub to write a brief description of your changes when creating a PR. 📝 +``` + +¹ If a first-time-contributor has a merge conflict, maintainers will resolve the conflict for them. + +## Duplicate + +> When PR is repetitive or a duplicate. + +```markdown +Hey @username + +This PR seems to make similar changes as the existing PR <#number>. As such, we are going to close this as a duplicate. + +If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened. + +Thanks again! 😊 + +--- + +If you have any questions, feel free to ask questions on the ["Contributors" category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://discord.gg/PRyKn3Vbay). +``` + +## Closing Invalid Pull Requests + +> When PR is invalid. + +```markdown +Hey @username + +Thank you for opening this pull request. + +This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you. + +Thank you and happy coding. +``` + +> When PR adds links to external resources. + +```markdown +Thank you for your pull request. + +We are closing this pull request. Please suggest links and other details to add the challenge's corresponding guide post through [a forum topic](https://forum.freecodecamp.org/new-topic?category=Contributors&title=&body=**What%20is%20your%20hint%20or%20solution%20suggestion%3F**%0A%0A%0A%0A%0A**Challenge%3A**%0A%0A%0A**Link%20to%20the%20challenge%3A**) instead. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## Adding Comment About Newbie Mistakes + +```markdown +Hi there, + +Thanks for creating this pull request. + +Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :) + +Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things. + +
+Here are some examples (expand) + +1. Do not edit files directly on GitHub – while you can, it's not a good idea. + + Typos and formatting errors can break the tests. + +2. Use the correct way to link issues. + + Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like. + +4. Keep mentions and review requests to a minimum. + + We understand you are excited about contributing, and our maintainers will get back to you when they can. + +5. Do not work directly off your `main` branch. + + You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue. + +
+ +Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you. + +We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions! + +Happy Contributing. +``` + +## Closing Invalid Issues + +> When an issue relates to the camper's code. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the **"Get Help"** button on the challenge on freeCodeCamp and choose the **"Ask for help"** option, which will help you create a question in the right part of the forum. Volunteers on the forum usually respond to questions within a few hours and can help determine if there is an issue with your code or the challenge's tests. + +If the forum members determine there is nothing wrong with your code, you can request this issue to be reopened. + +Thank you and happy coding. +``` + +> When an issue is duplicate of an earlier issue. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that this issue appears to be very similar to issue #XXXXX, so we are closing it as a duplicate. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +> When an issue is fixed in staging. + +```markdown +Thank you for reporting this issue. + +This is a standard message notifying you that the problem you mentioned here is present in production, but that it has already been fixed in staging. This means that the next time we push our staging branch to production, this problem should be fixed. Because of this, we're closing this issue. + +If you think we're wrong in closing this issue, please request for it to be reopened and add further clarification. Thank you and happy coding. +``` + +## `first timer only` Issues + +> When an issue is deemed to be eligible for first-time code contributors. + +```markdown +Thanks for opening this issue. + +This looks like something that can be fixed by "first-time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: + +List of files: + +1. ... +2. ... +3. ... + +Please make sure you read our [guidelines for contributing](https://contribute.freecodecamp.org/#/), we prioritize contributors following the instructions in our guides. Join us in our [chat room](https://discord.gg/PRyKn3Vbay) or our [forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing; our moderators will guide you through this. + +Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. + +Happy contributing. +``` + +## Requests for Assignment + +```md +We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. + +Issues labelled with `help wanted` or `first timers only` are open for contributions. + +Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. +``` \ No newline at end of file diff --git a/docs/i18n/ukrainian/security-hall-of-fame.md b/docs/i18n/ukrainian/security-hall-of-fame.md index 4548f80a7df..be996bec305 100644 --- a/docs/i18n/ukrainian/security-hall-of-fame.md +++ b/docs/i18n/ukrainian/security-hall-of-fame.md @@ -8,4 +8,4 @@ - Пітер Самір https://www.linkedin.com/in/peter-samir/ - Лоуренс Теннант ([@hyperreality](https://github.com/hyperreality)) працює з IncludeSecurity.com — [GHSA-c3r-grh4-27gj](https://github.com/freeCodeCamp/freeCodeCamp/security/advisories/GHSA-cc3r-grh4-27gj) -> ### Дякуємо за ваш вклад :pray: +> **Дякуємо за ваш вклад :pray:**