Some UX cleanups for package claiming

[chadwhitacre]

Part of #4305, follows on #4422.

• gray out the wombat so it feels more like a default
• add an npm indicator in project listings
• knock out Float "Fund Your Project" button as on homepage #4394 please

[chadwhitacre]

Working up a new default image (no wombat):

     

Started with:

https://www.iconfinder.com/icons/730810/box_order_package_parcel_post_postage_shop_icon

[chadwhitacre]

In situ:

Now for npm indicator ...

[chadwhitacre]

More in situ:

---

---

[chadwhitacre]

With the npm indicator we're coming back up against the discrepancy between the social profile listings and the project listings. I'm still not going to worry about harmonizing those yet.

[chadwhitacre]

---

---

[mattbk]

🤤

[chadwhitacre]

14000e9

[chadwhitacre]

Short

Medium

Long

[chadwhitacre]

gratipay=# select name, char_length(description) as len from packages order by len desc limit 10;
┌──────────────────┬─────┐
│       name       │ len │
├──────────────────┼─────┤
│ tower-view       │ 939 │
│ jquery-cropbox   │ 842 │
│ shubhadownloader │ 771 │
│ perstore         │ 749 │
│ schematic        │ 719 │
│ pomelo-protobuf  │ 689 │
│ resume-generator │ 615 │
│ clever-survey    │ 585 │
│ platformenv      │ 577 │
│ JSDev            │ 563 │
└──────────────────┴─────┘
(10 rows)

gratipay=#

[chadwhitacre]

Lol

[chadwhitacre]

Maybe we will need to vary text size based on content length?

[chadwhitacre]

For comparison: webpack 227, mysql 110, aspen 61.

[chadwhitacre]

41d0f64

[chadwhitacre]

The opposite case. 7b71a4f

[chadwhitacre]

Next up: styling unclaimed package for auth!

🤢

[kaguillera]

!m @whit537
Looks good so far.

[chadwhitacre]

[chadwhitacre]

gratipay=# select name, array_length(emails, 1) as n from packages where array_length(emails, 1) is not null order by n desc limit 10;
┌───────────────────┬────┐
│       name        │ n  │
├───────────────────┼────┤
│ colonel-mercator  │ 68 │
│ mapbox-file-sniff │ 66 │
│ ec2mnt            │ 66 │
│ mbview            │ 65 │
│ cfn-config        │ 64 │
│ vector-tile-query │ 64 │
│ kine              │ 64 │
│ guidance-replay   │ 61 │
│ guidance-geojson  │ 60 │
│ guidance-sim      │ 60 │
└───────────────────┴────┘
(10 rows)

[chadwhitacre]

[chadwhitacre]

Right, so in reality almost all addresses will be "Ready to link" for some time to come.

[chadwhitacre]

Working on a dropdown component (also useful for add social profile and country selector in identity page and … ?)

[chadwhitacre]

07d7e81

[chadwhitacre]

Okay! That was a bit of a rabbit hole, and we're not clear yet. :-)

Obviously this is still a ways from being finished, and this PR is getting big. I am thinking I will break this into multiple PRs, since there's still more to add. I'm also not sure what's going to happen when I look at this dropdown component on a phone. Could turn into a total mess.

[mattbk]

Normal dropdowns usually degrade to mobile-friendly versions (essentially what you have) on mobile; is there a way to force that, or is there no check-for-mobile anywhere on the site?

[chadwhitacre]

Okay, claim form styling (inc. custom dropdown) broken out into #4410. Slew of todos moved back up to #4305.

[kaguillera]

A little concern I have with the claiming of a package. Not sure if it should be stated her but just want to put it somewhere.
Any one of the maintainer's can claim the package, what if it is a maintainer that does not do much work on the package? Would that not be unfair? Should we leave the resolutions of that unfairness to the group of maintainers to resolve?

[chadwhitacre]

Worked this through a bit w/ @kaguillera IRL.

• Package projects still go through a review process.
• If we notify all other maintainers then that mitigates the issue, especially if we link to the review ticket.

[chadwhitacre]

Rebased, was 7b71a4f.

[mattbk]

Should we leave the resolutions of that unfairness to the group of maintainers to resolve?

I think we should, at least at this stage (crossposted at #4305 (comment)).

[dowski]

I'm rusty on my CSS. Feel free to get another pair of eyes on this.

[chadwhitacre]

I think we just proceed with merging if you're good, @dowski. If there's nothing downright dangerous going on here then I think we're within our risk tolerance. :)