-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Official providers All provider's logo is not proper showing #10327
Comments
This issue was marked with the This means that it is a good candidate for someone interested in contributing to the project, but does not know where to start. Have a look at the Contributing Guide first. This will help you set up your development environment to get started. When you are ready, open a PR, and link back to this issue in the form of adding Please make sure that - if applicable - you add tests for the changes you make. If you have any questions, feel free to ask in the comments below or the PR. Generally, you don't need to Note There is no need to ask for permission "can I work on this?" Please, go ahead if there is no linked PR 🙂 |
is this issue still open ? if yes , how do i get to this file? |
For now, the only thing I found is that the images are hosted on authjs.dev site ( All of this was found inside of |
Dark style logos were removed in #10542 as they were sparsely used anyway, so the dark mode part of this issue is probably redundant now |
The github and okta logos are still not resembling the theme. |
@Bisxsh They have removed dark styled logos from the application, not from the docs (which is referred in this issue) |
What is the improvement or update you wish to see?
According to the mode of the site, logo colors should change. If dark mode is enabled then the logo should be white and the same for the opposite.
some logos are not loaded properly
Is there any context that might help us understand?
No
Does the docs page already exist? Please link to it.
https://authjs.dev/getting-started/providers
The text was updated successfully, but these errors were encountered: