[GSoC 2025] Friendly p5.js Reference Translation Tasks

Hi everyone! 👋

This issue tracks the deliverables for my Google Summer of Code 2025 project under the Processing Foundation: "Friendly p5.js Reference Translation Tasks." The goal is to build GitHub Actions and contributor workflows to help translation stewards and volunteers keep the p5.js reference up to date across languages.

I’ll be checking off these items as the project progresses. Feedback is always welcome!

Core GitHub Actions & Automation

• GitHub Action to detect changes in English reference pages (MDX files).
• Automatic flagging of outdated translations by comparing update timestamps or metadata.
• GitHub Issues created or updated for each affected translation (per language).
• Weekly scheduled Action to summarize all outdated or missing translation files.
• Add needsUpdate: true frontmatter in outdated translation MDX files via PRs.

Missing Translation Detection

• Detect English reference files with no translated counterpart in each supported language.
• Automatically open Issues or PRs to notify language teams of missing translation files.
• (Optional stretch) Create stub MDX files for missing translations and open PRs.

Contributor Communication Workflow

• Tag relevant translation maintainers (via GitHub handles or teams) when updates are needed.
• Maintain a translation-teams.yml or similar config to manage language <-> contributor mapping.
• Document how to respond to flagged translation updates (contributor guide section).

Astro Site Integration

• If needsUpdate flag is used, add a visible banner to the reference page via Astro templates.
• Ensure that all automation respects Astro’s content schema and doesn’t break the build.

Documentation

• Write a “Translation Maintenance Guide” explaining all new workflows.
• Add setup instructions for maintainers and new stewards (how to run checks, add languages, etc.).
• Provide dry-run logs or test cases showing how Actions behave.

Let’s make p5.js documentation even more accessible and translator-friendly this summer! 🚀
Tagging @stalgiag and @ksen0 for visibility.

Start by mapping the proposed GitHub Actions against the English and translated reference MDX files, then review the planned translation-teams.yml configuration and Astro template integration. Use the checklist to define the workflow, missing-file detection, contributor guidance, and documentation deliverables; the work is done when the listed automation, integration, and maintenance materials are complete and demonstrated.