Grants:Programs/Wikimedia Community Fund/General Support Fund/Wiki Advocates Philippines 2026-2027
This is an automatically generated Meta-Wiki page. The page was copied from Fluxx, the web service of Wikimedia Foundation Funds, where the user has submitted their application. Please do not make any changes to this page because all changes will be removed after the next update. Use the discussion page for your feedback. The page was created by CR-FluxxBot.
Applicant information
[edit]- Organization name or Wikimedia Username for individuals. (required)
- Wiki Advocates Philippines User Group
- Do you have any approved General Support Fund requests? (required)
- Yes, I have already applied and received a General Support Fund
- You are applying as a(n). (required)
- Wikimedia Affiliate (chapter, thematic org., or user group)
- Are your group or organization legally registered in your country? (required)
- Yes
- Do you have a fiscal sponsor?
- Yes
- Fiscal organization name.
- Kiwix
- Please provide links to the following documents if they are available
These documentation can be provided in your local language(s), no translations required.
- Organizational website
- Detailed financial reporting and/or audits
- Documentation of the governance structure, board list, governance processes
- Documentation of the general assembly decision on your plan
- Organizational website: https://wikiadvocatesph.org/
- Governance structure: https://meta.wikimedia.org/wiki/WikiAdvocates/Member
- Financial Report 2024-2025
- Link to reports: https://commons.wikimedia.org/wiki/Category:WAP_UG_Report
Multi-year Impact Comparison Report

Main proposal
[edit]- 1. Please state the title of your proposal. This will also be a title for the Meta-Wiki page. (required)
- Wiki Advocates Philippines 2026-2027
- 2. Do you want to apply for the multi-year base funding for 3 years? (required) (only for returning applicants)
- No
- 2.1. Provide a brief overview of Year 2 and Year 3 of the proposed plan and how this relates to the current proposal and your strategic plan? (required)
N/A
- 3. Proposed start date. (required)
- 2026-07-01
- 4. Proposed end date. (required)
- 2027-06-30
- 5. Does your organization or group have an Affiliate or Organizational Annual Plan that can help us understand your proposal? If yes, please provide it. (required)
- Yes
- Link to 5-year Strategic Plan Roadmap: https://docs.google.com/document/d/14zI_cZVSFwYieM0TYJSVDqd1qjQ1SA6SYtAabBrHsq8/edit?tab=t.0
- 6. Does your affiliate, organization or group have a Strategic Plan that can help us understand your proposal? If yes, please provide it. (required)
- Yes
- https://docs.google.com/document/d/1tW2NtIT2NQpeiHWI5plGcxD53DBCermdjyvfhQkJNgg/edit?tab=t.0
- 7. Where will this proposal be implemented? (required)
- Philippines
- 8. What are your programs, approaches, and strategies? What are the challenges that you are trying to address and how will your strategies support you in addressing these challenges? (required)
Programs and Approaches
Our approach is evolving from partner-dependent projects to tool-grounded initiatives. While we continue our core work in Wikipedia, Wiktionary, and Wikiquote, our primary strategy now centers on building and deploying a suite of backend and frontend tools that stabilize our mission.
1. Technical Infrastructure as a Foundation: We are focusing on four key tools:
a. WikiDunong Kiosks: Our primary offline delivery system for remote schools.
b. philheritage-archive.toolforge.org: A centralized hub for Philippine heritage data.
c. suyat.toolforge.org: A specialized tool for indigenous script (Baybayin) preservation.
d. Wikimedia Commons Explorer: A tool to audit and visualize our media contributions. This tool is a hands-on training guide on proper media utilization and attribution.
2. Targeted Campaigns: Instead of broad, untargeted editing, we use these tools to identify critical gaps. For example, the Commons Explorer and Philippine Heritage Data Compass allow us to pinpoint heritage items lacking deep metadata or high-quality images, making our volunteer edit-a-thons more efficient and impact-driven.
3. The Hatch-A-Wikimedian & Community Learning Hub: We continue to use our physical space as a community learning space where volunteers transition from basic editors to leaders, maintaining the hub while mastering these new technical tools.
Challenges Addressed
- Climate & Partnership Fragility: As seen during the catastrophic typhoons of late (in 2024, and 2025), partner schools often have to pivot to disaster recovery, stalling our projects. Our new strategy addresses this by grounding the goals in the tools, not the partners. If one school or LGU is unable to fulfill their commitment due to unforeseen events, the modular nature of the WikiDunong Kiosks and Toolforge apps allows us to pivot to a different partner or region immediately without redesigning the project.
- Volunteer Retention & Economic Shifts: High-intensity volunteerism is difficult to maintain during economic hardship. By providing tools that make editing "targeted," we reduce volunteer fatigue. Editors see the immediate impact of their work (e.g., filling a specific metadata gap identified by the tool).
- Limited Staff Capacity: With only three paid staff handling everything from clerical work to project management, we are using technical automation to reduce the "administrative load." These tools help automate data gathering for reports, allowing staff to focus on high-level growth.
How Strategies Support Challenges
Our strategy creates a security layer for our mission. By investing in the WikiDunong Kiosks and Toolforge ecosystem, we ensure that:
- Sustainability is Built-In: The tools serve as permanent repositories of our work. Even if a volunteer leaves or a physical session is canceled due to weather, the digital infrastructure remains active and ready for the next cohort.
- Operational Agility: We are no longer "stuck" when a partner stalls. Because our work is focused on the tool's data needs (e.g., "The PhilHeritage tool says we need images for X town"), we can work with any local group in that town to fulfill the requirement, making our partnership model much more flexible and resilient.
- Evidence-Based Growth: We now use the data from our kiosks (clicks per device/daily stats) and Toolforge apps to justify our impact to future donors and partners with hard evidence, moving beyond anecdotal success.
- 9. What categories are your main programs and related activities under? Please select all that apply. (required)
| Category | Yes/No |
|---|---|
| Education | Yes |
| Culture, heritage or GLAM | Yes |
| Gender and diversity | Yes |
| Community support and engagement | Yes |
| Participation in campaigns and contests | Yes |
| Public policy advocacy | No |
| Technology (software development) | Yes |
| Other | No |
Education
- 9.1.1. Select all your programs and activities for Education. (required)
- Reading Wikipedia in the Classroom or other Reading/Evaluating Wikipedia Training, Editing Wikipedia Training, Wikidata programs, Wikimedia Commons programs
- Other programs and activities if any: N/A
- 9.1.2. Select all relevant audience groups for Education. (required)
- Secondary school students, Vocational, tertiary, or higher education, Teachers or professors
- Other groups if any: N/A
Culture, heritage or GLAM
- 9.2. Select all your programs and activities for Culture, heritage or GLAM. (required)
- Documenting or incubating languages on Wikimedia projects, Supporting institutions to open up their collections, data, metadata, and research, Supporting GLAM professionals to incorporate use of Wikimedia in their work, through documentation, training, or Wikimedian in Residence programs, Partnering with institutions, professional associations, and allied organizations to raise awareness of open culture, ethical sharing, and related issues
- Other programs and activities if any: N/A
Gender and diversity
- 9.3. Select all your programs and activities for Gender and diversity.
- Bringing in women and/or gender diverse participants and editors, Focusing on creating content about women and/or gender diverse groups, including biographies, intersectional topic areas and/or adding images, Focusing on creating content about marginalized (underrepresented) communities and their knowledge, Focusing on knowledge equity by bringing in contributors from underrepresented communities, Building organizer skills in women and diversity groups, Fomenting female leadership within the movement (either staff, members or boards), Sensitize and educate for gender perspective among Wikimedia projects stewards and editors
- Other programs and activities if any: N/A
Community support and engagement
- 9.4. Select all your programs and activities for Community support and engagement.
- On-wiki training of community members, Off-wiki training of community members, Organizing meetups, conferences, and community events, Supporting community members' participation in events and conferences, Offering micro-funding and other financial support to community members , Offering non financial support and services to community members (equipment, space, books, etc.)
- Other programs and activities if any: N/A
Participation in campaigns and contests
- 9.5. Select all campaigns that apply. (required)
- Art+Feminism, VisibleWikiWomen, Wiki Loves Women, Wiki for Sustainable Futures, Wikipedia Pages Wanting Photos, Wikipedia Birthday or Anniversary, Not applicable, Other
- Other programs and activities if any: Wikidata Day, #SheSaid, Wiki Loves Pride
Technology (software development)
- T1. Describe the technical project(s) or provide relevant links. (required) Include the following information
- Project goals, impact, and product strategy
- Technical approach, integrations, and dependencies
- Milestones, progress tracking and success metrics
- Demand and community consultations
Project Goals, Impact, and Product Strategy
Our technical strategy for this cycle is the creation of data-driven campaigns. The goal is to move away from untargeted editing toward a tool-grounded approach that ensures sustainability despite climate or partnership shifts. View our Technical Development Plan for this cycle.
- WikiDunong Kiosks: Our primary offline delivery system, deploying 10 offline wiki kiosks to remote schools to provide Wikipedia, Central Bikol Wiktionary, and SHS-relevant ebooks.
- Audit & Discovery Tools: We are leveraging three Toolforge-based MVPs:Wikimedia Commons Explorer, PhilHeritage Data Compass, and SUYAT. These tools will identify critical metadata gaps. The impact of this strategy is two-fold: we provide immediate offline access to students while using our web tools to re-align our volunteer campaigns toward documented needs (e.g., missing heritage images or incomplete Wiktionary entries).
Technical Approach, Integrations, and Dependencies
- Offline Infrastructure: 10 kiosks using Kiwix-Serve on lightweight Linux. Our main technical contribution is a custom Admin Dashboard (Python/SQLite) that parses Kiwix logs to generate visual daily/weekly usage graphs for school administrators.
- Web Tool Migration & Development: We are migrating Commons Explorer to Wikimedia Toolforge to ensure sustainability and adding a targeted query module for featuring high resolution gender and climate media.
- Data Auditing (MVPs): PhilHeritage Data Compass and SUYAT use the Wikidata SPARQL and MediaWiki APIs to audit content. For SUYAT, we are prioritizing the Central Bikol Wiktionary, implementing an on-screen ancient script keyboard and a QuickStatements batch-export feature for admin-verified community suggestions.
- Dependencies: These projects depend on the Wikimedia Toolforge environment, Kiwix ZIM files, and the stability of the Wikidata Query Service.
Milestones, Progress Tracking, and Success Metrics
- Milestones:
- Q1: Development of the Kiosk Admin Dashboard and Toolforge migration of Commons Explorer.
- Q2: Deployment of 10 kiosks to schools and launch of the SUYAT/PhilHeritage MVP audit listings.
- Q3: Data harvest from kiosks and re-alignment of edit-a-thons based on tool-identified gaps.
- Q4:Documentation and initial data collection.
- Success Metrics:
- Reach: Number of unique device clicks recorded by the Kiosk Dashboard.
- Data Quality: Percentage increase in "Complete" status for Central Bikol Wiktionary entries (tracked via SUYAT).
- Efficiency: Number of data orphans (items without images) resolved using the PhilHeritage tool.
- T2. Describe the project team, maintenance, and risk management. (required) Include the following information
- Security and privacy considerations and expertise
- Mitigation of security or privacy risks
- Long-term maintenance, code documentation and licensing
- Team description with expertise, roles, contribution (hours & compensation)
Project Team and Resource Allocation
The technical operations for the WikiDunong Kiosks, Commons Explorer, PhilHeritage Data Compass, and SUYAT are managed by our core team of three (3) full-time staff. To maintain a healthy balance between technical development and our ongoing community edit-a-thons, each staff member will dedicate 50% of their time (20 hours/week) to these technical projects.
- Technical Officer: Focuses on Toolforge migration, Python/SQLite backend for the Kiosks, and the SUYAT on-screen keyboard.
- Project Lead: Oversees strategic alignment, partnership coordination with DepEd/LGUs, and data auditing.
- Community Organizer: Leads volunteer training, "Hatch-A-Wikimedian" sessions, and translates tool data into targeted campaign tasks.
MVP Focus and Strategic Realignment
For this grant cycle, we are prioritizing Minimum Viable Products (MVPs), particularly for SUYAT and PhilHeritage Data Compass.
Our goal is not full-scale feature development, but rather the successful listing and retrieval of content assessments. By perfecting the data-gathering capabilities of these tools first, we can identify exactly where metadata is lacking (e.g., Central Bikol Wiktionary gaps or missing heritage images).
This allows us to re-align our campaign focus, ensuring our volunteers are directed toward high-impact, data-proven needs rather than untargeted editing.
Security, Privacy, and Risk Management
- Privacy by Design: All tools are designed to be free of personally identifiable information (PII) The WikiDunong Kiosks are entirely offline, and our Toolforge apps (Commons Explorer, SUYAT, PhilHeritage) do not require user accounts or store personal data.
- Mitigation of Technical Risks: To protect against the frequent power fluctuations (brownouts) in the Bicol Region, all 10 kiosks are equipped with high-grade surge protectors.
- Admin Gatekeeping: For the SUYAT tool, we mitigate the risk of mass-edit errors by routing all community suggestions through an admin-controlled QuickStatements batch process, ensuring a human-in-the-loop review before any data hits the live Wiktionary.
Long-term Maintenance and Licensing
- Sustainability: By hosting our web tools on Wikimedia Toolforge, we ensure they remain within the movement's technical ecosystem, benefiting from shared maintenance and high uptime.
- Documentation: We maintain a centralized technical repository on GitHub and detailed "how-to" guides on Meta-Wiki. This ensures that if staff roles change, the technical knowledge remains accessible to the User Group.
- Open Source: All custom code is released under the MIT/GPL License, and hardware designs for the kiosks are shared as Open Educational Resources (OER).
- T3. Approximately, how much of the requested budget will you dedicate to technical projects (local currency)? (required)
- 343000 PHP
- 10. Please include a link to or upload a timeline (operational calendar) for your programs and activities. (required)
- https://docs.google.com/spreadsheets/d/14Kr1U8FPc0CAcJtj_hoGOKqI0BSgbFSyMtuSzkXA378/edit?gid=1731796967#gid=1731796967
- 11. Describe your team. (required)
A more detailed description of our organizational structure, roles, and designation can be viewed here: https://docs.google.com/document/d/17q0um8w8tvgShEUGfhsOnZFw_J4DZoEts_y46zVoyPc/edit?tab=t.9y6p0op18y5j#heading=h.o0fbtb19majo
- 12. Will you be working with any internal (Wikimedia) or external partners? Describe the characteristics of these partnerships and bring a few examples of the most significant partnerships. (required)
Yes. We will continue to collaborate with our current partners. With our strategic pivot to develop the tools, the rollout of the WikiDunong Portal Kiosks relies on a multi-layered partnership model that combines global content expertise with local infrastructure and educational support. Internal (Wikimedia) Partners Art+Feminism and Wiki Loves Women: We continue our long-standing partnership with these groups to ensure that the tools we developed are gender-diverse and representative. Their frameworks help us curate specialized ZIM files that address gender gaps in knowledge while we build our WikiDunong Portal kiosk.
Let’s Connect: We participate in learning clinics to exchange best practices on offline education strategies and kiosk maintenance with other global Wikimedians working on similar "library-in-a-box" initiatives. External Partners Department of Education (DepEd) - Bicol Region: Our most significant partnership involves working closely with public high schools.
Local Government Unit (LGU) of Pasacao, Camarines Sur: We will work with this institution to fully understand the mapping requirements to purposely build the PhilHeritage Data Compass in compliance with existing laws.
Local Writers and Cultural Organizations: We partner with local writers. By using Suyat, they help translate and transcribe modern Philippine texts into indigenous scripts, ensuring that this cultural heritage is preserved within the Wikimedia ecosystem.
- 13. In what ways do you think your proposal most contributes to the Movement Strategy 2030 recommendations. Select all that apply. (required)
- Increase the Sustainability of Our Movement, Improve User Experience, Provide for Safety and Inclusion, Invest in Skills and Leadership Development, Identify Topics for Impact, Evaluate, Iterate, and Adapt
Metrics
[edit]Wikimedia Metrics
[edit]- 14. Please select and fill out Wikimedia Metrics for your proposal. (recommended)
- 14.1. Number of participants, editors, and organizers.
All metrics provided are optional, please fill them out if they are aligned with your programs and activities.
| Metrics name | Target | Description |
|---|---|---|
| Number of all participants | 500 | N/A |
| Number of all editors | 100 | N/A |
| Number of new editors | 50 | |
| Number of retained editors | 50 | |
| Number of all organizers | 15 | N/A |
| Number of new organizers | 10 |
- 14.2. Number of new content contributions to Wikimedia projects. (recommended)
| Wikimedia project | Created | Edited or improved |
|---|---|---|
| Wikipedia | 50 | 100 |
| Wikimedia Commons | 1000 | 5000 |
| Wikidata | 5000 | 10000 |
| Wiktionary | 2000 | 2000 |
| Wikisource | ||
| Wikimedia Incubator | 200 | 200 |
| Translatewiki | ||
| MediaWiki | ||
| Wikiquote | 1000 | 1000 |
| Wikivoyage | ||
| Wikibooks | ||
| Wikiversity | ||
| Wikinews | ||
| Wikispecies | ||
| Wikifunctions / Abstract Wikipedia |
- Description for Wikimedia projects contributions metrics. (optional)
For this grant cycle, we have chosen to maintain the same performance metrics used in our previous grant request. Since our core programs (Wikipedia, Wiktionary, and Wikiquote) remain consistent, with just a slight focus on Wikidata, keeping the same metrics provides a stable baseline for our reporting.
While our programs have not changed, our approach has shifted toward utilizing specialized technical tools mentioned above. By keeping our measurement criteria constant, we can more accurately observe and analyze how these new tools affect our efficiency, volunteer productivity, and the depth of our content metadata. This consistency allows us to isolate the impact of this tool as the primary variable, providing clear data on how technical innovation improves our organizational outcomes compared to previous years.
Other Metrics
[edit]- 15. Do you have other quantitative and qualitative targets for your project (other metrics)? (required)
- Yes
| Other Metrics | Description | Target |
|---|---|---|
| Active WikiDunong Deployments | Number of offline portals to be deployed or maintained during the 2026-2027 period. Trageting ten (10) portals as stepping stones toward the 2030 goal of fifty (50) portals. | 10 |
| Educational Impact Stories | Number of collected stories highlighting how access to the offline portals or local language wikis directly supported a student's education or access to information. | 5 |
| Safe and Inclusive Culture Feedback Survey | Number of respondents on regular feedback surveys or focus groups to measure the sense of belonging and psychological safety among volunteers, particularly women and minority advocates. This directly supports the goal of creating a sustainable, safe editing environment. | 50 |
| N/A | N/A | N/A |
| N/A | N/A | N/A |
Budget
[edit]- 16. Will you have any other revenue sources when implementing this proposal (e.g. other funding, membership contributions, donations)? (required)
- No
- 16.1. List other revenue sources. (required)
N/A
- 16.2. Approximately how much revenue will you have from other sources in your local currency? (required)
- N/A
- 17. Your local currency. (required)
- PHP
- 18. What is the total requested amount in your local currency? (required)
- 3918400 PHP
| Year | Amount (local currency) |
|---|---|
| Year 1 | N/A PHP |
| Year 2 | N/A PHP |
| Year 3 | N/A PHP |
- Requested amount in USD
- 67788.32 USD [note 1]
| Year | Amount USD [note 1] |
|---|---|
| Year 1 | N/A USD |
| Year 2 | N/A USD |
| Year 3 | N/A USD |
- ↑ a b c The following amount in US dollars was calculated by Wikimedia Foundation staff using the fixed currency rates. This amount is approximate and may not reflect the actual currency exchange rates on the day of submission or distribution. If the application is funded, the funding will be sent in the recipient’s local currency.
- 19. Does this proposal include compensation for staff or contractors? (required)
- Yes
- 19.1. How many paid staff members do you plan to have? (required)
Include the number of staff and contractors during the proposal period. If you have short-term contractors or staff, please include them separately and mention their terms.
- There will be 3 full-time staff, and several interns receiving daily allowance depending on the program need and budget.
- 19.2. How many FTEs (full-time equivalents) in total? (required)
Include the total FTE of staff and contractors during the proposal period. If you have short-term contractors or staff, please include their FTEs with the terms separately.
- There will be 3 full-time staff, and interns receiving daily allowance.
- 19.3. Describe any staff or contractor changes compared to the current year / ongoing General Support Fund if any. (required only for returning grantees)
- Proposed Changes in Staffing for FY 2026-2027
1. An increase of Php 5,000.00 or 8% for the compensation of the Program Manager role. 2. An increase of Php 2,000.00 or 6% for the compensation of the Lead Designer role. 3. Budget allocations for interns’ allowances will be based on the program budget.
- 20. Please provide an overview of your overall budget categories in your local currency. The budget breakdown should include only the amount requested with this General Support Fund (required).
| Budget category | Amount in local currency |
|---|---|
| Staff and contractor costs | 2304000 PHP |
| Operational costs | 398400 PHP |
| Programmatic costs | 836000 PHP |
- 21. Please upload your budget for this proposal or indicate the link to it. (required)
Additional information
[edit]- 22. In this optional space you can add any other additional information about your proposal or organization that you think can help us when reviewing your proposal. (optional)
Following a successful pilot phase for our core initiatives for the past years, the 2026-2027 cycle represents a period of technical consolidation and operational optimization for Wiki Advocates Philippines. Our strategy for this year is built on the principle of tool-grounded sustainability transitioning from manual outreach to a data-driven model powered by our own suite of open-source campaign tools.
1. Strategic Shift in Metrics and Tools' : For this cycle, we are retaining our core operational metrics while implementing a strategic pivot toward utilizing our proprietary campaign tools. By integrating SUYAT, PhilHeritage Data Compass, and the Commons Explorer, we are moving from generalized editing to a tool-based approach. This allows us to identify and resolve specific content gaps (e.g., missing audio, scripts, or heritage metadata) with much higher precision than in previous years.
2. Operational Efficiency and Office Usage : In an effort to maximize our programmatic impact while remaining fiscally lean, we have decided to forego the full-time administrative function of our office space. While we are retaining the physical space to serve as a hub for hosting community events, and edit-a-thons, The reduction in full-time staffing presence allows us to reallocate funds toward our core initiatives.
3. Optimized Staffing and Internship Model: To ensure our ₱836k programmatic budget is used effectively, we have restructured our staffing support. Instead of a standalone administrative budget for interns, intern allowances will now be deducted directly from Volunteer Support or specific program budgets on an as-needed basis. This ensures that our student interns are directly embedded in the projects they support, such as the WikiDunong Kiosk rollout or Salbar Tataramon.
4. Commitment to Core Work Areas: Despite our technical evolution, we remain fully committed to our established work areas: DEI, Language Preservation, Sustainability, and Education. These focus areas are dictated by the documented needs of our community, and our country.
5. Leveraged Funding Strategy : To protect the our core budget request, we intend to proactively seek additional funding support for other global events such as Wikidata Day, Wikimania, and Wikipedia Birthday Celebration. By accessing future scholarships and specialized grants for these global milestones, we can ensure that our primary grant remains dedicated to the achieving our core targets fort his year.
By submitting your proposal/funding request you confirm that you have read and agree to the Application Privacy Statement, WMF Friendly Space Policy, and the Universal Code of Conduct.
- Yes
Feedback
[edit]- Please add any feedback to the grant discussion page only. Any feedback added here will be removed.
- Wikimedia Community Fund/Proposals
- Wikimedia Community Fund/Proposals/Under review
- Education - General Support Funds in FY 2025-26
- Culture, heritage or GLAM - General Support Funds in FY 2025-26
- Gender and diversity - General Support Funds in FY 2025-26
- Community support and engagement - General Support Funds in FY 2025-26
- Participation in campaigns and contests - General Support Funds in FY 2025-26
- Tech - General Support Funds in FY 2025-26
- Under review General Support Funds for ESEAP in FY 2025-26
- Under review General Support Funds for ESEAP in FY 2025-26 (Round 2)
- General Support Funds for ESEAP in FY 2025-26 (Round 2)
- General Support Funds in FY 2025-26 (Round 2)
- Under review General Support Funds in FY 2025-26 (Round 2)
- General Support Fund proposals by Wiki Advocates Philippines User Group
- Under review General Support Funds in FY 2025-26