FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Translation: Tagalog (Filipino) by rollybueno · Pull Request #2336 · WordPress/wordpress-playground · GitHub

Translation: Tagalog (Filipino) - #2336

Closed
rollybueno wants to merge 8 commits into
WordPress:trunkfrom
rollybueno:translations/tagalog
Closed

Translation: Tagalog (Filipino)#2336
rollybueno wants to merge 8 commits into
WordPress:trunkfrom
rollybueno:translations/tagalog

Conversation

Copy link
Copy Markdown
Member

Motivation for the change, related issues

  • I’ve translated the entire Playground documentation into Tagalog to broaden accessibility for Filipino-speaking users.
  • This closes the gap for Tagalog localization and makes it easier for non-English–speakers to learn and contribute.
  • No existing issue tracked; this is a new effort to provide full Tagalog versions alongside the English docs.

Implementation details

  • Created Tagalog variants of every .md file under packages/docs/site/docs.
  • Preserved all frontmatter, HTML comments, code examples, info/tip blocks, and links.
  • Updated docusaurs.config.js to register tl, which is accessible as /tl/.
  • All new files are in packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/....

Note:

  • I have excluded the Changelog page since it's not needed, so it will be loaded as EN

Testing Instructions

  1. Local preview
    cd packages/docs/site
    npm run dev:docs -- --locale tl
    

Results:



fellyph commented Jul 7, 2025

Copy link
Copy Markdown
Collaborator

Wow! That is amazing @rollybueno. Thank you so much for your pull request!

Regarding the images, I would recommend that you maintain consistency when changing them in the English version, instead of creating a new version.

About the translations to speed up the reviewing process, it is good to have the original version as a comment. It is not a blocker, but it will help the review process(I will add it to the documentation).

fellyph left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

A few changes suggested, I will look for a reviewer to check the translation

@@ -0,0 +1,42 @@
{
"link.title.Docs": {
"message": "Docs",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Those messages you can add Filipino text, as a value

@@ -0,0 +1,54 @@
{
"version.label": {
"message": "Next",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

The message content can be translated into Filipino in this file.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Gotcha - thanks!

fellyph commented Jul 7, 2025

Copy link
Copy Markdown
Collaborator

@rollybueno, if you don't mind, I can create an issue to track the Filipino translations, similar to this one for Japanese.

fellyph added [Type] Documentation Improvements or additions to documentation [Aspect] Internationalization (i18n) labels Jul 7, 2025

Copy link
Copy Markdown
Member Author

Hey @fellyph - sure no problem and sorry I have to jump into translating right away before checking the issue. I think I did that because there are no mention about the process in the existing EN docs(or maybe I just completely missed it).

rollybueno commented Jul 9, 2025
edited
Loading

Copy link
Copy Markdown
Member Author

Regarding the images, I would recommend that you maintain consistency when changing them in the English version, instead of creating a new version.

These images are auto cloned when running npm run write-translations -- --locale tl right after setting up the docusaurus.config.js.. so no new version was actually created.

fellyph commented Jul 9, 2025

Copy link
Copy Markdown
Collaborator

These images are auto cloned when running npm run write-translations -- --locale tl right after setting up the docusaurus.config.js.. so no new version was actually created.

I will update it, it is not necessary to clone the images, because I reused them on the Brazilian translation.

https://wordpress.github.io/wordpress-playground/pt-br/quick-start-guide

fellyph commented Jul 10, 2025

Copy link
Copy Markdown
Collaborator

Hi @rollybueno, thanks for the latest changes. I saw some pages in English inside the Filipino folder. In this case, if you haven't translated yet, you don't need to upload a file. Docusaurus will figure it out by itself and send an English version as default.

Copy link
Copy Markdown
Member Author

I see, thanks @fellyph. I copied that from this folder - https://github.com/WordPress/wordpress-playground/tree/trunk/packages/docs/site/docs as I'm afraid, re-runing the script will override my existing tl translated files..

I'll find reviewer that can help us moving forward here once I'm done with translating the blueprints and developers.

Copy link
Copy Markdown
Member Author

I'll be following how shimotmk did on his work in Japanese translation e.g. #2202, it's way easier for reviewer to open per PR and it's easy for us to track changes as well.

Mentioned my concerns on #2353 (comment)

Hey @fellyph - I'll removing those newly added EN files for Blueprints and Developers. I'll do separate PR per article once I have reviewer here and start working on those sections once tl will be partially merged.

rollybueno changed the title Translation: Tagalog (Filipino) Translation: Tagalog (Filipino) Progress Tracker Jul 12, 2025
rollybueno changed the title Translation: Tagalog (Filipino) Progress Tracker Translation: Tagalog (Filipino) Jul 12, 2025
rollybueno added a commit to rollybueno/wordpress-playground that referenced this pull request Jul 26, 2025

Copy link
Copy Markdown
Member Author

Pushed an update to the feedbacks. I believe we should be ready here

Copy link
Copy Markdown
Member Author

Hey @jhimross - thanks for your feedback. I have updated them. If there's nothing else to review, can you give an approval to this PR so that we can merge the main docs?

Many thanks!

Copy link
Copy Markdown

@rollybueno All good! cc: @fellyph

rollybueno added a commit to rollybueno/wordpress-playground that referenced this pull request Aug 1, 2025

Copy link
Copy Markdown
Member Author

Hey @fellyph, as what we have talked on Slack - I have created a simplified and cleaner version of approved translation pages in #2448.

Up next:

  1. Translations: Clean up version from PR #2336 #2448 is ready for merging
  2. Once it merged, I'll close this PR
  3. Then we can use [Translation] Tagalog(Filipino) translation progress tracker #2353 for tracking the next content translations.
  4. All Tagalog translations on Blueprints and Developer pages will be broken down into smaller translations PR so that we can easily review it.

I'll close this PR once you have merged #2448

fellyph pushed a commit that referenced this pull request Aug 1, 2025
## Motivation for the change, related issues
Related to #2336,
this PR is a simplified version of Tagalog translation, particular on
Documentation section. The rest of the Tagalog translations will be
broken down on few pages per PR so that it can be easily review.
<img width="2167" height="1162" alt="2025-08-01_09-47"
src="https://github.com/user-attachments/assets/c34b6a41-c852-4250-a4d9-7b1fd07d7075"
/>

The translations in this PR has been reviewed and approved by secondary
Tagalog speaker as per
#2336 (comment),
which makes this PR a ready for merging.

Copy link
Copy Markdown
Member Author

Documentation page translation is now on trunk as per #2448

Moving next on Blueprints with smaller per PR. Many thanks for the help @jhimross & @fellyph 🙌

Closing this one 🚪

rollybueno closed this Aug 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Aspect] Internationalization (i18n) [Type] Documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants


Back | FazBrowse Home | New Git URL