Hi all,
With excitement we're sharing today that Vue.js is Wikimedia
Foundation's official choice for adoption as future JavaScript
framework for use with MediaWiki.
The evaluation of front-end frameworks officially started mid 2019, as
part of the Platform Evolution program’s goal to evolve our technology
platform and development processes to empower the Wikimedia
Movement[0].
The corresponding Technical RFC was successfully resolved in March
2020[1]. As this framework selection is a wide-ranging, long-term
decision, a dedicated group, the Front-end Architecture Working
Group[2], was established to drive the technology comparison and the
final recommendation. Besides the resolved RFC the outcome was to
build and test developer experience in a pilot project[3].
The selected pilot was within the Desktop Improvements project[4] with
its new Vue.js-based TypeaheadSearch feature that allows for providing
additional context while searching. Since its introduction in March
2021[5] the new TypeaheadSearch component has been the default across
15 wikis of varying sizes and has received positive user feedback[6].
A final developer satisfaction survey was completed to gain further
information on the developer experience. The survey results emphasized
“a positive light on the future of working with Vue.js”. And “[t]he
engineers felt optimistic about the future and confident in
recommending it for adoption across all our teams.”
The pilot gave us confidence in the recommendation to adopt Vue.js and
we are moving into further implementation of Vue.js tooling and
product migration planning.
To support further efforts, the Wikimedia Foundation has established
the Wikimedia Design System team[7], which I'm proudly part of. Our
continued work and upcoming priorities include:
- Preparing a shared Vue.js user-interface components library
- Deciding on Vue 2 or Vue 3 including transition path
- Figuring out how the components library will be built and
distributed in and beyond MediaWiki
You can find more of the ongoing work on Phabricator[8].
For full transparency, we've carried that knowledge with us for some
time already, but were prioritizing progressing integration, annual
planning and our internal All-hands conference to finally arrive at
this announcement today.
I'd like to thank a number of folks involved in leading to this, all
Front-end Architecture Working Group members, especially colleagues
Eric Gardner & Roan Kattouw for driving the RFC, the Readers Web team
for undergoing as pilot implementers and especially our former
colleague Stephen Niedzielski who was central to making it a success,
Wikimedia Deutschland for numerous insights through their Vue.js
experience, current Design System team members responsible for further
progress, all Movement volunteers involved in both providing feedback
to the pilot and contributing to development and Product & Tech
department leadership for their strong support of this wide-reaching
change.
Best regards,
Volker
References
[0] https://www.mediawiki.org/wiki/Platform_Evolution/Recommendations#1._Develo…
[1] https://phabricator.wikimedia.org/T241180
[2] https://www.mediawiki.org/wiki/Frontend_Architecture_Working_Group
[3] https://www.mediawiki.org/w/index.php?title=File:FAWG_Demo.pdf&page=26
[4] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements
[5] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Updates#Mar…
[6] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements#List_of_ear…
[7] https://www.mediawiki.org/wiki/Design_Systems_Team
[8] https://phabricator.wikimedia.org/T286946
---
Volker Eckl
Design Lead
Wikimedia Design System
Wikimedia Foundation
1 Montgomery Street
Suite 1600
San Francisco, CA 94104
Hi all,
we propose to remove `capitalize-all-nouns` skin functionality from
MediaWiki core without deprecation in 1.37.
Patch to remove: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/435638
Patch to continue functionality in Monobook:
Bug: https://phabricator.wikimedia.org/T97892
Existing uses:
https://codesearch.wmflabs.org/search/?q=MagicWord%3A%3AclearCache&i=nope&f…
MediaWiki core has a feature whereby the setting $capitalizeAllNouns = true
can be set in a LanguageXx.php file. When this is set, OutputPage attaches
the `capitalize-all-nouns` CSS class to the page <body> element. The only
languages for which $capitalizeAllNouns = true are German and languages
with German as a fallback (e.g. Alemannic).
The only widely used skin using this has been Monobook to disable lowercase
transformation of tab titles for those languages. A few other skins might
have applied the same functionality when basing on top of Monobook.
We've copied this obscure functionality over to Monobook in the meantime
and would recommend doing so for your skin if you like to continue to use
it.
In any case, as this removal results in a non-existing CSS class mostly
rendering of some elements of the skin in some languages would change
slightly.
Please note, that no other modern Wikimedia deployed skin has used this
ever since Monobook.
Thanks to volunteer Jack Phoenix and my colleague Jon Robson for driving
this work.
Regards,
Volker
Hi all,
Since January 2020, Wikimedia has not served traffic to browsers which do
not support TLS 1.2 [0]. We would like to bump basic MediaWiki software
stack support to exclude those very old browsers as well.
Our MediaWiki core, extensions and skins basic browser support matrix still
includes some end-of-life browsers published between 2007 and 2013 that are
only supporting the now insecure ciphers of TLS 1.0 and 1.1.
We've gathered stats [1] emphasizing the relatively small access
expectations. Now we want to push software stack support to align to those
browser versions already in place as minimum in Wikimedia hosted
MediaWikis.
We're continuing to provide support for browsers published from 2013 on!
Note that Internet Explorer 9 and 10 are unaffected by this proposed change
as well for the moment. See the specific list on task. [1]
What's to win:
A great number of design and layout features (CSS, SVG and WAI-ARIA, see
the list [2]) which we currently just exceptionally use in some products or
via extra effort, performance impacting hacks and workarounds, and
maintenance on the developer side.
Current support is slowing down some advances in Desktop Improvements and
other front-end work.
What's to lose:
Possible layout issues in third party MediaWikis still targeting those
end-of-life browers. Content access should be untouched there.
If there are no objections within the next 10 days, we're going to amend
the support matrix with aforementioned TLS 1.2 supporting browsers as the
minimum.
Please let us know about any objections or further inputs, preferably on
task.
Thanks and best regards,
Volker
[0] - https://phabricator.wikimedia.org/T238038
[1] - https://phabricator.wikimedia.org/T238038
[1] - https://phabricator.wikimedia.org/T266866
[2] - https://phabricator.wikimedia.org/T266866#6591703
---
Volker E.
Lead UX Engineer
Desktop Improvements/Design System
Wikimedia Foundation
The upcoming *Wikifunctions wiki needs a logo
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Abstract_Wikipedia/Wikif…>.*
Please help us to: discuss the overall goals of the logo, to propose design
ideas and specific designs, and to give feedback on other designs.
More details about design recommendations and ideas are on the talkpage.
You can read an explanation about "functions" and the related Abstract
Wikipedia initiative on the main project page
<https://meta.wikimedia.org/wiki/Special:MyLanguage/Abstract_Wikipedia>.
Thank you!
--
Nick "Quiddity" Wilson (he/him)
Community Relations Specialist
Wikimedia Foundation
Hi,
we've released OOUI v0.41.0 last Thursday.
It will rollout on the normal train tomorrow, Tuesday, 08 December.
Highlights in this release since v0.40.0:
- Accessibility enhancements on PopupWidget (keyboard tabbing order)
and ToggleSwitchWidget.
Thanks to volunteer contributor Edwin Tam.
- Icon optimization resulting in less data sent to our users in
several often used icons.
Thanks to Thiemo Kreuz for the contributions here.
- Additional 'volume*' & 'network', 'networkOff' icons.
Thanks Matthew Williams and Sudhanshu Gautam for the design work.
-It also contains a deprecating change. Passing a string to `OO.ui.infuse()` is
deprecated, use an HTMLElement or jQuery collection instead.
You can find details on additional new features, code-level, styling
and interaction design amendments, and all improvements since v0.38.0
in the full changelog[0].
If you have any further queries or need help dealing with deprecating
changes, please let me know.
As always, interactive demos[1] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.41.0
MediaWiki version: 1.36.0-wmf.21
Date of deployment to production: Regular train, starting Tuesday 08 December
[0] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.41.0/History.md
[1] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
Hi,
we've released v0.40.0 and follow-up hot fix v0.40.1 of OOUI library
last Friday.
It will rollout on the normal train tomorrow, Tuesday, 11 August.
Highlights in this release:
- Removal of Internet Explorer 8 specific code and fallbacks, largely
reducing size of CSS (~800+ lines on all icons) due to removal of PNG
fallback images, relying only on SVG icons from here on. This is going
to have a positive performance impact for all other users of the
library.
This is in alignment with approved RFC on removing IE 8 Basic support
for MediaWiki core.[0]. Hence, this release is a breaking release. If
you need continuous support in your environment for IE 8 you need to
stick with v0.39.3.
You can find details on additional new features, code-level, styling
and interaction design amendments, and all improvements since v0.38.0
in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[2] and library documentation is available
on mediawiki.org[3], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[4].
OOUI version: 0.40.1
MediaWiki version: 1.36.0-wmf.4
Date of deployment to production: Regular train, starting Tuesday 11 August
[0] - https://phabricator.wikimedia.org/T248061
[1] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.40.1/History.md
[2] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[3] - https://www.mediawiki.org/wiki/OOUI
[4] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
Hi,
I'm excited to share the release of the Vue.js Migration Project
Charter[0] today.
This is an update on the Foundation's evaluation and adoption of
Vue.js framework for building user-interfaces in a modern,
developer-friendly, inclusive, and internationalization-ready way. It
is a result of the platform evolution program[1] recommendations.
We aim to achieve this with help of the shared components and patterns
library Wikimedia Vue UI (WVUI). We project to implement first,
slimmed-down components for it as part of the Vue.js Search Case
Study[2].
Please find further details on the article. Also keep in mind, that
the shared charter reflects current planning and is subject to
repeated evaluation and possible change. Provide any feedback or
questions, on the talk page[3], technical issues and ideas on
Phabricator tagged with 'Vue.js'[4] or directly to me.
Thanks specifically to Jazmin Tanner, who has played an essential part
in gathering inputs from all stakeholders and interested groups in
synthesizing the charter.
Also to Stephen Niedzielski as a thoughtful driver of the Vue.js
Search Case Study – one of the first major milestones. And generally,
thanks to all members of FAWG, WMDE, Product and Technology department
teams (Reading Web, Editing, Growth, Language, Multimedia, Design,
Core Platform, Performance) involved and leadership for continuous
strong support of this wide-reaching project.
Best,
Volker
[0] - https://www.mediawiki.org/wiki/Vue.js/Migration_Project_Charter
[1] - https://www.mediawiki.org/wiki/Platform_Evolution
[2] - https://phabricator.wikimedia.org/project/view/4767/
[3] - https://www.mediawiki.org/wiki/Talk:Vue.js/Migration_Project_Charter
[4] - https://phabricator.wikimedia.org/tag/vue.js/
Hi,
we've released v0.39.0 of the OOUI library this Tuesday. It will rollout on
the
normal train next Tuesday, 26 May.
Highlights in this release:
- Text flow of form layouts on mobile devices was improved, surfaced
in Advanced Mobile Contributions
- Additionally this release removed deprecated icons 'beaker' and
'unTrash', both were renamed, former to 'labFlask', latter to
'restore'. Additionally 'toc' in 'icons-layout' was deprecated in this
release, as design team has decided to use 'listBullet' as unified
table of contents icon.[0]
- Added option in PopupWidget to remove close button and add custom icon to
widget head. Thanks to volunteer contributor Sohom Datta!
- Remove `onLookupMenuItemChoose` event in LookupElement. It got deprecated
in v0.35.2. Use onLookupMenuChoose instead.
- TagItemWidget: Remove `setDisabled` function. It was deprecated in
v0.27.0.
Please look through your code, if you still occur to use them.
- Underlying library OOjs was updated to v5.0.0, up from v3.0.1,
nominally a breaking change.
Also, as new features of OOUI v0.38.0, ButtonMenuSelectWidget and
IndexLayout.php#setTabPanel was newly implemented.
You can find details on additional new features, code-level, styling
and interaction design amendments, and all improvements since v0.38.0
in the full changelog[0].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[1] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.39.0
MediaWiki version: 1.35.0-wmf.34
Date of deployment to production: Regular train, starting Tuesday 26 May
[0] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.39.0/History.md
[1] -
https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker