diff --git a/README.md b/README.md index 260a35c..27fddff 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# Nuxt Toolbox Template +# Nuxt Toolbox Template ## Build Setup @@ -40,13 +40,15 @@ You can also use `netlify deploy (--prod)` to manually deploy and `netlify open` ### Running Locally -You can use `netlify dev` from the command line to access project information like environment variables as well as +You can use `netlify dev` from the command line to access project information like environment variables as well as + - test functions - test redirects - share a live session via url with `netlify dev --live` - [and more](https://cli.netlify.com/netlify-dev/) :) ### Deployment Resources + - [CLI docs](https://docs.netlify.com/cli/get-started/) - [File-based Netlify Configuration](https://docs.netlify.com/configure-builds/file-based-configuration/) - [Netlify Dev Overview](https://www.youtube.com/watch?v=RL_gtVZ_79Q&t=812s) @@ -110,10 +112,13 @@ For this to work we also need to add a `netlify-honeypot` attribute to the form In the [`netlify.toml`](./netlify.toml) configuration file there is an example of how to implement redirects. Redirects can be used to do many things from redirecting Single Page Apps more predictably, redirecting based on country/language to leveraging On-Demand Builders for [Distributed Persistant Rendering](https://www.netlify.com/blog/2021/04/14/distributed-persistent-rendering-a-new-jamstack-approach-for-faster-builds/). -In the example we'll be using redirects to have a shorter endpoint to Netlify functions. By default, you call a Netlify function when requesting a path like `https://yoursite.netlify.com/.netlify/functions/functionName`. Instead, we'll redirect all calls from a path including `/api` to call on the Netlify functions. So the path will be `https://yoursite.netlify.com/api/functionName`, a lot easier to remember too. +In the [`netlify.toml`](./netlify.toml) configuration file there is an example of how to implement redirects. Redirects can be used to do many things from redirecting Single Page Apps more predictably, redirecting based on country/language to leveraging On-Demand Builders for [Distributed Persistant Rendering](https://www.netlify.com/blog/2021/04/14/distributed-persistent-rendering-a-new-jamstack-approach-for-faster-builds/). + +In the example we'll be using redirects to have a shorter endpoint to Netlify functions. By default, you call a Netlify function when requesting a path like `https://yoursite.netlify.com/.netlify/functions/functionName`. Instead, we'll redirect all calls from a path including `/api` to call on the Netlify functions. So the path will be `https://yoursite.netlify.com/api/functionName`, a lot easier to remember too. ### Example + ```toml [[redirects]] from = "/api/*" @@ -135,3 +140,22 @@ There are many ways to use redirects. Check out the resouces below to learn more - [Creating better, more predicatable redirect rules for SPAs](https://www.netlify.com/blog/2020/04/07/creating-better-more-predictable-redirect-rules-for-spas/) - [Redirect by country or language](https://docs.netlify.com/routing/redirects/redirect-options/#redirect-by-country-or-language) - [On-Demand Builders](https://docs.netlify.com/configure-builds/on-demand-builders/) + +## Serverless Functions + +With Netlify, you can build out server-side code without having to setup and maintain a dedicated server. Inside of our default folder path, [`netlify/functions`](./netlify/functions) you can see an example of the format for JavaScript functions with the [`joke.js`](./netlify/functions/joke.js) file. + +The function format expects a function named `handler` to be exported. This will be the function that will be invoked whenever a client makes a request to the generated endpoints. The endpoint's format is followed as `/.netlify/functions/joke`. So whenever the site is deployed, if you go to `https:///.netlify/functions/joke` you will see a random joke! + +> Side note: In our example, we're using `import` to include data from another location and `export const const handler` to let our function be consumed by Netlify. We're able to do this because of [esbuild](https://esbuild.github.io). This is a bundler configuration we set in our `netlify.toml` under `[functions]`. + +### Serverless Functions Resources + +There is quite a bit you can do with these functions, so here are some additional resources to learn more! + +- [Netlify Function Format](https://docs.netlify.com/functions/build-with-javascript/#synchronous-function-format) +- [Build Netlify Functions with TypeScript](https://docs.netlify.com/functions/build-with-typescript/) +- [Event-triggered Functions](https://docs.netlify.com/functions/trigger-on-events/) +- [What are Background Functions](https://www.netlify.com/blog/2021/01/07/what-are-background-functions/) +- [Netlify Functions - Examples](https://functions.netlify.com/examples/) +- [Using esbuild as your bundler for new ECMAScript Features](https://www.netlify.com/blog/2021/04/02/modern-faster-netlify-functions/) diff --git a/components/JokeBlock.vue b/components/JokeBlock.vue new file mode 100644 index 0000000..73ea89e --- /dev/null +++ b/components/JokeBlock.vue @@ -0,0 +1,25 @@ + + + + + diff --git a/components/feedbackForm.vue b/components/feedbackForm.vue index b608310..2d540f0 100644 --- a/components/feedbackForm.vue +++ b/components/feedbackForm.vue @@ -3,7 +3,6 @@