Translation: Tagalog (Filipino)

[rollybueno]

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]

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]

Those messages you can add Filipino text, as a value

[fellyph]

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

[rollybueno]

Gotcha - thanks!

[fellyph]

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

[rollybueno]

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]

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]

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]

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]

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]

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.