I was just testing random things - #9137
Conversation
Help new translators find needs-translation issues and stubs, edit MDX, preview with npm run dev, and open a PR, with screenshots and a link to localization.md for deeper detail. Co-authored-by: Cursor <cursoragent@cursor.com>
Continuous ReleaseCDN linkPublished PackagesCommit hash: c8838f7 Previous deploymentsThis is an automated message. |
aashishpanthi
changed the title
There was a problem hiding this comment.
🟡 Changes recommended
The new guide’s local preview and PR targeting instructions should be aligned with the contributor docs’ existing assumption that p5.js-website work is done against the 2.0 branch to prevent contributors from using the wrong branch.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds a new beginner focused contributor document that guides translators through finding website translation work in p5.js-website, editing MDX stubs, optionally previewing locally, and opening a PR, then links that guide from the contributor docs README so it can surface on p5js.org/contribute.
Changes:
- Added
contributor_docs/translating_the_website.mdwith step by step translation workflow, Mermaid overview, and screenshots. - Linked the new guide from
contributor_docs/README.md. - Added an SVG screenshot asset (
translation-needsTranslation-line.svg) to support the guide.
File summaries
| File | Description |
|---|---|
| contributor_docs/translating_the_website.md | New beginner guide for translating p5.js website content in the p5.js-website repo. |
| contributor_docs/README.md | Adds an entry linking to the new translation guide. |
| contributor_docs/images/translation-needsTranslation-line.svg | New screenshot asset referenced by the guide. |
Review details
Suppressed comments (1)
contributor_docs/translating_the_website.md:78
- Step 5 says to open a PR into the website’s “default contribution branch”, but elsewhere in these contributor docs the website branch is explicitly
2.0. Being explicit here can prevent translators from accidentally targeting the wrong base branch.
2. Open a pull request into the website’s default contribution branch (follow whatever the PR template or maintainers ask for).
- Files reviewed: 2/6 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
as part of my lecutre of AI agents for one of my modules, I was trying to run the AI agent (supposed to be in controlled environment) to see how well it does the job, somehow I gave it more premission that needed.
|
Trying out random things, somehow landed here