[Translation] Tagalog(Filipino) translation progress tracker

[rollybueno]

Introduction

WordPress core currently lacks official Tagalog translations, which limits accessibility for some Filipino-speaking users(there are 100 milion +). This ticket proposes to initiate the Tagalog localization effort and integrate a Tagalog locale into the core translation set. There's already on-going translations effort for the whole documentation in single PR, which ou can visit on: https://github.com/WordPress/wordpress-playground/pull/2336.

Purpose

The purpose of this issue is to track and increase visibility into our progress on Tagalog translations.

Section tracking

We already done with the main directory which focuses on the Documenatation , while we have on-going work with Blueprints and Developers. Below are the task list of each topics that are done and in-progress.

Translations Completed:

Documentation

Documentation:

Translated	Reviewed	Title
✅	✅	WordPress Playground Docs
✅	✅	Start using WordPress Playground in 5 minutes
✅	✅	WordPress Playground web instance
✅	✅	Links and Resources

About Playground:

Translated	Reviewed	Title
✅	✅	About WordPress Playground
✅	✅	Build
✅	✅	Test
✅	✅	Launch

Guides:

Translated	Reviewed	Title
✅	✅	Guides
✅	✅	Playground in native iOS apps
✅	✅	Playground for Plugin Developers
✅	✅	Playground for Theme Developers
✅	✅	Providing content for your demo with Playground

Contributing:

Translated	Reviewed	Title
✅	✅	Contributing to WP Playground project
✅	✅	Code contributions
✅	✅	Coding principles
✅	✅	WordCamp Contributor Day
✅	✅	Documentation contributions
✅	✅	Contributions to translations

Blueprints:

Translated	Reviewed	Title
✅	X	Blueprints
✅	X	Getting started
✅	X	Tutorial
✅	X	Blueprint data format
✅	X	Using Blueprints
X	X	Steps
X	X	Blueprint Bundles
X	X	Examples
X	X	Troubleshoot and debut

Tutorial:

Translated	Reviewed	Title
✅	X	What are Blueprints
✅	X	How to run Blueprints
✅	X	Build your first Blueprint

Steps:

Translated	Reviewed	Title
X	X	Resources References
✅	X	Shorthands
✅	X	API Consistency

[rollybueno]

I noticed it's horrible to include links to the individual title above in the same PR. It's eating majority of my desktop resources when opening those and my Chrome hangs. This will be a problem for reviewers.

For the rest of the articles that are yet translated, maybe it's best if I should follow on how shimotmk did on https://github.com/WordPress/wordpress-playground/issues/2202, by separating each article as PR, which is way easier for reviewer to do their job.

[rollybueno]

Hey @SHINOB1NINJA - you helped me reviewing the lessons translations in https://github.com/WordPress/Learn/, would you mind to review these as well?

[fellyph]

Hi @rollybueno, thanks for creating the issue, and great work with the translations! To relate single files is hard; having a small PR with a group of translations per section can facilitate the linking process.

I would suggest that, on this issue, to have a global overview, we can also include the files that have not been translated yet.

Having a single issue to follow up on the translation process for Filipino can be helpful, as it allows other contributors to communicate around it. For example, in the Brazilian translation, I have included all files and tagged the PRs that require reviews #2306.

I suggest small groups of translations per PR, which can attract more reviews and require less time to approve.

[rollybueno]

Thanks for the feedback @fellyph, I'll update this issue to include all pages for global overview.