Getting a 404 on console for favicon.

[LilyLME]

GEThttp://localhost:5000/favicon.png
[HTTP/1.1 404 Not Found 0ms]

[wlach]

I believe this is web browser default behaviour to just check for this, so we're not seeing this because of anything we're doing wrong. That said, we should create/add a favicon at some point for sure.

[LilyLME]

Great, whenever that's (favicon) available, I would just go ahead and add it then.

[acmiyaguchi]

It's actually missing from the project (as opposed to being browser behavior).

glean-dictionary/public/index.html

Line 9 in df3b400

<link rel="icon" type="image/png" href="/favicon.png" />

[LilyLME]

OPTION ONE

OPTION TWO

OPTION THREE

@wlach What do you think here?

[LilyLME]

The rough edges would be cleared, so each template is just to give an idea.

[wlach]

@LilyLME Sorry for the late reply on this. I think ideally we would have unique branding for the Glean dictionary but I think this is definitely better than nothing. Option (2) looks good to me, it probably will look reasonable when scaled down. @Dexterp37 @mdboom does this seem like reasonable use of the glean assets to you?

[Dexterp37]

@LilyLME Sorry for the late reply on this. I think ideally we would have unique branding for the Glean dictionary but I think this is definitely better than nothing. Option (2) looks good to me, it probably will look reasonable when scaled down. @Dexterp37 @mdboom does this seem like reasonable use of the glean assets to you?

@wlach yes, Option (2) looks good to me too! FWIW:

• This is the favicon from the currently deployed https://glean-dictionary.netlify.app/ .
• If that's not good enough, we also have vector-based Glean assets to derive the favicon from.

[wlach]

Oh right, I didn't even think about looking at the early glean dictionary! Moving ahead with option (2) by just copying what's in https://glean-dictionary.netlify.app/ seems like the best option -- I believe it's stored here: https://github.com/mozilla/probe-dictionary/tree/sveltify/public . Thanks @LilyLME for exploring the solution space -- I think this issue is now open if someone wants to look at it.