Lead Design System Architecture efforts.
User Details
- User Since
- May 7 2015, 3:20 PM (471 w, 1 d)
- Availability
- Available
- IRC Nick
- Volker_E
- LDAP User
- Unknown
- MediaWiki User
- Volker E. (WMF) [ Global Accounts ]
Today
Yesterday
Given the small maximum size of the SVGs I'd recommend to
- to reduce the numeric precision to 2 decimals (hope we keep the original somewhere)
- lowercase, in these two SVGS only, the hex colors for slightly better gzipping
That would save 1kb un-gzipped and def some bytes after.
Thu, May 16
Wed, May 15
Tue, May 14
Thanks for the quick turnover @bmartinezcalvo
Repeating from patch for general visibility:
I feel like content overflow is more a visual style belonging to Typography or even better “Layout guidelines” than being such important overarching design principle.
I'm not fully on page yet. Two questions/inputs:
- Wouldn't we do this consistently for all documentation pages? We have these titles across all components and on overview pages like components, icons, design tokens. Guessing that was the plan, but the patch is not flagged as 'work in progress' and we could end up currently with only a few pages changed, instead of all at once.
- Given our current documentation page layout, I think it's a really good idea to repeat the title again. It provides a mental anchor point for the readers switching through a number of our documentation. So for example instead of “When to use” “When to use Tables”.
Mon, May 13
@CCiufo-WMF Email to wikitech-l is sent out!
Sun, May 12
@Sarai-WMDE On “sorting icons display incorrect color”. Would it probably be useful to provide extra clearance for users, by emphasizing the sorted up and sorted down icons over the normal non-hierarchical ones?
Thanks for reporting @Daimona!
While I see the WCAG guidelines as guiding principles, as in 4.49:1 vs 4.5:1 is not a fail in my opinion, I assume that we could change the color slightly to also make automated tests not chew up on this every time it's encountered. cc: @DTorsani-WMF
Sat, May 11
@Izno I've uploaded the exported Google doc as PDF for you to download.
Fri, May 10
It could possibly as simple as putting aria-live="polite" on .cdx-chip-input__chips listbox.
Thu, May 9
Wed, May 8
As much as we should unify terminology, I'm torn between unifying and negatively impacting readability of names beyond just technical terminology. Reading
“These external links must use the external link icon, cdxIconLinkExternal, in addition to the text to denote a destination outside of the current domain.” vs
“These external links must use the external link icon 'linkExternal', in addition to the text to denote a destination outside of the current domain.”
I prefer latter.
An alternative would be to have another column in “All icons” to include a name and then a code column.
A rule of thumb for good user-interface is that icons only move when the movement is intended to provide the user feedback and consistent.
That's not the case here, and therefore jarring.