마크다운은 텍스트 기반의 마크업 언어로 쉽게 쓰고 읽을 수 있다. HTML로 변환도 가능하다. 특수 기호와 문자를 이용한 간단한 구조의 문법을 사용해 웹에서도 빠르게 콘텐츠를 작성하고 직관적으로 인식된다. 최근 마크다운이 각광받기 시작한 이유는 깃허브에서 사용하는 README.md의 영향이다. 마크다운을 통해 사용 방법, 코드 설명, 이슈 등을 간단히 기록할 수 있고, 가독성이 높다는 장점이 부각되면서 점점 여러 곳에서 사용되고 있다.
---
title: 'When to Use Static Generation v.s. Server-side Rendering'
date: '2020-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.
You can use Static Generation for many types of pages, including:
- Marketing pages
- Blog posts
- E-commerce product listings
- Help and documentation
You should ask yourself: "Can I pre-render this page **ahead** of a user's request?" If the answer is yes, then you should choose Static Generation.
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.---
title: 'Two Forms of Pre-rendering'
date: '2020-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.
- **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 let's 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.반응형
