#VisualEditor
Tech News 2026 – Issue 42
Latest **tech news** from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available. **Weekly highlight** * Starting October 13, wikis can change the default pattern for auto-generated reference names in VisualEditor (currently `<**ref** name=":1" />`). They will be able to use human-readable, content-based reference names that are more helpful to contributors using the source editor (e.g. `<**ref** name="Miller2026-1" />`). VisualEditor reference name patterns can be defined using MediaWiki system messages, JSON, templates and modules (more information). Admins can enable these changes via community configuration. This is a community wish implemented by WMDE Technical Wishes. [1] * Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to English Wikipedia on October 14 and to remaining Wikimedia Foundation wikis by end of October (likely October 21). The FAQ lists possible actions to take on your wiki to support the deployment. This is a long-standing community wish implemented by WMDE Technical Wishes. [2][3] **Updates for editors** * Moderator Tools will be removing the list view of the Watchlist and defaulting everyone to the changelog view. Previously, there were two versions of how the Watchlist is shown to mobile web users: the list view, where editors could see watched articles in a list format, and the changelog view, where editors could see changes to watched articles in a log format, controlled by a user’s Advanced Mobile Control settings. This has created issues for code-base maintenance: two different displays means two sets of code to manage. By defaulting to the changelog view, we are simplifying the codebase and avoiding the likelihood of missing bugs. * The Wikipedia Android app is testing a way to listen to article introductions in the “For you” feed. A text-to-speech model reads the existing article text aloud without rewriting it or adding any content. The 30-day experiment will begin in the Wikipedia Beta app during the third week of September, then move to the regular Wikipedia Android app in October for a limited group of eligible users. A small portion of app users (those with English feeds and at least one topic interest) will have access to the feature. This experiment is part of broader efforts to give app readers options in how they consume content in order to deepen engagement and user retention. Learn more and share feedback. * CodeMirror syntax highlighting was enabled by default for all logged out and newly registered users on the English Wikipedia on September 14. With no signs of adverse effects, the same change is being proposed to be made globally across all wikis in a few weeks. If you have concerns or feedback, or if your wiki would like to opt out, please see the help page. [4] * Wikidata mobile statement editing of all datatypes will be officially launched on October 13, when it will be removed from Wikidata beta features and become available to all editors. Users can report bugs and share feedback. * Last week, language link changes were removed from Recent Changes and Watchlist feeds on Wikivoyage, Wikisource, Wikiversity, Wikiquote and Wiktionary. As no adverse effects have been observed, the Wikidata For Wikimedia Projects plans to roll out this change globally to all Wikipedias. This is scheduled for October 13 at 07:00 UTC, after which editors will no longer see when a link to _another_ language version of a page is added, removed, or changed in its Wikidata item. Editors who rely on these notifications can read more on the project page and share feedback or ask to opt out their wiki on the talk page. [5] * View all 28 community-submitted tasks that were resolved last week. For example, an issue where accidentally touching the graph while scrolling on the Pageviews tool on mobile could unintentionally zoom in has now been fixed. Click-and-drag zoom is now disabled on touch devices. [6] **Updates for technical contributors** * There are three major changes coming to dumps: the legacy content dumps deprecated in January 2026 will now be sunset, the replacement MediaWiki Content File Exports will be delayed to implement a “safety buffer”, and they are now also available as 7zip-compressed files. Users will need to switch the URL they download their dump from. For more information, timeline and migration instructions, see Legacy content dumps sunset. * The Wikimedia Foundation discovered unauthorized activity by OpenAI agents on Wikimedia projects, including edits to wikis, attempts to exploit a public note-taking tool, and heavy automated traffic. There is no evidence that Wikimedia systems were used for coordination among agents or that our systems or data were compromised. * Detailed code updates later this week: MediaWiki **Meetings and events** * Save the date for the next Wikimedia Hackathon! We’ll be meeting in lovely Tirana, Albania for the 2027 Wikimedia Hackathon from April 9–11, 2027. Scholarship and staff sponsorship applications are currently being accepted through Pretix and will close on October 30, 2026. General registration will open in January 2027. _**Tech news** prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe._
diff.wikimedia.org
October 13, 2026 at 12:34 AM
If the AI can code, then we should probably be treating it like other code compilers, just with more 'built-in' subroutines and components. Maybe the interface for _that_ AI application looks like a cross between The Incredible Machine and the Wikipedia VisualEditor. links and code and objects
September 30, 2026 at 4:51 PM
The Aotearoa New Zealand Online Wiki Meetup is on this Saturday 19 Sept, 10–11:30am 💻

Wikimedians from across the motu will discuss what they've been up to, share what they've learned lately, and get help with anything they're stuck on. New attendees are always welcome! Details here: w.wiki/UeDA
Wikipedia:Meetup/Aotearoa New Zealand Online/79 - Wikipedia
Edit with VisualEditor
w.wiki
September 17, 2026 at 9:01 PM
Lean Publishing Tip of the Day 💡 New Author Features Livestream with Peter & Len

youtu.be/hpTHHC1xA5w

Sign up on LinkedIn: www.linkedin.com/newsletters/...

#books #leanpublishing #selfpublishing #writingtips #MinimalEditor #VisualEditor #Markua #GhostAI
September 9, 2026 at 2:15 AM
Lean Publishing Tip of the Day 💡 Managing Book Files in Our Visual Editor

youtu.be/5KVCGJPGJnM

Sign up on LinkedIn: www.linkedin.com/newsletters/...

#books #leanpublishing #selfpublishing #writingtips #visualeditor #bookmanuscript #filemanagement #ghostAI
August 29, 2026 at 3:45 AM
Working with the Visual Editor within Outreachy
Continuing our work in the wish #3 of the Lusophone Technological Wishlist within the 32nd round of Outreachy… Over the past weeks, development focused on MediaWiki, Visual Editor and their core extension ecosystem. While the validation logic itself was initially expected to be straightforward, configuring the local ecosystem presented the first major complexity. Setting up VisualEditor, Citoid, and Cite locally required carefully identifying and setting up the exact suite of dependencies needed to replicate Wikipedia’s production environment. Following mentor recommendations, the setup was built using a Wikimedia dockerized environment. To ensure accurate citation formatting and parsing, the following extensions were required to integrate: * Cite, Citoid which are required to search, retrieve, and translate inputs (ISBN, DOI, or URL) into reference nodes. * TemplateData, Scribunto, TemplateStyles to support structured citation template rendering. A key learning in this initial stage was that a mismatch between Citoid’s expected metadata structure and the local template key identifiers causes a parsing failure. After fixing, the end-to-end debugging automation citation flow was ready to use. The next phase was development iterations and workflow progressions. The first ‘proof of concept’ successfully captured duplicate reference nodes within the Automatic Tab and displayed a prompt within the dialog. Then a direct redirect button was introduced to transfer users to the Re-Use tab. The initial patch was submitted to Gerrit for review. The feedback from mentors included establishing unit tests, fixing bugs and improving the validation logic. In collaboration with project mentors we explored different alternatives to resolve duplicates. One option was to resolve this duplicate in the active dialog instead of redirecting. This first attempt worked but ignored the option to add details in a reference. So, the flow was adjusted back to redirect to the Re-Use tab and enhanced to include the details information when present. “Add a citation” popup in Visual Editor modified with new in development feature of “duplicate reference found”. Wikimedia provides extensive documentation. Covering extension configuration, core file structures and navigating a high volume of technical resources was initially overwhelming. As part of the next steps and status at this stage, the patch for the VisualEditor duplicate reference validation is currently under review on Gerrit. While awaiting further feedback to polish this implementation, project efforts are transitioning to new objectives on the Lusophone wishlist, specifically wish #8. It is expected a transition to work mainly on Python instead of Javascript and focus on reviewing the WikiScore project codebase and updating it to support Wikidata. Further updates on the patch status and the initial findings on WikiScore will be detailed in the next progress report.
diff.wikimedia.org
August 15, 2026 at 5:22 PM
I believe I have a unique perspective on this. As background, I am, indeed, *that* "kww", the one that blocked the visual editor on Wikipedia in direct defiance of Wikimedia.
March 27, 2026 at 4:36 PM
"What was your biggest impact on the internet?"

I led a successful rebellion against Wikimedia.
January 1, 2026 at 4:15 AM
Then again, the Wikimedia Foundation has a bad track record for listening to editors. Did I ever tell you about the time I overrode their choice of default editing tools? www.dailydot.com/unclick/wiki...
Wikipedia faces revolt over VisualEditor
Wikipedia's VisualEditor was supposed to solve a problem, but instead, it's caused one of its own.
www.dailydot.com
June 12, 2025 at 1:55 PM
My first claim to international fame was in the Daily Dot.
May 2, 2025 at 4:11 AM
Enhance Your WordPress Design Experience: Live, Easy, and Enjoyable. Say goodbye to the backend! Design your forms directly from the Elementor editor, adjusting fields, spacing, columns, and layout—all within the same interface. #Elementorpro #FormBuilder #visualeditor
codagift.com/elementor-pr...
May 5, 2024 at 7:56 PM
Wikipedians: Meet VisualEditor and help with the rollout #Wikipedia #VisualEditor http://t.co/6U6ffeyWqK
December 7, 2024 at 11:48 AM
We referenced geissler tubes to create new creatures.
Models used:
- Flux by @blackforestlabs.bsky.social
- Kling
- Hunyuan
- Rembg image background removal
#aiworkflow #creativesoftware #nodes #visualeditor #aimodels #moodboard #characterdesign #klingai #hunyuanai #fluxai
February 9, 2025 at 9:27 AM
簡単なフィード作るなら、jsonをゴリゴリ書く必要もなく、VisualEditorで十分ですな。
February 8, 2024 at 3:33 AM