Add a docs favicon

[virgile-dev]

Bug Report

Problematic behavior
As a user I want to identify easily the browser tabs that are docs.
Right now Docs has La Marianne, which is not generic nor indicates clearly which website it is.

Expected behavior/code
I'd like to have a Docs favicon.
It should be easily overidable so that admin sys deploying docs can easily add they own favicon (the nav bar logo should be overidabel as well)

Additional context / Screenshots

The Favicon could be derived from this:

@rl-83 could you propose a design for the favicon please ?

[rl-83]

https://www.figma.com/design/hPwxE24MEaX3mBQ0KXNTSY/UI-La-Suite?node-id=248-10408&t=l7Jfw92KbBzFfTcz-1

[virgile-dev]

Hey @rl-83 perfect. I don't have edit access to the figma in edit. Can you export it for me in .svg (color and black and white) ? thanks

[rl-83]

[virgile-dev]

@rvveber any idea we can make that easily overidable at build time like you did for the logo ?

[rvveber]

@virgile-dev I will take a look to find an elegant solution when i have time. Probably next week.
I was testing all kinds of methods the last two weeks.
But i haven't found something, that is easy and universal yet.

The problem is, that favicons, just like tsx modules, will be compiled into optimized files that can be served to the browser. (As it should be) this happens before/when the Image is created.
So the image contains only production optimized, minified code.
All files will be combined, renamed, compressed etc.

When an admin wants to host the image he only has access to the finished image.
He can create files in the image at runtime, but it's essentially useless because the node application has already been compiled, it does not look for them, and also can't read uncompiled code.

In the scope of favicons, it's possible, we can instruct the node application to look for the file dynamically.
But it would be at runtime not at build time

[rvveber]

So what an admin needs to do, to get his overrides at built-time

1. is to pull the src from a specific version
2. replace files, with modified files, while keeping their original names
3. and build the image from the modified source
4. that he then releases(locally) and uses in his deployment.

[virgile-dev]

Ideally, it'd be great that you don't have to this in a fork using config files and env variables
In another project I worked on we only do overrides (translations, themes etc.) in a deployment repo.
Have you explored this direction ?