Page MenuHomePhabricator

RHo (Rita Ho)
User

Projects (22)

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

User Since
Mar 23 2016, 6:05 PM (420 w, 3 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
RHo (WMF) [ Global Accounts ]

Recent Activity

Fri, Apr 12

RHo moved T362455: Investigate Penpot as a Figma alternative from Incoming to Doing on the Wikimedia-Design board.
Fri, Apr 12, 10:11 PM · Design, Wikimedia-Design
RHo created T362455: Investigate Penpot as a Figma alternative.
Fri, Apr 12, 10:11 PM · Design, Wikimedia-Design
RHo added a comment to T362433: UX testing training and inclusion plan.

Thanks for putting up this task @GEscalante-WMF. One aspect of the plan to note is clarifying (I hope) that this is not a *complete* transition away from design research from doing any the usability testing, but capacity building for designers to be able to take on more of the work.
It would be important to set a rubric/prioritisation/triage system as there will continue to be projects requiring a design researcher to execute.

Fri, Apr 12, 8:13 PM · Design-Research, Research (FY2023-24-Research-April-June)

Thu, Apr 11

RHo assigned T361978: Graphic design request: Publication of P&T FY24-25 OKRs to DTorsani-WMF.

Assigning to @DTorsani-WMF to lead per discussion today 👏🏻

Thu, Apr 11, 9:25 PM · Design, Wikimedia-Design
RHo updated subscribers of T340456: Tooltip: Add Tooltip component to Codex.
Thu, Apr 11, 1:35 PM · Growth-Team, Wikimedia-Design, Design, Design-System-Team (Design-System-Product-Roadmap), Codex

Fri, Apr 5

RHo added a comment to T361978: Graphic design request: Publication of P&T FY24-25 OKRs .

Creating a intake request task for review

Fri, Apr 5, 9:02 PM · Design, Wikimedia-Design
RHo moved T361978: Graphic design request: Publication of P&T FY24-25 OKRs from Incoming to Needs discussion on the Wikimedia-Design board.
Fri, Apr 5, 9:00 PM · Design, Wikimedia-Design
RHo created T361978: Graphic design request: Publication of P&T FY24-25 OKRs .
Fri, Apr 5, 9:00 PM · Design, Wikimedia-Design
RHo removed a member for Wikimedia-Design: MNovotny_WMF.
Fri, Apr 5, 8:40 PM
RHo removed a watcher for Wikimedia-Design: RHo.
Fri, Apr 5, 8:39 PM
RHo added a watcher for Wikimedia-Design: RHo.
Fri, Apr 5, 8:38 PM

Thu, Apr 4

RHo updated the task description for T361376: Volunteer Archetypes: Design Research exploration toward v1.
Thu, Apr 4, 1:47 PM · Research (FY2023-24-Research-April-June), Design, Wikimedia-Design

Tue, Apr 2

RHo moved T361376: Volunteer Archetypes: Design Research exploration toward v1 from Incoming to Tracking on the Wikimedia-Design board.
Tue, Apr 2, 4:10 PM · Research (FY2023-24-Research-April-June), Design, Wikimedia-Design
RHo updated subscribers of T361376: Volunteer Archetypes: Design Research exploration toward v1.
Tue, Apr 2, 4:10 PM · Research (FY2023-24-Research-April-June), Design, Wikimedia-Design
RHo added a project to T361376: Volunteer Archetypes: Design Research exploration toward v1: Wikimedia-Design.
Tue, Apr 2, 4:10 PM · Research (FY2023-24-Research-April-June), Design, Wikimedia-Design

Wed, Mar 27

RHo added a comment to T277189: Consider applying 960px max-width to Newcomer Homepage.

My two cents is we should consider this change broadly on Special pages, esp with full width dashboard or table content rather than doing for each special page.

Wed, Mar 27, 3:13 PM · Web-Team-Backlog, Wikimedia-Site-requests, Growth-Team-Filtering, Growth-Team, Desktop Improvements (Vector 2022)

Fri, Mar 22

RHo moved T141801: WikimediaUI (Codex/OOUI) icon inventory (tracking) from Needs discussion to Tracking on the Wikimedia-Design board.
Fri, Mar 22, 3:25 PM · Design-System-Team, Codex, Tracking-Neverending, Design, Wikimedia-Design, OOUI
RHo removed a project from T1193: Polish : paragraph text should not have typographic orphans: Design.
Fri, Mar 22, 3:22 PM · Design, MediaWiki-Parser, Wikimedia-Design
RHo closed T1189: Polish : Credit card input form should reflect organization of credit card as Declined.

Declining as nothing has happened in close to a decade.

Fri, Mar 22, 3:20 PM · Design, Fundraising-Backlog, Wikimedia-Design
RHo moved T141801: WikimediaUI (Codex/OOUI) icon inventory (tracking) from Tracking to Needs discussion on the Wikimedia-Design board.
Fri, Mar 22, 3:18 PM · Design-System-Team, Codex, Tracking-Neverending, Design, Wikimedia-Design, OOUI
RHo merged T85682: Investigate desktop TOC alternatives into T273473: [Epic] Improve the table of contents.
Fri, Mar 22, 3:18 PM · Web-Team-Backlog (Kanbanana-FY-2021-22), Epic, Desktop Improvements (Vector 2022)
RHo merged task T85682: Investigate desktop TOC alternatives into T273473: [Epic] Improve the table of contents.
Fri, Mar 22, 3:17 PM · Design, Wikimedia-Design
RHo moved T292757: Design branding and logo for Codex from Doing to Needs discussion on the Wikimedia-Design board.
Fri, Mar 22, 3:15 PM · Design, Design-System-Team, Codex, Design-Systems-team-20200324-20220422 (Codex Milestone), Wikimedia-Design
RHo added hashtags to Wikimedia-Design: #wmf-ux, #wmf-product-design.
Fri, Mar 22, 3:11 PM
RHo added a comment to T360367: Grant Access to ldap/wmf for Katie Coleman.

Hi @Fabfur - Confirming @KColeman-WMF should have access to Superset and Turnilo – and Grafana too. Thank you! :)

Fri, Mar 22, 2:16 PM · Patch-For-Review, SRE, LDAP-Access-Requests

Thu, Mar 21

RHo awarded T349044: Evaluate how we want to represent "Patterns" in Codex a Party Time token.
Thu, Mar 21, 10:08 PM · Design, Epic, Design-System-Team (Design-System-Product-Roadmap), Codex

Wed, Mar 20

RHo renamed T256190: Update footer image links on all MediaWiki skins to be legible and accessible from Remove or remodel small site ownership icons which are used in every MediaWiki skin to Update footer image links on all MediaWiki skins to be legible and accessible.
Wed, Mar 20, 6:04 PM · Web-Team-Backlog (FY2023-24 Q4 Sprint 2), Wikimedia-Design, Design, MediaWiki-General, Accessibility
RHo added a comment to T256190: Update footer image links on all MediaWiki skins to be legible and accessible.

The context is that if you visit any page in desktop, at the bottom there are two buttons that show "this is part of wikimedia movement" (movement awareness) and "this is powered by mediawiki" (software trademark).

grafik.png (957×1 px, 339 KB)

The issues:

  • It doesn't show up in mobile
  • it is too small
  • It is PNG
  • the design is subpar (the old apple key look?)
  • the link to wikimedia project goes to the foundation. Brand team said it'd be better for that to link to https://wikimedia.org but that aforementioned page needs a complete redesign (and more prominent link to wmf)

There are also discussions to be had around the larger footer issues. e.g. parts of the footer that's missing in mobile and lack of any branding to "wikimedia" or "wmf" in mobile. The legal text being different in mobile and desktop and generally many more footer clean ups that can be done. But I'd assume that is outside of scope of this ticket

Wed, Mar 20, 2:49 PM · Web-Team-Backlog (FY2023-24 Q4 Sprint 2), Wikimedia-Design, Design, MediaWiki-General, Accessibility

Mar 13 2024

RHo updated the task description for T333681: Establish consistent guidelines on how to visualize diffs across desktop, mobile web, and mobile apps.
Mar 13 2024, 9:28 AM · MediaWiki-Page-diffs, Accessibility, Wikipedia-iOS-App-Backlog, Wikipedia-Android-App-Backlog, Design-System-Team

Mar 1 2024

RHo added a comment to T358296: [UX] No obvious way to close notice dialog telling me that I'm using the Parsoid view experimental feature.

Hi there, looks like a big in the link displaying as white text on mobile notification (officewiki)

Screenshot_20240301-084550~2.png (471×1 px, 56 KB)

Mar 1 2024, 7:54 AM · Content-Transform-Team-WIP, MW-1.42-notes (1.42.0-wmf.20; 2024-02-27), MediaWiki-User-Interface (mw.notifications), Parsoid-Read-Views

Feb 28 2024

RHo added a comment to T345921: LoadingIndicator: Add LoadingIndicator component to Codex.

Additional usage on Commons MediaSearch:

image.png (1×2 px, 306 KB)

Feb 28 2024, 12:19 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo attached a referenced file: F42209886: image.png.
Feb 28 2024, 12:18 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo attached a referenced file: F42209896: image.png.
Feb 28 2024, 12:17 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo attached a referenced file: F42209959: image.png.
Feb 28 2024, 12:17 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo attached a referenced file: F42209967: image.png.
Feb 28 2024, 12:17 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo attached a referenced file: F42209916: image.png.
Feb 28 2024, 12:16 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo attached a referenced file: F42209927: image.png.
Feb 28 2024, 12:16 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex
RHo updated subscribers of T345921: LoadingIndicator: Add LoadingIndicator component to Codex.

Known use cases

image.png (622×1 px, 38 KB)
Special:RecentChanges/RCFilters
Watchlist/RC filter loading panel
Screenshot 2023-09-08 at 16.22.57.png (230×456 px, 23 KB)
Wikibase Date input component: the loader indicates that the input is being processed

The Indeterminate Progress Bar implemented in Codex communicates that a process is happening. The elevated bar communicates an ongoing process on a page, while the inline bar communicates it within other components.

Captura de pantalla 2024-02-28 a las 11.41.42.png (1×1 px, 106 KB)

The use cases described in this task for BouncingDots could potentially be addressed using elevated and inline progress bars. Unless there are additional use cases that necessitate BouncingDots, we may consider not implementing this component.

Feb 28 2024, 11:56 AM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex

Feb 27 2024

RHo updated subscribers of T338015: Module: Add Module component to Codex.

Does this actually need to be a component? What if we provided guidelines or documented this as a pattern instead? I'm not sure what value creating a dedicated component for this brings that can't be done through a combination of existing tokens and components.

I lean towards creating it as a Codex component. A Module or Content Box is a versatile container for different types of content. You can find some examples in this Figma inventory. I also explored how to handle all these use cases with a single Module component in this exploration where you can check how we could cover many the different use cases with one single component.

Captura de pantalla 2024-02-19 a las 20.02.21.png (592×1 px, 339 KB)

There are many benefits to building it as a component But in case we don't want to create it as a component for now, we can start by providing design guidelines. Later on, we can turn those guidelines into a component if we find more situations where it's useful.

Either way, we will need to define and document the following:

  • What type of content can be included within a Module
  • The paddings in the Module, according to the size of the Module (paddings will vary on small and large modules).
  • Color and style
  • How the Module's head will look like and what type of content will have (title, action?)
  • Where to place any buttons or actions
Feb 27 2024, 3:34 PM · Design-System-Team, Codex

Feb 26 2024

RHo awarded T357498: Non-autocreated temp accounts creations do not appear in Special:Log a Like token.
Feb 26 2024, 1:35 PM · MediaWiki-Platform-Team (Radar), MediaWiki-Core-AuthManager, Temporary accounts

Feb 20 2024

RHo updated subscribers of T357837: Remove non-public/WMF-specific resources from Codex content writing resources page.

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.

I think if we feel this is all still relevant and accurate (which I imagine we do since we were linking to it in resources) then we can totally consider revising our Voice and tone guidelines to reflect this and surface this guidance. Would we would need to note in the revision that these specific aspects are in collaboration with WO?

Feb 20 2024, 8:57 PM · Design-System-Team (DST-Sprint-17 (2024-02-20 to 2024-03-01)), Codex, Documentation, Wikimedia-Design, Design
Volker_E awarded T357837: Remove non-public/WMF-specific resources from Codex content writing resources page a Like token.
Feb 20 2024, 6:09 PM · Design-System-Team (DST-Sprint-17 (2024-02-20 to 2024-03-01)), Codex, Documentation, Wikimedia-Design, Design

Feb 16 2024

RHo updated the task description for T357837: Remove non-public/WMF-specific resources from Codex content writing resources page.
Feb 16 2024, 11:14 PM · Design-System-Team (DST-Sprint-17 (2024-02-20 to 2024-03-01)), Codex, Documentation, Wikimedia-Design, Design
RHo created T357837: Remove non-public/WMF-specific resources from Codex content writing resources page.
Feb 16 2024, 11:13 PM · Design-System-Team (DST-Sprint-17 (2024-02-20 to 2024-03-01)), Codex, Documentation, Wikimedia-Design, Design

Feb 13 2024

RHo added a project to T355914: Change default image thumbnail size: Wikimedia-Design.

@DTorsani-WMF and @JScherer-WMF - per @Ladsgroup suggestions, wondering if you both can offer any ux recommendations for recommended thumbnail sizing (250px, or higher). Seems like this would be beneficial to research if it may apply across all wikis, not only enwiki.

Feb 13 2024, 12:52 PM · Web-Team-Backlog, Design, Wikimedia-Design, Thumbor, Traffic, SRE-swift-storage, Data-Persistence, SRE, Wikimedia-Site-requests
RHo updated the task description for T355914: Change default image thumbnail size.
Feb 13 2024, 12:52 PM · Web-Team-Backlog, Design, Wikimedia-Design, Thumbor, Traffic, SRE-swift-storage, Data-Persistence, SRE, Wikimedia-Site-requests

Feb 9 2024

RHo updated subscribers of T280724: Add form layout guidelines to DSG.

@DTorsani-WMF - can this task be merged into T330481 ? Thanks!

Feb 9 2024, 10:43 PM · Wikimedia Design Style Guide, Design
RHo added a comment to T356351: Accordion with InfoChip.

Would suggest this be considered for putting into the planned "Badge" component T280708 instead since this fits in with the definition as something which is "Small indicator of status or count" which is not interactive for the user (whereas it seems like a chip in Codex defo is an interactive input).

Feb 9 2024, 9:20 PM · Design, Codex, Design-System-Team
RHo updated the task description for T280708: Badge: Add Badge component to Codex.
Feb 9 2024, 9:15 PM · Design, Design-System-Team (Design-System-Product-Roadmap), Codex

Jan 29 2024

RHo updated the task description for T329963: Provide guidelines on when to choose which basic interaction element in Codex.
Jan 29 2024, 7:32 PM · Design-System-Team (DST-Sprint-15 (2024-01-22 to 2024-02-02)), Documentation, Design, Wikimedia-Design, Wikimedia Design Style Guide, Codex

Jan 24 2024

RHo closed T355766: Mediaviewer download options not showing the file size data as Resolved.
Jan 24 2024, 10:37 PM · MediaViewer
RHo added a comment to T355766: Mediaviewer download options not showing the file size data.

What do you get when running mw.config.get('wgHostname') in the console?

I get 'mw1477'

Jan 24 2024, 10:27 PM · MediaViewer
RHo added a comment to T355766: Mediaviewer download options not showing the file size data.

Interesting... fwiw still happening for me consistently in different browsers on different images

Jan 24 2024, 6:22 PM · MediaViewer
RHo created T355766: Mediaviewer download options not showing the file size data.
Jan 24 2024, 11:51 AM · MediaViewer

Jan 18 2024

RHo attached a referenced file: F37805499: image.png.
Jan 18 2024, 4:08 PM · Design-System-Team, Codex, Web-Team-Backlog, Desktop Improvements (Vector 2022)
RHo attached a referenced file: F37805501: image.png.
Jan 18 2024, 4:08 PM · Design-System-Team, Codex, Web-Team-Backlog, Desktop Improvements (Vector 2022)
RHo attached a referenced file: F37805504: image.png.
Jan 18 2024, 4:08 PM · Design-System-Team, Codex, Web-Team-Backlog, Desktop Improvements (Vector 2022)

Jan 17 2024

RHo added a comment to T332849: [Spike] Investigate form generation options for community configuration.
Research notes

One of the first questions that has come up is whether it would be more appropriate to render the form on the server or the client. It clearly depends on the system requirements we want to enforce. In preliminary conversations with @Urbanecm_WMF we did not find a clear advantage of building the form on the server. These are the alternatives we have studied:

Considered options

  • HTMLForm (server): same setup as current EditGrowthConfig. Makes use of HTMLForm (OOUI display) and FormSpecialPage. Requires ad-hoc logic for generating a form descriptor that matches HTMLForm descriptors.
  • Codex + custom components (client): make use of existing Codex components (TextInput, Checkbox, etc). Requires ad-hoc logic for generating a form descriptor that matches Codex components and also building ad-hoc controls, eg: a wiki page selector
  • jsonforms + Codex renderers (client): leverage the form generation logic to jsonforms and create a set of vue renderers using Codex components and styling.

Below some comparison of the pros and cons

Server

Pros

  • Support for no-JS experience
  • Reduced loading times and minimal payload
  • Existing form infrastructure

Cons

  • Still requires some JS for client validation
  • No SSR or hydratation for Codex
  • Integrating a third party tool for form description with HTMLForm seems challenging
Client

Pros

  • Opportunity to use Codex and latest DSG
  • Opportunity to leverage form generation to a third party tool

Cons

  • No existing form building infrastructure
  • Increased loading time and payloads
Conclusions

After playing a little more with jsonforms I find the library could be appropriate for externalizing the form generation logic and have a high degree of form customization while using the latest MW UI technology available (Vue/Codex). This path would require a non trivial amount of work to create a minimal set of control and layout renderers but it would save us from writing form generation logic based on JSON schemas. On the other hand if we keep using HTMLForm, the current support of Codex in CodexHTMLForm with css-only components seems not ready for a CommunityConfiguration MVP. A fair amount of work is required to achieve the same UX than OOUI provides at the moment.

Regardless of the rendering technology we pick up, the "uischema" concept (used in jsonforms and other libs) seems on point for the problem we want to solve. It does not need to be necessarily written in JSON but such concept could allow to both to work with HTMLForm and jsonforms (or other form renderers).

Jan 17 2024, 9:03 PM · Growth-Team (Sprint 10 (Growth Team)), CommunityConfiguration, Design-System-Team, GrowthExperiments-CommunityConfiguration (2.0), Spike

Jan 16 2024

RHo added a comment to T354774: Publish the usability testing guidelines in a public place.

I believe we do want to include this publicly after checking to remove/generalise any WMF-specific process, services, etc. One question though is whether to include in Design Style Guide / Codex site, or whether it is more apt on the design.wikimedia.org site that can be linked from Codex in the appropriate section.

Jan 16 2024, 4:48 PM · Design-System-Team, Epic, Design, Codex

Jan 15 2024

RHo updated the task description for T353073: Design: Evaluate the need to create a library of Project templates in Figma.
Jan 15 2024, 8:27 PM · Design, Codex, Design-System-Team

Jan 4 2024

RHo added a comment to T343680: Figma upgrades: include size & spacing variables and the new auto layout in the Codex library.

My take on the open question:

Is it worth applying min-max width to OOUI components library? Or do we want to apply min-max width just to Codex components one?

I'm unsure of the scope/effort required to perform this update in general. But if the goal is to bring the behavior of design components closer to the code, in order to satisfy the user story, then I'd say that the requirement applies to both design libraries, OOUI and Codex.

Jan 4 2024, 10:44 AM · Design, Codex, Design-System-Team

Jan 3 2024

RHo added a comment to T353618: TextInput: Include "date" input type in Figma spec.

Note that usage of this input type occurs in products maintained by at least the following designer-supported teams:

  • T&S Product team (eg., Special:Block),
  • Campaigns (eg., Event registration)
  • Structured Content (eg., Image upload > Date)
  • Abstract Wikipedia (Wikifunctions)
Jan 3 2024, 9:44 AM · Wikimedia-Design, Design, Codex, Design-System-Team
RHo created T354246: [Low] Mentor dashboard module info icon misaligns.
Jan 3 2024, 9:29 AM · GrowthExperiments-Mentorship, GrowthExperiments-MentorDashboard, Growth-Team
RHo added projects to T354243: Visual design bugs: UI fixes to the Send Praise settings dialog: GrowthExperiments-MentorDashboard, Design.
Jan 3 2024, 9:24 AM · GrowthExperiments-Mentorship, Design, GrowthExperiments-MentorDashboard, Growth-Team
RHo created T354243: Visual design bugs: UI fixes to the Send Praise settings dialog.
Jan 3 2024, 9:24 AM · GrowthExperiments-Mentorship, Design, GrowthExperiments-MentorDashboard, Growth-Team
RHo added a comment to T332849: [Spike] Investigate form generation options for community configuration.

Hi @Sgs - from Product Design team and Design Systems perspective I think it would be a resounding yes to improving for a Codex version. Please do reach out to Design-System-Team if there is support that may be needed from DST (code and design-wise)!

Jan 3 2024, 8:55 AM · Growth-Team (Sprint 10 (Growth Team)), CommunityConfiguration, Design-System-Team, GrowthExperiments-CommunityConfiguration (2.0), Spike
RHo updated subscribers of T348805: Create dashboard for viewing edits Edit Check was activated within.

Adding @KStoller-WMF for ref as one of the suggested features for Community Configuration was enabling access to analytics for to help with decision-making on product feature configuration.
Separately, would it make sense to standardise and centralise analytics UIs like this which may relate to work being done by Data Products ?

Jan 3 2024, 8:50 AM · Goal, EditCheck, Editing-team (Kanban Board)

Jan 2 2024

RHo updated subscribers of T328385: "Year in Review" for Wikipedia Contributions.

adding @JTannerWMF as this is something that has been brewing for a while on the apps

Jan 2 2024, 2:39 PM · Web-Team-Backlog, Growth-Team, Editing-team

Dec 6 2023

RHo created T352903: Wireframes/Design for A/B Testing workflows.
Dec 6 2023, 6:48 PM · Design, Wikimedia-Design
RHo moved T85682: Investigate desktop TOC alternatives from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Design, Wikimedia-Design
RHo moved T85966: Define in a clear way what we currently store about users for explaining how recommendation system would work from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Design, Wikimedia-Design, WMF-Legal
RHo moved T86225: Graphics on the login and create account forms are not SVG from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Design, UI-Standardization, Wikimedia-Design, MediaWiki-User-login-and-signup
RHo moved T88581: Notify that your article has been translated by another user from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Growth-Team-Filtering, Growth-Team, Design, OKR-Work, Notifications, Wikimedia-Design, ContentTranslation
RHo moved T87867: Experiment ways to get more users to translate articles (tracking) from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Design, OKR-Work, Wikimedia-Design, Tracking-Neverending, ContentTranslation
RHo moved T91783: Improve branding / design of Echo notifications from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Growth-Team-Filtering, Design, Growth-Team, Wikimedia-Design, Notifications
RHo moved T89650: Request a translation for an article (or collection of articles) from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:39 PM · Design, OKR-Work, Wikimedia-Design, ContentTranslation
RHo moved T89654: Propose a short sequence of articles to translate from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · OKR-Work, Design, Wikimedia-Design, ContentTranslation
RHo moved T89697: After an article has been created, suggest translating it to another language from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, OKR-Work, Wikimedia-Design, ContentTranslation
RHo moved T139866: Year input fields on special pages should be 4 digits wide from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · CSS, Wikimedia-Design, MediaWiki-User-Interface, Design, MediaWiki-Special-pages
RHo moved T103901: Translate the updates to existing articles as a micro-contribution from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Microcontribution, Design, OKR-Work, ContentTranslation, Wikimedia-Design
RHo moved T155197: OOUI directional icons should have prefixes for semantics and organization from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · OOUI, Wikimedia-Design, Design
RHo moved T77894: Release thumbnail border design changes from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, Wikimedia-Design, MediaWiki-General
RHo moved T156664: Find a low-level, contributor friendly and performant translation/internationalization solution for the style guide from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · I18n, Wikimedia-Design, Design, Wikimedia Design Style Guide
RHo moved T129433: Improve design for wiki-facing error pages from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · User-Frostly, Wikimedia-Design, Voice & Tone, Design
RHo moved T148579: Define and implement DropdownWidget font-weight consistently from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-Design, UI-Standardization, UI-Standardization-Kanban, Design
RHo moved T156531: Ensure usage of SVGs where applicable from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-Design, Wikimedia Design Style Guide, Design
RHo moved T170899: Rollback favicon from black to colourful for chapters wikis from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-Design, Design, Wikimedia-Site-requests
RHo moved T164863: Change MediaWiki:sig-text to use a proper dash instead of two hyphen-minuses from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-Design, Design, MediaWiki-General
RHo moved T162329: Audiences well addressed? from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-Design, Wikimedia Design Style Guide, Design
RHo moved T166201: Guidelines for signifying button actions: Actions, Popups, unfold etc. from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design-System-Team, Codex, Design, Wikimedia-Design
RHo moved T13477: Don't mark external links to the current wiki as external from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · patch-welcome, Design, Wikimedia-Design, Parsing-Team--ARCHIVED, MediaWiki-Parser, Technical-Debt
RHo moved T184022: Ensure indicators use same canvas as icons from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, Wikimedia-Design, OOUI
RHo moved T1016: SVG attachments are not displayed from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, Wikimedia-Design, Upstream, Phabricator (Upstream)
RHo moved T217363: Consider minimizing the presence of Partial Blocks UI elements on Special:Block from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · User-notice, MediaWiki-Blocks, Patch-For-Review, User-DannyS712, MediaWiki-User-Interface, Wikimedia-Design, Design, Anti-Harassment
RHo moved T78022: in pholio mockups it is not possible to reply in-line to a comment from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, Wikimedia-Design, Upstream, Phabricator (Upstream)
RHo moved T209100: Pholio mock comments are not featuring persistent links from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, Upstream, Wikimedia-Design, Phabricator (Upstream)
RHo moved T216520: Alternative Wikidata logo for social media and circular frames from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · WMF-Communications, Wikimedia-Design, Logos, Wikidata, Design, WMF-Legal
RHo moved T180837: Take down livingstyleguide.wmflabs.org from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Design, Wikimedia-Design
RHo moved T215162: Compile case studies showcasing the design process at WMF from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-Design, Design
RHo moved T218148: Icon design for programmatic banners from Incoming to Needs discussion on the Wikimedia-Design board.
Dec 6 2023, 6:38 PM · Wikimedia-CentralNotice-Administration, Design, Wikimedia-Design