Mg/landing page* Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features) (N/A)
[x] Docs have been added / updated (for bug fixes / features) (N/A)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Housekeeping
What is the current behavior? (You can also link to an open issue here)
Assets are located in /content/asset per Gatsby guidelines
Current favicon is Vercel logo, which is not actually being used in the Document
Leftover static files output by Gatsby remain in /public directory
What is the new behavior (if this is a feature change)?
/asset directory moved to /public/asset (NextJS serves static files from /public at the root path).
/cou directory moved to /public/asset/cou
Leftover Gatsby output files in /public are removed
/public/favicon.ico changed to CFT sticker (which conveniently has the smallest file size)
<link> added for favicon in SeoHead.tsx component.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
An asset in /public, e.g. /public/asset/mypic.jpg should now be imported at the top level from /public/asset/mypic.jpg, or referenced in-line at /asset/mypic.jpg (for instance, <img src="/asset/mypic.jpg">).
Existing imports have been updated accordinglly.
Other information:
The SeoHead.tsx component is currently implemented at the page level. Because NextJS Merges the contents inside <Head></Head> tags, we may also want to implement it at the layout level or in /src/pages/_app.tsx to apply global head tags. (Adding the key attribute to tags prevents their duplication. In the case of matching key attributes, latest wins).
Mg/landing page* Please check if the PR fulfills these requirements
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes / features) (N/A)
[x] Docs have been added / updated (for bug fixes / features) (N/A)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Housekeeping
What is the current behavior? (You can also link to an open issue here)
/content/assetper Gatsby guidelines/publicdirectoryWhat is the new behavior (if this is a feature change)?
/assetdirectory moved to/public/asset(NextJS serves static files from/publicat the root path)./coudirectory moved to/public/asset/cou/publicare removed/public/favicon.icochanged to CFT sticker (which conveniently has the smallest file size)<link>added for favicon inSeoHead.tsxcomponent.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
An asset in
/public, e.g./public/asset/mypic.jpgshould now be imported at the top level from/public/asset/mypic.jpg, or referenced in-line at/asset/mypic.jpg(for instance,<img src="/asset/mypic.jpg">).Existing imports have been updated accordinglly.
Other information:
SeoHead.tsxcomponent is currently implemented at the page level. Because NextJS Merges the contents inside<Head></Head>tags, we may also want to implement it at the layout level or in/src/pages/_app.tsxto apply global head tags. (Adding thekeyattribute to tags prevents their duplication. In the case of matchingkeyattributes, latest wins).