Conversation
|
👀 does this also apply to Client? |
@donnie-msft yes! this would apply anywhere the current blue checkmark is shown |
|
@JonDouglas I really like the other icon that you proposed, I would definitely like to add that to the discussion of potential icons. I do, however, see the potential for people to associate it with the existing tags concept on NuGet mistakenly. Perhaps some customer research could be done here about the icon options? I did consider the idea of doing away with the icon all-together (probably should have mentioned this in the proposal, thank you for calling it out!) However, I thought that keeping an icon present would still retain the importance of prefix reservation for security reasons and keep things consistent with what users are used to. I do think that this is a good option to consider though! Would love to get some more opinions |
nkolev92
left a comment
There was a problem hiding this comment.
Great write-up!
I like the icon in this proposal, but I like the icon in what @JonDouglas proposed as well.

I don't have an opinion about the text beyond real estate considerations.
I have a slight preference towards the icon I linked.
JonDouglas
left a comment
There was a problem hiding this comment.
This lgtm. May want to do a quick team review to finalize the settled concept & merge.
|
@albarry4 - How can we validate the icons with customers ahead of making the change? |
| @@ -0,0 +1,81 @@ | |||
| # ***Replacing the Blue Checkmark*** | |||
| <!-- Replace `Title` with an appropriate title for your design --> | |||
There was a problem hiding this comment.
Should these comments really be left in?
|
Why was this PR abandoned? Seems useful @albarry4 |



Rendered Spec