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
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...
Answer
#4: Post edited
by
trichoplax
·
2023-01-20T17:53:58Z (over 1 year 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:
- []()
- ## 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:
- []()
#3: Post edited
by
trichoplax
·
2023-01-20T01:10:08Z (over 1 year 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:- []()
- ## 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:
- []()
#2: Post edited
by
trichoplax
·
2023-01-20T01:09:25Z (over 1 year 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: 
- ## 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:
- []()
#1: Initial revision
by
trichoplax
·
2023-01-20T01:08:35Z (over 1 year 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: 