✨ อัปเดตล่าสุด: wiki/Special:MyLanguage/Wikifunctions:Status updates/

Wikifunctions Status updates

Quarterly planning

What's planned for Q2 (October–December 2026) - With October, we're starting Q2 of the Foundation's fiscal year which runs from July to June. To kick off this quarter, we'd like to share our two main areas of focus: working with our pilot communities towards bringing abstract articles into their Wikipedias, and making it easier to create and edit articles on Abstract Wikipedia. Alongside this, we'll keep working on performance and reliability, and on other improvements based on what we learn along the way.

Focus 1: Pilot Wikipedia Integration

Throughout Q1, we worked with three pilot communities (Malayalam, Dagbani, and Igbo) interested in using abstract articles on their Wikipedias. We ran our first round of Lexeme workshops and have started rolling out the integration functionality to our first pilot community, though no articles are integrated yet.

This quarter, we want to build on that. Our goal is to support the communities in bringing the first abstract article into their Wikipedias by the end of this quarter. To ensure the articles the communities are interested in render well in their languages, we're planning to run Wikifunctions workshops and additional Lexeme workshops.

Concrete hypotheses we're working on:

Lexeme coverage (continued from Q1, led by our colleagues in Wikimedia Deutschland). We're aiming for an average of 80,000 Lexeme edits a month across Q1 and Q2 (baseline for January–March 2026: 66,670), with efforts increasingly focused on Abstract Wikipedia's pilot communities.
Wikifunctions workshops for pilot communities. If we run workshops tailored to the pilot communities, we can support the communities in creating and improving the language-specific functions their languages need to render Abstract articles.
Improving language-specific function creation. If we make it simpler to create a new language-specific function, it should be easier for communities, pilot communities especially, to build the functions they need.

Focus 2: Abstract Wikipedia Experience

Currently, editing on Abstract Wikipedia is pretty complicated and works best for contributors already familiar with Wikifunctions. We've seen that it's much harder for other editors, and as Abstract Wikipedia grows, we'd like both the existing community and newcomers to be able to edit effectively. Making it easier to create and edit articles will be a focus over the next two quarters (October–March).

Concrete hypotheses we're working on:

Abstract Wikipedia editing improvements. If we iteratively implement and evaluate focused editing improvements, then we can progressively make editing and article creation accessible to a broader, less technical group of contributors.
Feedback loop between Abstract editors and function creators. If we explore ways for contributors to capture sentences they would like to include but can't yet express on Abstract Wikipedia, and share these with the Wikifunctions community, we can establish a workable feedback loop between content needs and function development.
Exploration: Natural language to function mapping. If we explore approaches that map what contributors want to express in natural language to relevant function calls, we can find out whether this might be a viable way to lower the barrier to creating abstract content.
Cache-refresh for Abstract articles. If we provide a clear and reliable way to refresh stale cached data on Abstract Wikipedia, contributors will be able to see their changes in Wikifunctions and Wikidata reflected, and be more confident that their edits take effect.

Recent Changes in the software

We are replacing the editor used when editing code Implementations and HTML fragments, switching from Ace to CodeMirror (T400015), which should resolve several Unicode issues and be more consistent with the rest of the Wikimedia editing experience. We plan to enable the new editor this week, but may delay or undo this if there are any issues.

Creating and editing Objects on Wikifunctions will now apply your edit preferences, like saving edited pages to your watchlist (T372149).

The type-ahead search bar integration on Abstract Wikipedia will now show pages without current articles as red links, "No article yet", and an icon, instead of just "— AW" for pages that do have one (T435649).

We also improved the way that Special:FunctionUsage tracks pages that use a Function, which should improve the data as pages get edited (T433542). A follow-up will clean the old data out (T435656).

We fixed a bug that meant regular users would see no test results at all when there were lots to fetch (T433746).

Finally, we added support for the Z2075/kqr (Kimaragang, T437497), Z2076/gdo (Godoberi, T436856), Z2077/bn-sylo (Bangla in Sylheti Nagari, T438611), and Z2078/it-ch (Swiss Italian, T439338) Languages.

News in Types: Multilingual and monolingual HTML

As part of the work needed for the new error message key (Z50K3), which was announced three updates ago, we created a couple of new types we haven't really announced yet. While these were really important for having translatable HTML error messages, we believe they can also be used for a lot other things, so we are excited to make an official introduction.

Meet Z91/Monolingual html, and Z92/Multilingual html: These two types follow a similar naming and structure Z11 and Z12, but instead of containing a Z6/String as their terminal value, they contain a Z89/HTML fragment:

Z91/Monolingual html, represents a HTML blob in a specific language, and has two keys:

Z91K1/language: with the natural language used in the fragment, and
Z91K2/HTML fragment: with the string containing a valid HTML.

Z92/Multilingual html, represents a HTML blob available for multiple languages, and has one key:

Z92K1/HTML fragments: with a list of Monolingual html objects.

Unlike the Monolingual and Multilingual text types, the new types don't have custom UI components that provide easier editing, selection of languages, visualization and controls for deduplication, but the default view allows for detailed creation and editing. Let us know your suggestions and uses for these types!

Volunteers’ Corner on 12 October

The next Volunteers’ Corner will be on Monday, 12 October 2026 at 17:30 UTC. We plan to have the following agenda: there will be time to ask questions and discuss all matters arising. If we have time, we will write a function together. Everyone is welcome to join us on Google Meet.

Fresh Functions weekly: 175 new Functions

This week we had 175 new functions. Here is an incomplete list of functions with implementations and passing tests to get a taste of what functions have been created. There has been a massive increase in Hindi coverage over the last week, and quite a few Malayalam, Japanese, and Latin functions. Thanks everybody for contributing!

A complete list of all functions sorted by when they were created is available.