Lead Design System Architecture efforts.
User Details
- User Since
- May 7 2015, 3:20 PM (462 w, 4 d)
- Availability
- Available
- IRC Nick
- Volker_E
- LDAP User
- Unknown
- MediaWiki User
- Volker E. (WMF) [ Global Accounts ]
Yesterday
@stijn Thanks, you're right. I've misunderstood just based on the last comments.
This is already the case and in place since 2015:
https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/refs/heads/master/resources/src/mediawiki.less/mediawiki.mixins.less#179
Sat, Mar 16
Fri, Mar 15
Tue, Mar 12
Sun, Mar 10
Thu, Mar 7
Wed, Mar 6
One thing to keep in mind with treating "legacy" as mode: there are already theme-wikimedia-ui-legacy.less files in use in Translate and Universal Language Selector extensions since regards to removing 'mediawiki.ui' vars.
This file was meant to be updated continuously in the extensions needing them. With the modes, we have to change what we're providing there. Reason for putting them there was that we wanted the two with their old MediaWiki support pre v1.38. As we're talking Translate seems to be adapted to use skin vars, so it's a one extension only issue.
“Red Link” has got a semantic meaning within Wiki community, even though it features a color. It's only used for this action in Wikiverse.
One of the reason this came up was folks have designed for English and not taken i18n into consideration when designing before min-width.
Tue, Mar 5
Currently the notification from Parsoid original implementation (thanks @cscott for filing this task and reaching out) uses the subtle Message background. But these kind of toast notifications shouldn't be using a neutral message background IMO. The notification “toast” message is better in a white background territory there. cc: @bmartinezcalvo
Thanks for coming back to this, unifying makes a lot of sense here.
I'd be against default as I'd refer to an unstyled HTML link by “default” ;)
I'd also don't think that “progressive” is a good fit in the case of a link even though it features the same color in the default theme, as we also don't say “destructive” for the “Red Link” as it's not general progression we're describing with a “base” Link in contrast to the progressive Buttons.
I'd go for “base” as we use the term for our baseline in many different cases.
Mon, Mar 4
Fri, Mar 1
Thu, Feb 29
Tue, Feb 27
Thu, Feb 22
What is exactly meant with utf-8 encoding, the utf8 piece in the data URI?
Wed, Feb 21
Tue, Feb 20
For https://docs.google.com/presentation/d/1xeLgj9f1BS4HYYdDMkoHIge3SJtoiXBLHkx-NixhgKg/edit#slide=id.g4bab39e9b0_0_0 it might make sense to update and expand our Voice & Tone guidelines. I'd like to hear @bmartinezcalvo's and @DTorsani-WMF's inputs here.
Note, that the double arrows need to fit into the 20px canvas, which means the height is limited, so 12px might be too small to fit both in height with distance gap. Also I think the gap should be tried to be more than 1px in order to make it easier recognizable.
That's in connection with T341632: [EPIC] Palette customizations and dark mode and even T26070: [GOAL] Provide a dark / night mode skin or theme. We could use this task for the specific addition of dark mode/night mode colors to Codex design tokens.
On 4.1.a. we should require a caption, but make it AT/screenreader only visible through a prop.
On 3.1. I'd strongly suggest taking a path that will enable us to generalize pagination later. I see more UX commonalities than differences in table and other pagination.
Just passed by a detailed article on pagination design in general that captures a number of thoughts that went into existing paginations and might be helpful here again.
Thanks @Izno!
Mon, Feb 19
All actionable quests have been resolved. Not putting it back to the DST Sprint for Codex 1.2.0, released at 2023-12-19 but leaving in this sprint.
Sun, Feb 18
Feb 15 2024
One concern to take into consideration is how to deal with MediaWiki as platform, with external skin authors, how to tackle and communicate a possible unification like html { font-size: 100% } [or html { font-size: 62.5% }.
Feb 14 2024
Removing WikimediaUI-Base as we'll only bring changes to the unified Codex design tokens from here on, although they are originated in former.
With DSG deprecated and on its way out, declining this. T357544: Establish a low-level, contributor friendly and performant translation/internationalization solution for Codex is equivalent successor.
@matmarex Do you find your answer in the newly provided https://doc.wikimedia.org/codex/main/style-guide/using-links-and-buttons.html#weight?
Without further information from the task author and the font stack in use in these scripts with the single voice raised here, declining until more information is raised.