processing / processing/p5.js-web-editor

Adding Multilingual README for the repo

Open
#3,074 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Documentation Area: Translation Needs Discussion
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

Increasing Access

As our project gains traction, it's becoming increasingly important to ensure accessibility and inclusivity for contributors from diverse linguistic backgrounds. One of the key steps towards achieving this goal is by adding multilingual support to our README.md file. This will not only make it easier for non-English speakers to understand the project's objectives and guidelines but also encourage a broader community engagement.

Feature request details

Implementation Steps:

  • Identify Target Languages: Determine which languages are most relevant based on the demographics of potential contributors and the project's global reach.
  • Establish Translation Workflow: Define the process for translating, reviewing, and updating multilingual README content. Consider using translation management tools or platforms to streamline collaboration.
  • Engage Community: Reach out to existing contributors and community members to solicit assistance with translations. Encourage participation from native speakers or proficient translators for each target language.
  • Integrate Translations: Incorporate translated content into the README.md file, ensuring clear segmentation and visibility for each language section.
  • Regular Maintenance: Implement a system for periodically reviewing and updating translations to reflect changes in the primary README.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing README.md and the issue's proposed steps. The target languages, translation workflow, community ownership, and maintenance process are not defined; done would require those decisions plus integrated translated README sections and a way to keep them current.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, internationalization, localization
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.