Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More different logo #2

Closed
jcbhmr opened this issue Dec 16, 2023 · 3 comments
Closed

More different logo #2

jcbhmr opened this issue Dec 16, 2023 · 3 comments

Comments

@jcbhmr
Copy link
Member

jcbhmr commented Dec 16, 2023

might I suggest a logo that more clearly differentiates @typst-community from @typst? Specifically: at a small size "t" with "community" written in size 8 font sideways is quite hard to differentiate vs the official @typst logo. The turquoise vs white color difference is good though! I think it might be better with something like "tc" instead of "t"? Just to differentiate https://typst.community or whatever other site in your browser tab favicon from https://typst.app. as-is, the "t"-on-turquoise and "t"-on-white look like "main site" and "docs" versions lol

ex:
image

cc @huwaireb since im not sure if you're watching this repo https://github.com/typst-community/.github/watchers

@huwaireb
Copy link
Member

The original PoC was exactly the second one, however I didn't really like how it turned out at the time so I decided to go with another approach the one you see now:

Differentiate by colors and the community lettering offers visual distinction even if not readable.

Branding needs to be redone sooner or later, imo it's fine if we just keep the one we have now and hold a poll later with the community with more variants as well. Although that is blocked by finishing setting up the typst-community org.

Probably would be before the site is live, which is what matters the most in this case due to favicon of course.

@huwaireb
Copy link
Member

should we move this to a discussion? @jcbhmr

@jcbhmr
Copy link
Member Author

jcbhmr commented Jan 11, 2024

did this ever get decided one way or the other? keep/change?

@huwaireb huwaireb transferred this issue from typst-community/.github Jan 24, 2024
@typst-community typst-community locked and limited conversation to collaborators Jan 24, 2024
@huwaireb huwaireb converted this issue into discussion #3 Jan 24, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants