Page MenuHomePhabricator

Homepage: layout and UI fixes
Open, Needs TriagePublic

Description

This task is a central place to address outstanding Newcomer homepage layout and UI fixes that haven't been surfaced elsewhere or don't need a specific phabricator task.

A list of UI fixes (current -- could be updated in the future) has been collected and prioritized in the following spreadsheet file:
https://docs.google.com/spreadsheets/d/1FXTiZX8ogKG3WLYZgZaQHdrzN-WLXi5ZNa8tPTqEBSI/edit?usp=sharing

The reference mockups can be accessed at:

Related Objects

StatusAssignedTask
OpenNone
OpenSBisson
ResolvedSBisson
OpenSBisson
OpenSBisson
OpenNone
ResolvedSBisson
OpenSBisson
OpenJTannerWMF
OpenSBisson
ResolvedSBisson
ResolvedSBisson
OpenSBisson
Openkostajh
ResolvedSBisson
ResolvedSBisson
OpenNone

Event Timeline

Cntlsn created this task.Aug 7 2019, 11:47 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 7 2019, 11:47 AM

FYI @Cntlsn, I deleted the row about the mentor introductory message being in quotes, because we have a more complex rule: it should be in quotes if the mentor wrote it, but not in quotes if it's the default message (since the default message is not a quote).

Cntlsn added a comment.Aug 8 2019, 9:56 AM

@MMiller_WMF sounds good, thanks for the correction!

@Cntlsn thank you for creating this, but could you please create one task per issue? It's important for 1) being able to associate patches with specific tasks that contain the relevant history (as opposed to what is now a private spreadsheet), 2) makes QA and code review easier since the reviewer just needs to evaluate one thing, in context 3) makes the tasks more easily distributed.

RHo added a comment.Aug 12 2019, 11:33 AM

@Cntlsn thank you for creating this, but could you please create one task per issue? It's important for 1) being able to associate patches with specific tasks that contain the relevant history (as opposed to what is now a private spreadsheet), 2) makes QA and code review easier since the reviewer just needs to evaluate one thing, in context 3) makes the tasks more easily distributed.

hi @kostajh - sorry that was my bad! I asked @Cntlsn to file UI bugs prioritized in one task first, so that y'all could review together and break out into smaller bug tasks to fix according to priority and feasibility. Assuming that all the line items are fine to log as separate tickets, @Cntlsn can you please file as subtasks this parent "UI fixes" task? Thanks and sorry for the bad phabbing!

Thanks @RHo and @kostajh, happy to break the list into single phab tasks.
A couple of questions before doing the work:

  • what would be the right column where to move all the tasks I create?
  • what would be the best way to highlight tasks priority? Triaging each task directly?

what would be the right column where to move all the tasks I create?

I think Ready for Development, since this one is there currently

what would be the best way to highlight tasks priority? Triaging each task directly?

Maybe just use High/Normal/Low in the phabricator priority field for each indvidual task?

thank you!

phuedx moved this task from Needs triage to Growth on the Mobile board.Aug 15 2019, 11:11 AM

This is actually an epic so I am moving this to the correct column