processing / processing/p5.js-website

🌍 Update translations for p5.nvim.yaml

Open
#1,335 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help Wanted lang-es lang-hi lang-ko needs translation
Dominant language
MDX
Stars
96
Forks
322
Avg merge
5d 22h
Merged PRs (30d)
8

Description

🌍 Translation Update Needed

File: src/content/libraries/en/p5.nvim.yaml
Branch: main

📅 Timeline
  • Latest English update: 4/8/2026 by Dean Tarisai
❌ Missing Translations
  • Spanish (Español): Translation file does not exist (cc @marioguzzzman)

    • Expected location: src/content/libraries/es/p5.nvim.yaml
  • Hindi (हिन्दी): Translation file does not exist (cc @Divyansh013, @takshittt)

    • Expected location: src/content/libraries/hi/p5.nvim.yaml
  • Korean (한국어): Translation file does not exist (cc @hana-cho)

    • Expected location: src/content/libraries/ko/p5.nvim.yaml
  • Chinese Simplified (简体中文): Translation file does not exist (cc @limzykenneth, @lirenjie95) This one has been added, thanks!

    • Expected location: src/content/libraries/zh-Hans/p5.nvim.yaml
🔗 Quick Links
✅ Action Checklist

For translators / contributors:

  • Review the recent English file changes and the current translations
  • Confirm if translation already reflects the update — close the issue if so
  • Update the translation files accordingly
  • Maintain structure, code blocks, and formatting
  • Ensure translation is accurate and culturally appropriate
📝 Summary of English File Changes

Last commit: Add p5.nvim libraries

Change Type: English file was updated. Spanish (Español), Hindi (हिन्दी), Korean (한국어), Chinese Simplified (简体中文) translations are missing.


ℹ️ Need help? See our Contributor Guidelines

🤖 This issue was auto-generated by the p5.js Translation Tracker

Contributor guide

No contributing guide indexed for this repository

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 src/content/libraries/en/p5.nvim.yaml and compare it with the existing library translation structure. Add or update src/content/libraries/es/p5.nvim.yaml, src/content/libraries/hi/p5.nvim.yaml, and src/content/libraries/ko/p5.nvim.yaml while preserving structure, code blocks, and formatting. Done means the three translations accurately reflect the current English file.

Written by the indexing model from the issue text.

Assessment

Domain
localization
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.