Starting this as task, might be transformed into a milestone or other form of Phab-compatible structure
Branding
Documentation
https://www.mediawiki.org/wiki/OOUI
- Restructure information and get rid of restructure notice
- Updating all imagery to HiDPI examples
- Comparison matrix to other libs – what value OOUI brings in the clearest form possible (SN)
- Use cases outside MW core: Here's the “Hello World” example to install Tutorials are written with such use case in mind
- Strengthen connection with interactive demos T118126
- Switch from jsduck to jsdoc
Code (–Mobile)
- Dialogs are too complex, should be revisited, something like SimpleDialog (MS) – major use case is gadgets right now T213476
- Process stuff seems overly complicated, API stuff (ES)
- Breaking out computation/calculation logic (f.e. floatable) as extra part, to be used elsewhere as well
Performance (–Mobile)
- T125292: Optimize how we load OOUI in MediaWiki
- “It's big”. “It comes with jQuery”. MobileFE tries to move away jQuery by utility file Main problem with $element property
“As underdog the lib has to present why adding jQuery and the bigger lib makes sense and is fine performance-wise”
QuickSurvey as an example
UX (–Mobile)