Translation: Tagalog (Filipino) #2336

rollybueno · 2025-07-07T13:37:47Z

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

Local preview

cd packages/docs/site
npm run dev:docs -- --locale tl

Results:

fellyph · 2025-07-07T15:11:53Z

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

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

fellyph · 2025-07-07T14:38:14Z

packages/docs/site/i18n/tl/docusaurus-theme-classic/footer.json

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


Those messages you can add Filipino text, as a value

packages/docs/site/i18n/tl/docusaurus-theme-classic/navbar.json

fellyph · 2025-07-07T15:14:46Z

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current.json

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


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

Gotcha - thanks!

fellyph · 2025-07-07T15:18:40Z

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

rollybueno · 2025-07-09T12:49:55Z

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 · 2025-07-09T13:00:40Z

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 · 2025-07-09T16:52:34Z

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 · 2025-07-10T13:42:27Z

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.

rollybueno · 2025-07-12T10:02:56Z

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.

rollybueno · 2025-07-12T10:50:22Z

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.

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/blueprints/01-index.md

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/about/build.md

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/about/index.md

.../site/i18n/tl/docusaurus-plugin-content-docs/current/main/guides/wordpress-native-ios-app.md

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/intro.md

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/quick-start-guide.md

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/resources.md

packages/docs/site/i18n/tl/docusaurus-plugin-content-docs/current/main/web-instance.md

…ress#2336

rollybueno · 2025-07-26T13:24:39Z

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

rollybueno · 2025-07-26T13:27:43Z

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!

jhimross · 2025-07-26T14:05:08Z

@rollybueno All good! cc: @fellyph

rollybueno · 2025-08-01T01:57:35Z

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:

Translations: Clean up version from PR #2336 #2448 is ready for merging
Once it merged, I'll close this PR
Then we can use [Translation] Tagalog(Filipino) translation progress tracker #2353 for tracking the next content translations.
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

## 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.

rollybueno · 2025-08-01T09:17:52Z

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 added 2 commits July 7, 2025 21:01

Translation: Tagalog (Filipino)

dcb56fb

Fix: Extra opening bracket that breaks the INFO section

68f8833

fellyph reviewed Jul 7, 2025

View reviewed changes

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

Fix: Add Blueprints and Developers files for translation

66efaad

rollybueno mentioned this pull request Jul 12, 2025

[Translation] Tagalog(Filipino) translation progress tracker #2353

Open

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

fellyph added 2 commits July 14, 2025 10:38

Merge branch 'trunk' into translations/tagalog

2b8c471

Merge branch 'trunk' into translations/tagalog

6f2df90

jhimross reviewed Jul 23, 2025

View reviewed changes

Merge branch 'trunk' into translations/tagalog

e9e3200

fellyph mentioned this pull request Jul 25, 2025

Adding approved Filipino translation for Contribution and Intro #2430

Closed

Translations: Update strings based on feedback

ed4808b

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

Translations: Add recent approved Tagalog translated files from WordP…

f7a3d0e

…ress#2336

Merge branch 'trunk' into translations/tagalog

4f35bc1

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

Translations: Clean up version from PR WordPress#2336

f4c1612

rollybueno mentioned this pull request Aug 1, 2025

Translations: Clean up version from PR #2336 #2448

Merged

rollybueno closed this Aug 1, 2025

Translation: Tagalog (Filipino) #2336

Translation: Tagalog (Filipino) #2336

Uh oh!

Conversation

rollybueno commented Jul 7, 2025

Motivation for the change, related issues

Implementation details

Note:

Testing Instructions

Uh oh!

fellyph commented Jul 7, 2025

Uh oh!

fellyph left a comment

Choose a reason for hiding this comment

Uh oh!

fellyph Jul 7, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

fellyph Jul 7, 2025

Choose a reason for hiding this comment

Uh oh!

rollybueno Jul 9, 2025

Choose a reason for hiding this comment

Uh oh!

fellyph commented Jul 7, 2025

Uh oh!

rollybueno commented Jul 9, 2025

Uh oh!

rollybueno commented Jul 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

fellyph commented Jul 9, 2025

Uh oh!

fellyph commented Jul 10, 2025

Uh oh!

rollybueno commented Jul 12, 2025

Uh oh!

rollybueno commented Jul 12, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rollybueno commented Jul 26, 2025

Uh oh!

rollybueno commented Jul 26, 2025

Uh oh!

jhimross commented Jul 26, 2025

Uh oh!

rollybueno commented Aug 1, 2025

Uh oh!

rollybueno commented Aug 1, 2025

Uh oh!

Uh oh!

rollybueno commented Jul 9, 2025 •

edited

Loading