-
Notifications
You must be signed in to change notification settings - Fork 34
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
Replace the Logo of Layer5 with Meshery in config.yml workflow #109
Comments
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack. |
Hi @anshgoyalevil can I work on this? |
Thanks for asking out. Please get it assigned to you from a maintainer. After that, you can create a PR. |
@leecalcote can I work on this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
Description
Currently, we are using the Logo of Layer5 instead of Meshery. This repository is under the organization Meshery, so, there should be the image of Meshery.
How to resolve this?
Go to .github and replace this welcome image with the new one:
Make sure to display the images conditionally, based on the theme selected by user.
Here's the sample code:
New images are:
Download these images, and upload with an appropriate name. Make sure to use conditional rendering as described above.
After uploading the image, and removing the previous image, go to .github/config.yml folder and update the reference to previous image to the new image in the following part:
Here, replace
![Congrats!](https://raw.githubusercontent.com/meshery/meshery.io/master/.github/welcome/Layer5-celebration.png)
with the codemake sure to change the image sources with the path to image in the folder where you upload it.
Contributor Guides and Handbook
The text was updated successfully, but these errors were encountered: