Recipes in Drupal core should have a logo for findability in Project Browser/Starshot

I think we need some kind of differentiation as to which ones would show up on the UI and which ones are too low level. Then we don't need the icons for the low level ones.

As an ambitions site builder, wouldn't I want the ability to discover everything I can do with Drupal?

I agree that the installer should list only certain recipes to start, and even an initial load of project browser. But I feel like I should be able to filter/expand to see all available options.

Adding 📌 Decide and update recipe naming and classification standards Needs review as a dependency as the recipe's type, or other classification will most likely need to be used in determining which recipes are available to Project Browser's filters and the installer.

I can see a difference between "it made sense to break it down like this for code reuse" vs "this is a level of feature that makes sense for users". I think the later would need icons, the former I would not make people do icons, if they show up on the UI they could be very overwhelming. Eg. the full list of current core recipes is not all something the user level would expose I think. Maybe a (very) advanced setting.

Just wanted to make a few clarifications:

1. For the visuals/logos, do we need something fairly abstract or more indicative of the type of recipe? For example, the Starshot wires have 6 categories with a graphic representation/logo/icon. Should we continue with these type of visuals or be more abstract? It might be really hard to represent a specific recipe with an icon/logo.

2. Assuming recipes loaded through the Project Browser interface, and we are sticking to the card format that “regular modules” in Project Browser have? I am aware of the 512x512 PNG requirement, just wanted to confirm where these logos be showing.

3. Do we need a “default” logo/icon for the Recipes that will not have any visual? Sort of like an empty puzzle piece in Project Browser card?

4. Created a few quick visuals to get started with design direction. Note, intentionally staying away from cooking concepts and keeping things fairly abstract.

I think we need a "don't have an icon" icon yes. The mockups from the Starshot wireframes are not necessarily indicative IMHO of what we should end up with, that's up for definition. The icons will show up in a card type of interface too, since project browser will offer recipes in the full UI of project browser later in the site's life.

Here is an idea for the placeholder / "don't have an icon" logo.

Using the colors from the new Brand Guidelines → .

@zetagraph

For your #1) This issue is not about the Starshot recipes. Those recipes will most likely come from contrib and not Drupal core.

The Drupal core recipes can be found here: https://git.drupalcode.org/project/drupal/-/tree/11.x/core/recipes?ref_t...

But see the comments in #6; we haven't yet determined which of those recipes will need/should have images.

#2) At this time, I assume so, but work is ongoing in the Project Browser initiative to add support for recipes.

#3) If there were an issue and need for a "don't have an icon" logo, I believe it would also be in the Project Browser initiative.

@thejimbirch thanks for clarifications. Apologies if this confuses things. I was just trying to see if I can help with the visuals/graphics.

Adding a link to a conversation that was also happening in Slack here

Also, here are some "default logo" variations based on ^ that conversation:

Thanks for moving this along @zetagraph and @Gábor Hojtsy!

I posted this in the slack convo as there were some other voices there. Posting her for posterity and to continue the conversation.

Thanks folks for moving this along. I will update the issue also. I don't have any objections to using the initiative logo for the Standard recipe. However, what would a log look like for the Umami and Minimal (if we have one) recipes?

I think this should be postponed pending the wireframes/designs just so we have a better sense of what specifically is needed.

That said, I love your experiments @zetagraph, don't feedback here as discouragement for the future, it is just not the right timing yet :)

Thanks Gabor, yes I should have also said that :)

We hope to have wireframes soon and I just realised (from looking at the Slack thread) that @zetagraph you have already been in touch about helping out with those wireframes, so it is good to connect those dots!

All good, thanks for letting me know @gábor-hojtsy and thanks for connecting @pameeela.

We aren't exposing core recipes in Drupal CMS at this time, we are using some as dependencies but I can't see showing them in the UI since many of them directly conflict with the recipes that we ship with.

Un-postponing then as this is a Drupal core issue, not a Drupal CMS issue.