(What are the source code management and version control
platforms used in the community of the project you are contributing to? How do those fit and
accommodate your project’s workflow?)
In the community I’ve been contributing to, the workflow involves a few interconnected platforms: first, new contributors are asked to fill out an intake form or survey, after which they are added to a platform called ghost which is used to translate articles as well as the GitHub repository, I also joined the Discord server for ongoing communication and coordination.
Figure 1. Google forms completed
Figure 2. Emails sent to me by translations team leader.
Figure 3. Claiming article though ‘issues’ on Github
Figure 4. Article #596 being assigned
Figure 5. Article ‘Build a Memory Game in React’ In translation
Figure 6. Joining and engaging with the Discord chat
Previously, the community also used a third-party platform called Crowdin for managing translations in a more structured way. However, access to Crowdin is no longer available, and the workflow has since shifted.
Figure 7. Confirmation email Crowdin freeCodeCamp organisation
Figure 8. Spanish translation contribution through Crowdin
Currently, the main contribution process takes place through a publishing platform called Ghost, where team members can select articles to translate. Although the project has a GitHub repository for managing version control and tracking contributions, the actual translation work is done directly within the Ghost platform. This hybrid setup is somewhat unique, GitHub is used more as a record-keeping or syncing tool, while Ghost serves as the central workspace.
Figure 9. freeCodeCamp Ghost platform
Figure 10. Ghost platform staff user, contributor
https://www.freecodecamp.org/news/build-a-memory-game-in-react – original article
https://www.freecodecamp.org/espanol/news/p/b8093cf3-6991-4d57-8fdf-b93e827610bf – translated article
Figure 11. Waiting to be reviewed
Figure 12. Communicating with the team
Figure 12 shows a message I sent to the team (in Spanish) asking about the status of an article I had completed. I inquired whether I needed to submit it to someone or if there were any next steps to follow. The response I received was that “there is no other step to take,” which left the process somewhat unclear. Despite following up again later, I did not receive any further communication from the team.
This experience highlights a gap in the project’s workflow, particularly around contributor feedback and follow-through. While the initial onboarding was welcoming, the lack of consistent communication made it difficult to understand whether my work would be reviewed, published, or acknowledged. It’s a reminder of how crucial clear, ongoing support is in maintaining contributor motivation and trust.
While I did complete a translation, my contribution was not published, which highlighted one of the challenges of this setup, there isn’t always going to be an active member after submitting work to review it and publish your work. Still, the structure encourages multilingual participation and has the potential to grow with better contributor visibility and workflow transparency.
List of figures
Figure 1 Bueno, I (2025) Google forms completed [Screenshot]
Figure 2 Bueno, I (2025) Emails sent to me by translations team leader [Screenshot]
Figure 3 Bueno, I (2025) Claiming article though ‘issues’ on Github [Screenshot]
Figure 4 Bueno, I (2025) Article #596 being assigned. [Screenshot]
Figure 5 Bueno, I (2025) Article ‘Build a Memory Game in React’ In translation [Screenshot]
Figure 6 Bueno, I (2025) Joining and engaging with the Discord chat [Screenshot]
Figure 7 Bueno, I (2025) Confirmation email Crowdin freeCodeCamp organisation [Screenshot]
Figure 8 Bueno, I (2025) Spanish translation contribution through Crowdin [Screenshot]
Figure 9 Bueno, I (2025) freeCodeCamp Ghost platform [Screenshot]
Figure 10 Bueno, I (2025) Ghost platform staff user, contributor [Screenshot]
Figure 11 Bueno, I (2025) Waiting to be reviewed [Screenshot]
Figure 12 Bueno, I (2025) Communicating with the team [Screenshot]
Leave a Reply