| Type of contribution | Original Post | Translated Post | Issue | Pull Request |
|---|---|---|---|---|
| Translation | HTML Line Break – How to Break a Line with the HTML <br> Tag | Interruzione di riga in HTML – Come andare a capo con il tag <br> (Published) | HTML Line Break – How to Break a Line with the HTML <br> Tag (Issue #308) | X (Different process for translations) |
| Translation | Git List Branches – How to Show All Remote and Local Branch Names | Elenco dei branch in Git – Come visualizzare tutti i nomi dei branch remoti e locali (Draft) | Git List Branches – How to Show All Remote and Local Branch Names (Issue #290) | X (Different process for translations) |
| Post-editing | How to Work with SQLite in Python – A Handbook for Beginners | Come Lavorare con SQLite in Python – Un Manuale per Principianti | How to Work with SQLite in Python – A Handbook for Beginners (Issue #532) | Come Lavorare con SQLite in Python – Un Manuale per Principianti (Issue #631) |
Joining freeCodeCamp
This form (click here to view) is designed for individuals interested in volunteering to help translate freeCodeCamp’s educational content into various languages.
Once submitted, this will be the message displayed.
- Articles chosen why?
This is the read.me file containing all the information on different types of non-coding contributions for freecodecamp (click here to view).
Two methods for our localisation
We are currently localising handbooks and articles in two ways:
- (A) Traditional translation process: As a collaborator, you can pick an article, translate it, and submit it for review.
- (B) Post-editing process: As a collaborator, you can pick an AI-translated article to post-edit, ensuring it’s grammatically correct and fixing any possible AI errors, such as untranslated words or paragraphs, missing content, or incorrectly wrapped paragraphs in backticks.
In both localisation methods, the collaborator’s meticulous revision is crucial, especially on AI-translated handbooks and articles, since AI translations are known to make mistakes or miss certain details.
Please take a look and decide which of these two methods you would like to collaborate on.
Choosing an article
In order to contribute to the Italian translation of freeCodeCamp articles and handbooks, I used their GitHub project board (click here to view), which is organised by topic and translation progress. The topic selection was relevant to the content of the course I am taking, which is why I chose to contribute to freeCodeCamp in the first place.
The board includes separate columns for different types of tasks. I focused on the "To Translate" column for articles that needed to be fully translated from English to Italian, and the "To Post-edit" column for articles that had already been machine-translated and required human review and editing. Articles in the post-editing column are usually labelled with "auto" to indicate that they were generated using AI.
Once I found an article I wanted to work on, I opened its GitHub issue and left a comment with /translate. This command automatically assigned the article to me and moved it to the "In Translation" column, so others would know it was being worked on.
After that, I translated the article from English to Italian. When I finished, I followed the instructions in the issue to submit my work and get it reviewed.
Translation contributions
Once I found an article I wanted to work on, I opened its GitHub issue and left a comment with /translate. This command automatically assigned the article to me and moved it to the “In Translation” column, so other contributors would know it was being worked on.
Translated article for HTML Line Break – How to Break a Line with the HTML <br> Tag in Ghost.
Translated article for Git List Branches – How to Show All Remote and Local Branch Names in Ghost.
For Italian translations,
Post-Editing contributions
FreeCodeCamp’s Issue page for How to work with SQLite in Python article [1].
This process helped me contribute to making freeCodeCamp’s content available in other languages.
Published translations
“HTML Line Break” got published on Monday, 12th of May.
My translation of “HTML Line Break – How to Break a Line with the HTML <br> Tag” was officially published on Monday, May 12th.
After the article went live (click here to view it), the corresponding GitHub issue was closed, and the task was moved to the “Published” column on the freeCodeCamp GitHub Project Board, marking it as complete.
Two of my other contributions are still in the review phase and are waiting to be approved before being published.
