Fix #1508: Port SEO from Gatsby to Nextjs

[hyunjiLeeTech]

Issue This PR Addresses

issue #1508

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI
• Port: Port Gatsby to Nextjs

Description

Port SEO from Gatsby to Nextjs. The run test is not passed because currently, '../hooks/use-site-metadata' module is not there. Except this issue, test will be passed.

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[humphd]

The site-metadata hook isn't going to work as is, since it uses graphql to talk to Gatsby. We'll have to figure out a plan for passing data into next components from the build statically, maybe as env variables or maybe using static props. I know that others are thinking about this too.

[hyunjiLeeTech]

I've checked the SEO.tsx file was not located in the correct folder. I moved the file into the /next/src/component folder. For the '../hook/use-site-metadata', I'm waiting somebody have done this part for the next :)

[tonyvugithub]

@hyunjiLeeTech : Hi there, we are in the process of reviewing these migrated to Next PRs. Just wonder if you are still interested to work on this as we would like you to make some changes to your PR. Please let us know in case you decided to drop this then we can assign the issue to others. Thank you.

[chrispinkney]

Closing due to #1566