imApoorva36 commented 10 months ago

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 apply

[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How 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 apply

[ ] Test A
[ ] Test B

Checklist

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.

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

imApoorva36 commented 10 months ago

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 :)

imApoorva36 commented 10 months ago

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.

nishant-nayak commented 10 months ago

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