Implement admin for Primary Hero Shelf

[jvillalobos]

Part of this PRD.

The Primary Hero Shelf in the homepage will feature one extension, chosen from a subset of Recommended extensions:

Since this will only work with Recommended extensions, it seems sensible to extend the admin we already have for it.

For the admin of a Recommended extension, add:

• Featured Image, chosen from a pool of predetermined images.
• Background color, used for the gradient.
• Featured on Primary Hero Shelf, checkbox that adds or removes the extension from the set. The checkbox shouldn't be toggled on if the other two properties haven't been set, or if the extension is only in the Recommendable state. There should always be at least one extension with the checkbox turned on.

[jvillalobos]

The background color will be chosen from a fixed palette, to be provided by @brassy- here.

[jvillalobos]

It should also be possible to feature unlisted Recommended extensions in the homepage (and we most likely will at launch). The Call to Action will point to the homepage URL, so having one set should be another requirement to enable the checkbox in the admin, for unlisted ones.

[eviljeff]

It should also be possible to feature unlisted Recommended extensions in the homepage (and we most likely will at launch).

Okay, we could have an additional setting which would mark the item as referring to an unlisted-only add-on and then frontend would know to display it differently.

Unlisted versions can't be approved for recommended though, currently, so it's not possible to have an add-on without a listed version be recommended - that's #1806. (And we'd be referring the user to an install that wouldn't be marked in Firefox as recommended)

[eviljeff]

The background color will be chosen from a fixed palette

would this be defined by two colours if it's for a gradient (a start and an end colour)?

[bobsilverberg]

The background color will be chosen from a fixed palette

would this be defined by two colours if it's for a gradient (a start and an end colour)?

What I recall from the last meeting we had is that there will always be a single color that represents the start of the gradient, and then each gradient will be defined as having a different end color. If that is the case then the user would only need to choose one color for the gradient (the end color).

Can @jvillalobos and/or @brassy- confirm or deny this?

[eviljeff]

The start and end colours will both need to be defined somewhere though, I assume. As the API would be returning one colour value I thought it may as well return both. I think we're basically blocked on someone telling us at least one "gradient", and we can see how it's best represented (to the user the admin; and in the api., which may be different)

[bobsilverberg]

The start and end colours will both need to be defined somewhere though, I assume. As the API would be returning one colour value I thought it may as well return both. I think we're basically blocked on someone telling us at least one "gradient", and we can see how it's best represented (to the user the admin; and in the api., which may be different)

It does seem like the API should return both colors, and then they only ever need to be defined in one place (the server).

[brassy-]

Meanwhile, here the 5 different gradients. The colors are coming from the new brand palette.

[eviljeff]

alright, unblocked!