Grants:Programs/Wikimedia Community Fund/Rapid Fund/Codex Toolbox (ID: 23598580)
Applicant details
[edit]- Main Wikimedia username. (required)
Toghrul R
- Organization
N/A
- If you are a group or organization leader, board member, president, executive director, or staff member at any Wikimedia group, affiliate, or Wikimedia Foundation, you are required to self-identify and present all roles. (required)
N/A
- Describe all relevant roles with the name of the group or organization and description of the role. (required)
Main proposal
[edit]- 1. State the title of your proposal. This will also be the Meta-Wiki page title.
Codex Toolbox
- 2. and 3. Proposed start and end dates for the proposal.
2026-01-16 - 2026-04-16
- 4. What is your tech project about, and how do you plan to build the product?
Include the following points in your answer:
- Project goal and problem you solve
- Product strategy or project roadmap
- Technical approach (infrastructure, tech stack, key tools and services)
- Integrations or dependencies (if any)
The project is about creating a Codex-based gadget for Azerbaijani Wikipedia similar to Twinkle but with many new features and built with modern tools. At the moment, patrollers and admins spend too much time on repetitive manual work. The gadget will bring everything into one interface: nominating pages for deletion, adding and removing maintenance templates, viewing article statistics, performing actions on page links, protecting and unprotecting pages, handling user complaints, sending user warnings, greeting newcomers, and several exclusive moderation features. It will also have user settings, so each editor can customize the gadget to their own workflow and preferences.
The plan is to build and release the tool in three months. In the first month, a prototype with deletion nominations and tagging will be developed. In the second month, user-related functions (warnings, greetings, complaints), page protection, and preferences will be added. In the third month, the gadget will be fully tested, the interface will be refined, and the final version will be released with documentation.
- 5. What is the expected impact of your project, and how will you measure success?
Include the following points in your answer:
- Milestones and progress tracking
- Project impact and success metrics
On Azerbaijani Wikipedia about 85 users rely on the old Twinkle gadget, and the community has already expressed support for a Codex-based replacement. The project will move from prototype to full release within three months. Success will be measured by how many editors adopt the new tool, the feedback from patrollers and admins, and the extent to which it speeds up routine maintenance work. The expected impact is a modern, customizable and scalable gadget that makes almost all action faster and easier.
- 6. Who is your target audience, and how have you confirmed there is demand for this project? How did you engage with the Wikimedia community?
Include the following points in your answer:
- Project demand and target audience description
- Links to interaction(s) with Wikimedia community
- Evidence from community consultation such as the [Community Wishlist]
The target audience for this project is experienced editors, patrollers, and administrators on Azerbaijani Wikipedia who carry out page maintenance, tagging, user warnings, and deletion and many other processes on a daily basis.
A detailed project proposal was published on the Village Pump of Azerbaijani Wikipedia, where editors, mosty admins, expressed their support for the idea: https://w.wiki/FqGz
- 7. How will your team predict and manage potential user security and privacy risks, and what risks do you currently see?
Include the following points in your answer:
- The level of in-house or consulted security and privacy expertise you will have available to you during delivery of this project
- How your development, testing, and deployment processes mitigate the introduction of unnecessary security or privacy risks
The gadget will only use the standard MediaWiki Action API with existing permissions and logs, so no new data collection or storage is involved. Development will follow Wikimedia's security and privacy guidelines, with testing done on-wiki in a controlled environment before release. Experience from maintaining existing gadgets and sysop tools will guide the work, supported by WMF documentation and best practices to avoid unnecessary risks.
- 8. Who is on your team, and what is your experience?
Include the following points in your answer:
- Your experience as a developer, relevant past projects
- Wikimedia SUL (developer), Gerrit, Github, Gitlab or other relevant public account handles
- Other team members, their roles and expertise
The team consists of Toghrul Rahimli (developer) and Aida Aslanova (testing, documentation). Toghrul has been an Interface Administrator on Azerbaijani Wikipedia since 2019, with several years of front-end development experience. He has developed numerous gadgets and scripts (for example, AFD Archiver (Codex), Admin Stats Menu, Case Converter Unwikilink), is experienced in JavaScript, CSS, and Lua, and created and adapted modules that enable full Wikidata infobox integration into Azerbaijani Wikipedia, including lexical rules and technical adaptations. He is also familiar and tested an alpha version of the proposed gadget, without integrating into Wikipedia.Aida Aslanova, the other member of the team will act as a tester, providing feedback during development to ensure smooth integration and usability. Her work will mainly include preparing documentation and recording test results, reporting bugs and tracking issues/fixes.
- 9. How will the project be maintained long-term?
Include the long-term maintenance plan with maintainer(s) in your answer. If you expect the long-term maintenance to incur expenses, please list those and the plan for long-term expense coverage.
The project is planned to be fully completed within three months, with small polishing touches over time and no further extensive development. The gadget will be stable and ready for long-term use, but the code will remain open and well documented so that it can be scaled or extended later
- 10. Under what license will your code be released, and how will you ensure the product is well documented?
Include the following points in your answer:
- Code license and compatibility with Wikimedia projects
- Documentation plan
The code will be released under CC0, making it fully open and compatible with Wikimedia projects. Documentation will be provided in-code and on a dedicated help page, covering setup, functions and user preferences. The gadget will be built with central configuration files so it can be easily adapted to other wikis.
- 11. Will your project depend on or contribute to third-party tools or services?
No, the project will not depend on any third-party tools or services.
- 12. Is there anything else you’d like to share about your project? (optional)
Budget
[edit]- 13. Upload your budget for this proposal or indicate the link to it. (required)
https://docs.google.com/spreadsheets/d/1gJbVADpnpge3a-TQr4XgLdNJd_PyWsSkqSY1TaryZbE/edit?usp=sharing
- 14. and 15. What is the amount you are requesting for this proposal? Please provide the amount in your local currency. (required)
8490 AZN
- 16. Convert the amount requested into USD using the Oanda converter. This is done only to help you assess the USD equivalent of the requested amount. Your request should be between 500 - 5,000 USD.
4995 USD
- We/I have read the Application Privacy Statement, WMF Friendly Space Policy and Universal Code of Conduct.
Yes
Endorsements and Feedback
[edit]Please add endorsements and feedback to the grant discussion page only. Endorsements added here will be removed automatically.
Community members are invited to share meaningful feedback on the proposal and include reasons why they endorse the proposal. Consider the following:
- Stating why the proposal is important for the communities involved and why they think the strategies chosen will achieve the results that are expected.
- Highlighting any aspects they think are particularly well developed: for instance, the strategies and activities proposed, the levels of community engagement, outreach to underrepresented groups, addressing knowledge gaps, partnerships, the overall budget and learning and evaluation section of the proposal, etc.
- Highlighting if the proposal focuses on any interesting research, learning or innovation, etc. Also if it builds on learning from past proposals developed by the individual or organization, or other Wikimedia communities.
- Analyzing if the proposal is going to contribute in any way to important developments around specific Wikimedia projects or Movement Strategy.
- Analysing if the proposal is coherent in terms of the objectives, strategies, budget, and expected results (metrics).
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.