Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Unique favicons for each site
Could each site have its own favicon? When I have too many tabs open and can't read the page titles, it'll help me distinguish the different sites.
What about as a compromise using the book as favicon but colored in the color of the corresponding sub domain?
3y ago
The idea is pretty nice. This post of mine has become a duplicate of this one, which has the same premise as this. An …
3y ago
In support of unique favicons A common logo to bring the communities together In response to another answer, which say …
2y ago
Multiple favicon is an awesome idea for people participating in multiple sites. However it has a very important disad …
4y ago
4 answers
What about as a compromise using the book as favicon but colored in the color of the corresponding sub domain?
0 comment threads
The idea is pretty nice. This post of mine has become a duplicate of this one, which has the same premise as this.
And as I love the idea, I actually made (kinda crappy)[1] icons for these existing sites. Also in chat (Discord), some of these icons I created became the basis of newer emojis:
These are most likely the icons to be put in place when we think we should get a favicon for a site. It's not mandatory, as they say, but if a bunch support it, then they'll get what they want. A site without a favicon will have the default Codidact logo.
Notes:
- [1]: In "kinda crappy", I mean that some of these images on the repo are quite blurry since the softwares I use for making them caused some weird stuff.
- [2]: The first 4 emojis are not logos of the communities, except for the default Codidact logo. 101, amen, and the Codidactyl are not logos of the sites.
0 comment threads
In support of unique favicons
A common logo to bring the communities together
In response to another answer, which says:
it has a very important disadvantage of diluting the platform image (the book) when being reached by newcomers
If it is considered important to have the Codidact logo (rather than a specific community logo) on every community, then that seems like a reason to have it in the body of the page rather than in the favicon. The favicon is tiny, especially on higher resolution screens. The favicon is also not visible to mobile users.
For these reasons I would recommend viewing the favicon as navigation rather than promotion, and address separately any need for overall platform promotion[1].
Letting each community form its own identity
Personally I would prefer to emphasise a specific community to a new user, and let the "community of communities" which is Codidact be something they discover later as they settle in. Codidact communities are separate for a reason - they benefit from having a common interest and expertise. A subset of each community will take an interest in Codidact as a whole and participate on Meta Codidact, but I wouldn't want to push that and detract from the identity of the specific community.
For this reason I'd like to see a unique favicon per community, in the same way that each community has a unique logo at the top of the page. There could perhaps be a general Codidact favicon as a backup until a new community gets its own favicon.
As the general Codidact favicon would presumably be used for Meta Codidact, and not only be a backup, I'd also like to see it reworked to better fill the space available for a favicon[1:1].
-
If the favicon is to be used to promote site cohesion for new users, then I would suggest that it would benefit from being made to better fit the format of a favicon. The logo is in isometric projection, which looks good in the Codidact panel in the sidebar, where it is larger. However, in a favicon it leaves a lot of empty space, which makes the Codidact favicon look significantly smaller than most:
↩︎ ↩︎
0 comment threads
Multiple favicon is an awesome idea for people participating in multiple sites.
However it has a very important disadvantage of diluting the platform image (the book) when being reached by newcomers.
For that reason, for the time being it shouldn't be a mandatory change, but rather an option and very importantly disabled by default.
2 comment threads