✨ Posts
This commit is contained in:
		
							
								
								
									
										14
									
								
								content/posts/initial.md
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										14
									
								
								content/posts/initial.md
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,14 @@ | ||||
| --- | ||||
| thumbnail: 'https://images.unsplash.com/photo-1707344088547-3cf7cea5ca49?q=80&w=2970&auto=format&fit=crop&ixlib=rb-4.0.3&ixid=M3wxMjA3fDF8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8fA%3D%3D' | ||||
| title: 'Two Forms of Pre-rendering' | ||||
| date: '2020-01-01' | ||||
| --- | ||||
|  | ||||
| # Woah! | ||||
|  | ||||
| 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 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. | ||||
		Reference in New Issue
	
	Block a user