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

[Project] Getnighthawk Logo update for Project Grid #1794

Closed
vinayaksh42 opened this issue Apr 18, 2021 · 4 comments · Fixed by #1797
Closed

[Project] Getnighthawk Logo update for Project Grid #1794

vinayaksh42 opened this issue Apr 18, 2021 · 4 comments · Fixed by #1797
Labels
kind/chore Necessary task

Comments

@vinayaksh42
Copy link
Member

Current Behavior
The old logo of Getnighthawk is currently on the Project Grid page

chrome_8GiA6JJjbW

Desired Situation
Update it to the new logo of getnighthawk. You can find the suitable files required for this at https://layer5.io/company/brand or simply link it with the already existing logo at https://github.com/layer5io/layer5/blob/master/src/assets/images/getnighthawk/icon-only/SVG/getnighthawk-logo.svg

The Logo already exists in the assets.


[Optional] Alternatives

[Optional] Additional context


Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

@vinayaksh42 vinayaksh42 added the kind/chore Necessary task label Apr 18, 2021
@adithyaakrishna
Copy link
Member

@vinayaksh42 Can You Assign this to Me?
If it's okay will fix this issue as part of PR #1767

@vinayaksh42
Copy link
Member Author

@adithyaakrishna that PR already refers to 2 different issues. It would be better if you open a separate PR for this issue so that it is easy to review it.

@adithyaakrishna
Copy link
Member

Okay Sure @vinayaksh42

@adithyaakrishna
Copy link
Member

@vinayaksh42 Could you please assign this to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/chore Necessary task
Development

Successfully merging a pull request may close this issue.

2 participants