Skip to content
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

added new logo #2157

Merged
merged 1 commit into from
Jun 9, 2024
Merged

added new logo #2157

merged 1 commit into from
Jun 9, 2024

Conversation

sdushantha
Copy link
Member

The logo was created by the Kali Linux team and gave us permission to use it.

In addition to the new logo, the ./images/ directory has been moved to into ./docs/ in order to make the root directory of the project cleaner. The old preview.png was never used as we had been using a preview image that was hosted on user-images.githubuesrcontent.com. This too has been changed so that we use the local copy instead

The logo was created by the Kali Linux team and gave us permission to
use it.

In addition to the new logo, the ./images/ directory has been
moved to into ./docs/ in order to make the root directory of the project
cleaner. The old preview.png was never used as we had been using a
preview image that was hosted on user-images.githubuesrcontent.com. This
too has been changed so that we use the local copy instead
Copy link
Collaborator

@matheusfelipeog matheusfelipeog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice logo. Good job by the Kali Linux team.

After the merge (which will force GitHub to load the images and create a link from their CDN), we should change the src to the full links provided by GitHub instead of the relative path. This is so that the images can be viewed if the README.md is loaded somewhere else on the internet.

@matheusfelipeog
Copy link
Collaborator

@ppfeister
Copy link
Member

If the CDN links expire, then proper fully-qualified links to the raw img in the repo should work as well. But using the CDN is actually a pretty good idea if it's long-lived. Curious if there's any load time differences and if the fully qualified url ultimately redirects to the CDN anyways. I also wonder if there's any negative to it or if it's really just there to use...

@sdushantha
Copy link
Member Author

But using the CDN is actually a pretty good idea if it's long-lived.

I'm unsure about this. I've seen people link to the CDN in READMEs but the link returns 404 even though the image is in the repo. I'll merge this for now, but we can decide later if using the CDN is something we should opt for

@sdushantha sdushantha merged commit d678908 into master Jun 9, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants