-
- {title}
-
+ {title}
diff --git a/basics/api-routes-starter/posts/pre-rendering.md b/basics/api-routes-starter/posts/pre-rendering.md
index de33130..3bf0c3e 100644
--- a/basics/api-routes-starter/posts/pre-rendering.md
+++ b/basics/api-routes-starter/posts/pre-rendering.md
@@ -1,6 +1,6 @@
---
-title: "Two Forms of Pre-rendering"
-date: "2020-01-01"
+title: 'Two Forms of Pre-rendering'
+date: '2022-01-01'
---
Next.js has two forms of pre-rendering: **Static Generation** and **Server-side Rendering**. The difference is in **when** it generates the HTML for a page.
@@ -8,4 +8,4 @@ Next.js has two forms of pre-rendering: **Static Generation** and **Server-side
- **Static Generation** is the pre-rendering method that generates the HTML at **build time**. The pre-rendered HTML is then _reused_ on each request.
- **Server-side Rendering** is the pre-rendering method that generates the HTML on **each request**.
-Importantly, Next.js lets you **choose** which pre-rendering form to use for each page. You can create a "hybrid" Next.js app by using Static Generation for most pages and using Server-side Rendering for others.
\ No newline at end of file
+Importantly, Next.js lets you **choose** which pre-rendering form to use for each page. You can create a "hybrid" Next.js app by using Static Generation for most pages and using Server-side Rendering for others.
diff --git a/basics/api-routes-starter/posts/ssg-ssr.md b/basics/api-routes-starter/posts/ssg-ssr.md
index fe4a156..b670ac3 100644
--- a/basics/api-routes-starter/posts/ssg-ssr.md
+++ b/basics/api-routes-starter/posts/ssg-ssr.md
@@ -1,6 +1,6 @@
---
-title: "When to Use Static Generation v.s. Server-side Rendering"
-date: "2020-01-02"
+title: 'When to Use Static Generation v.s. Server-side Rendering'
+date: '2022-01-02'
---
We recommend using **Static Generation** (with and without data) whenever possible because your page can be built once and served by CDN, which makes it much faster than having a server render the page on every request.
@@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque
On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request.
-In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.
\ No newline at end of file
+In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.
diff --git a/basics/assets-metadata-css-starter/pages/index.js b/basics/assets-metadata-css-starter/pages/index.js
index a245ddc..d9b5863 100644
--- a/basics/assets-metadata-css-starter/pages/index.js
+++ b/basics/assets-metadata-css-starter/pages/index.js
@@ -1,5 +1,4 @@
import Link from 'next/link'
-
import Head from 'next/head'
export default function Home() {
@@ -12,10 +11,7 @@ export default function Home() {
>
)
diff --git a/basics/basics-final/components/layout.js b/basics/basics-final/components/layout.js
index 92f0214..5049dfc 100644
--- a/basics/basics-final/components/layout.js
+++ b/basics/basics-final/components/layout.js
@@ -1,5 +1,7 @@
import Head from 'next/head'
import Image from 'next/image'
+import Script from 'next/script'
+
import styles from './layout.module.css'
import utilStyles from '../styles/utils.module.css'
import Link from 'next/link'
@@ -25,6 +27,13 @@ export default function Layout({ children, home }) {
+