Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Post History

75%
+4 −0
Q&A Unique favicons for each site

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 (th...

posted 2y ago by trichoplax‭  ·  edited 2y ago by trichoplax‭

Answer
#4: Post edited by user avatar trichoplax‭ · 2023-01-20T17:53:58Z (almost 2 years ago)
Typo
  • ## In support of unique favicons
  • ### A common logo to bring the communities together
  • In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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 as 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](https://en.wikipedia.org/wiki/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:
  • []()![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)
  • ## In support of unique favicons
  • ### A common logo to bring the communities together
  • In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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](https://en.wikipedia.org/wiki/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:
  • []()![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)
#3: Post edited by user avatar trichoplax‭ · 2023-01-20T01:10:08Z (almost 2 years ago)
Add two spaces to prevent image being brought back onto the line above
  • ## In support of unique favicons
  • ### A common logo to bring the communities together
  • In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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 as 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](https://en.wikipedia.org/wiki/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:
  • []()![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)
  • ## In support of unique favicons
  • ### A common logo to bring the communities together
  • In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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 as 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](https://en.wikipedia.org/wiki/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:
  • []()![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)
#2: Post edited by user avatar trichoplax‭ · 2023-01-20T01:09:25Z (almost 2 years ago)
Add newline to account for formatting difference between preview and saved post
  • ## In support of unique favicons
  • ### A common logo to bring the communities together
  • In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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 as 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](https://en.wikipedia.org/wiki/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: ![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)
  • ## In support of unique favicons
  • ### A common logo to bring the communities together
  • In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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 as 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](https://en.wikipedia.org/wiki/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:
  • []()![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)
#1: Initial revision by user avatar trichoplax‭ · 2023-01-20T01:08:35Z (almost 2 years ago)
## In support of unique favicons
### A common logo to bring the communities together
In response to [another answer](https://meta.codidact.com/posts/277432/277442#answer-277442), 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 as 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](https://en.wikipedia.org/wiki/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: ![The Codidact favicon looking smaller than others](https://meta.codidact.com/uploads/oz20hvilxk89p04y2yji0zj7e2vy)