-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Labels
ADOConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionRFERequest For Enhancement AKA feature requestRequest For Enhancement AKA feature requestSTYStyle/polish/CSS, or think of it as in pigsty or an eyesoreStyle/polish/CSS, or think of it as in pigsty or an eyesoreUVIUser-Visible ImprovementUser-Visible Improvement
Description
Here's an off-the-cuff proposal -- help with filling in actual hex codes solicited!
- No due date -- obnoxious neon yellow
- Overdue -- neon pink [1]
- Due in <24h -- bright red
- Due in <2d -- orange
- Due in <3d -- blue
- Due in >=3d -- green
- Due in >=7d -- darker green
- Completed -- black
- Failed (cf Uncle button AKA "mark as failed" #248) -- dark red, almost black
- Newly created -- gray [2]
Footnotes
[1] Or show little flames or sirens or something? Blinking would be too much but some kind of subtler animation somehow? Actually the realtime ticking down of the score may be exactly the ticket. And maybe that's the answer for no due date: a blinking "N/A" for the score to goad you into picking a due date to make the godawful blinking stop. :)
[2] This would be moot if we drop create-on-GET but I don't like making the promise gray like in the status quo. Instead, the background of the whole webpage should be a different color or something. Just some unimportant but obvious difference to indicate that the promise has been created.
Metadata
Metadata
Assignees
Labels
ADOConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionConsensus needed on what to Actually Do (or "much ado about ∅"), AKA questionRFERequest For Enhancement AKA feature requestRequest For Enhancement AKA feature requestSTYStyle/polish/CSS, or think of it as in pigsty or an eyesoreStyle/polish/CSS, or think of it as in pigsty or an eyesoreUVIUser-Visible ImprovementUser-Visible Improvement