|
85 | 85 | #### Server Actions |
86 | 86 |
|
87 | 87 | - Introduce "Server Actions" as a specific type of Server Function |
88 | | -- Provide context by mentioning plain old `<form>`s on the internet that are historically sent to a server for processing (we could say a "server function"!) |
89 | | -- Explain how attaching a Server _Function_ to an `action` makes it a Server _Action_ |
| 88 | +- Provide context by mentioning plain old `<form>`s on the internet that can be sent to a server for processing (we could call them "server functions"!) |
| 89 | +- Explain how attaching a Server _Function_ to a (form) `action` makes it a Server _Action_ |
90 | 90 |
|
91 | 91 | #### API Routes |
92 | 92 |
|
|
101 | 101 |
|
102 | 102 | - Introduce Vercel as the company behind Next.js, as well as a provider of cloud infrastructure |
103 | 103 | - Explain how Vercel's hosting options allow developers to host Next.js applications with very little effort |
104 | | -- Highlight that hosting on Vercel is perfect for a prototype or portfolio website built with React and/or Next.js |
| 104 | +- Highlight that hosting on Vercel is a good fit for a prototype or portfolio website built with React and/or Next.js |
105 | 105 |
|
106 | 106 | ### Connecting a GitHub Repository With Vercel |
107 | 107 |
|
108 | | -- Demonstrate in the browser how a **public** GitHub repository from your account can be connected to Vercel and deployed with the click of a button |
| 108 | +- Demonstrate in the browser how a **public** GitHub repository from ones account can be connected to Vercel and deployed with the click of a button |
109 | 109 | - Illustrate one way to get started with Vercel by installing the Vercel CLI globally `npm -g vercel` |
110 | 110 | - Show logging in to Vercel using `vercel login` and using ones GitHub account |
111 | 111 | - Show how one can deploy a local folder with a Next.js app using the `vercel deploy` CLI command |
112 | 112 |
|
113 | 113 | ### Limitations of Vercel |
114 | 114 |
|
115 | | -- Mention that Vercel apparently works best for hosting Next.js applications or static websites |
| 115 | +- Mention that Vercel probably works best for hosting Next.js applications or static websites |
116 | 116 | - Discuss how other frameworks are supported, but that the focus is likely on Next.js |
117 | 117 | - Mention that knowledge about DNS, domains, npm, dependencies etc. is not required, but useful when managing a site on Vercel |
118 | 118 | - Highlight that Vercel is well-suited for production applications, but that prices can apparently vary a lot based on usage |
|
0 commit comments