-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: overhaul branding and add new logo #6147
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
docs: overhaul branding and add new logo #6147
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
f6a22f8
to
873880c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love the look of the final form of the new logo now, great stuff!
Uses that instead of which - which I barely 51% confident as [Grammarly which-vs-that explainer]
Wow this explainer is actually really good and I genuinely wasn't familiar with this technicality between them, I think I'd always based it on "feel".
Standardizes the name as "TypeScript-ESLint", not "typescript-eslint" or "TypeScript ESLint"
This one really caught me off guard, it would have best to have discussed this first, I haven't seen it mentioned in our chats at all.
The name of the project is typescript-eslint and it always has been. That's the reason why this PR has had to make so many changes.
The onus would be on any proposed name change to justify why it would be better, but nevertheless here are some reasons why typescript-eslint has always been the choice:
-
It simply has to be written as typescript-eslint in so many important contexts
- domain name
- npm
- github
...so having an alternate casing of the same words is of questionable value and just creates noise.
-
TypeScript is how the TypeScript project is written, ESLint is how the ESLint project is written, so combining them together with a dash actually makes it less clear that a separate unique project is being referenced. Having typescript-eslint helps differentiate it in a sentence.
Please let's discuss these things going forward to avoid confusion 🙏
Again, love the new logo and thanks for improving my grammar!
I was hoping this PR would be the discussion! 😄 Your points make sense - I'll switch this to prefer typescript-eslint, and add that explainer in the docs. Thanks! |
These places all use all-lowercase by convention, but that might not be the canonical name of the product. ESLint uses all-lowercase in these three places as well; TypeScript uses all-lower in the former two, but that's only because Microsoft is weird and they like using CamelCase even in GitHub repos. |
"ESLint", | ||
"typescript-eslint" | ||
"typescript-eslint", | ||
"TypeScript" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No actual changes here, just sorting. It happens automatically sometimes anyway.
@@ -19,6 +19,7 @@ | |||
} | |||
|
|||
.sponsorsTier img { | |||
background: white; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tangentially related: I noticed sponsor logos such as Nrwl weren't showing up in dark mode. Branding!
Ohhh boy! |
Ok perfect, it's looking good! Please could we update these two (the navbar and the hero): Maybe for the hero we could add the logo in there to accompany the I'm totally fine if we want to bump a hero update to a follow up though and spend some more time on it... Other minor thing on the home page: I think that's our old logo rather than the actual TS logo (i.e. I don't think that's their color) |
Hmm yeah +1. I think I'd like to do that as a followup. There are a few different treatments we could try and I'm not solid on which one is best. 🤔
Ha! Yes. Changing.
Blurgh yeah I haven't been able to figure this one out: #6081. Thanks for the bump - pinging in that issue. |
How come this is just a black shape? |
@@ -66,7 +66,7 @@ const themeConfig: ThemeCommonConfig & AlgoliaThemeConfig = { | |||
], | |||
image: 'img/logo-twitter-card.png', | |||
navbar: { | |||
title: 'TypeScript ESLint', | |||
title: 'typescript-eslint', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JamesHenry @Josh-Cena this is why I'd gone towards solidifying as TypeScript-ESLint at first. IMO it looks a little odd to have the project name be lower-kebab-case on the homepage:
My logic was:
- I think it's good to keep the title casing & general phrasing consistent where possible
- For a project homepage, it makes sense to keep things in title case
- The hyphen is useful for showing it's a single project
- Therefore, TypeScript-ESLint is the logical conclusion
Comment reference to counterpoints: #6147 (review)
Thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can make the hero prettier in general in a follow up as we mentioned
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
webpack and many others have the same approach, but they mostly combine the word with the logo, we can do the same
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I've started playing with this locally and really like putting that logo there. I'll throw up a few examples soon 😄
packages/typescript-estree/tests/lib/__snapshots__/parse.test.ts.snap
Outdated
Show resolved
Hide resolved
FWIW, I like either |
@Josh-Cena The project's name was never in scope for changing as part of this work. One of the few luxuries afforded to me as the project's creator is that I get to decide what it is called :)
Likewise with this... it simply isn't the case. I called the project |
10efa72
PR Checklist
Overview