-
Notifications
You must be signed in to change notification settings - Fork 9
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
modified seo tags #110
modified seo tags #110
Conversation
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.
Left a couple of comments. Additionally, I would recommend you look at what each meta
tag is really doing and what it represents. It is good information to know for SEO.
Maybe you can even add additional tags for updated SEO.
I have reverted with optimized content and I've also added all the images as required and added a favicon too Do let me know in case of any more changes if required :) |
Also I just realised that I also added the favicon, linked from issue #76 too, as it was as well along with the icons in the old website icons' collection. Just informing. |
If you can, can you also replace the text Corpus on the navbar with the IEEE NITK logo? The requirement is listed in #76 , if you can add that then we can close both issues in this PR |
ieee-nitkYour Livecycle playground is ready 🎉.✅ Playground version up to date (84733e0) Invite team members and start collaborating 💪 Check the box and click "invite" to invite collaborators
Click here to invite the rest of your team. |
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.
Requested some small UI changes.
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.
Description
Added the seo tags for the website
Fixes # (91)
Dependencies
List any dependencies that are required for this change.
Type of Change
What types of changes does your code introduce?
Put an
x
in the boxes that applyHow Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration. (for bug fix / breaking change)
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.