Skip to content

Conversation

@marioguzzzman
Copy link

@marioguzzzman marioguzzzman commented Dec 1, 2025

Resolves #8228

Changes

This PR updates the Spanish steward guidelines to align with p5.js 2.0, removing obsolete references to Grunt, the task automation system used in p5.js 1.x, and replaces them with information about current version 2.0 tools:

  • npm scripts
  • ESLint
  • Vitest

Bilingual Educational Approach

I am proposing a bilingual educational approach to translation by including English technical terms in parentheses the first time they appear (e.g., "verificación de estilo (linting)", "pruebas unitarias (unit tests)", "scripts de compilación (build scripts)"). My thinking is that this strategy is important to build a shared technical vocabulary that helps both Spanish-speaking and English-speaking readers so that we/they can:

  1. Participate in international discussions about p5.js
  2. Navigate technical documentation in both languages
  3. Understand common technical terms in software development
  4. English speakers can also relate to how terms are expressed in other languages

I think this makes the documentation useful as both a learning resource and a reference.

Translation Decisions

  • Used educational parentheticals consistently for technical terms throughout the Grunt-removing update

Original issue: #7871

PR Checklist

  • npm run lint passes - (N/A- Documentation-only PR, no code changes)
  • [Inline reference] is included / updated - (Updating steward guidelines, not API reference)
  • [Unit tests] are included / updated - ( N/A - Documentation update, no code changes)

Note: This is a documentation-only PR updating Spanish translation. No code changes require linting or testing.

…ces)

Remove Grunt references, update to npm scripts, ESLint, and Vitest
@welcome
Copy link

welcome bot commented Dec 1, 2025

🎉 Thanks for opening this pull request! For guidance on contributing, check out our contributor guidelines and other resources for contributors!
🤔 Please ensure that your PR links to an issue, which has been approved for work by a maintainer; otherwise, there might already be someone working on it, or still ongoing discussion about implementation. You are welcome to join the discussion in an Issue if you're not sure!
🌸 Once your PR is merged, be sure to add yourself to the list of contributors on the readme page !

Thank You!

@marioguzzzman
Copy link
Author

cc: @perminder-17 @ksen0

@ksen0
Copy link
Member

ksen0 commented Dec 4, 2025

Thanks so much @marioguzzzman , just checked this ✔️

@ksen0 ksen0 merged commit 43fd2c0 into processing:dev-2.0 Dec 4, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants