Merge pull request israelmuca#5 from israelmuca/cms/2019-02-27-jamstack-and-cd-pipelines-create-a-blog-with-nuxt-netlify-cms-and-netlify

Automatically generated. Merged on Netlify CMS.

Author: israelmuca

content/blog/2019-02-27-jamstack-and-cd-pipelines-create-a-blog-with-nuxt-netlify-cms-and-netlify.md

@@ -24,7 +24,7 @@ It's a perfectly viable option, although slower compared to more modern options,
 ## JAMstack to the rescue!
 So what is JAMstack? It stands for **J**avaScript, **A**PIs and **M**arkup. A modern way of writing webpages that are compiled to static assets right before deploying. JavaScript handles the dynamics in your page, what were server-side processes, are now abstracted into APIs if needed, and your markup is compiled during deploys. Go ahead and read all about it on the [official webpage](https://jamstack.org/).
 
-The benefits that this approach has is that your webpage ends up being blazing fast and with all of your content precompiled, nothing has to be fetched every time the page is served and, you can host it in many many more places (and it's way cheaper (or even free, with [Netlify](https://netlify.com)), as it is only HTML and JS files all while getting improved SEO with your page.
+The benefits that this approach has is that your webpage ends up being blazing fast and with all of your content precompiled, nothing has to be fetched every time the page is served and, you can host it in many many more places (and it's way cheaper (or even free, with [Netlify](https://netlify.com))), as it is only HTML and JS files all while getting improved SEO with your page.
 Your page is also more secure! Since you don't have exposed APIs, you could even use Wordpress as a CMS but without the security risks or performance problems of running Wordpress itself.
 The performance is definitely worth mentioning again, as it is quite easy to make your site super fast.
 
@@ -49,13 +49,14 @@ Netlify is an amazing [PaaS](https://en.wikipedia.org/wiki/Platform_as_a_service
 - AND S O, M U C H, M O R E.
 
 Check out their [features](https://netlify.com/features/) or dive straight into the [documentation](https://www.netlify.com/docs/) pleeeeeaaaase. As everything I mentioned is included in their VERY generous free tier.
-So for our use case, we'll can be using their automated build and deployment (as I am).
+So for this guide, we'll be using their automated build and deployment service (as I am).
 
 
 ## Nuxt.js + Netlify, a match made in heaven
-In my case, I've been working with [Vue.js](https://vuejs.org) and I wanted to build my blog with Vue, so for that, I used [Nuxt.js](https://nuxtjs.org) which is a framework built on top of Vue that offers both Server Side Rendering (you need a Nuxt instance running, thus a server as well, a no-go for our project) and also offers Static Site Generator, which **compiles** all of your fancy Vue code into plain HTML and JS. That's exactly what we need for Netlify! _OH YEAH!_ . 
+In my case, I've been working with [Vue.js](https://vuejs.org) and I wanted to build my blog with it, so for that, I used [Nuxt.js](https://nuxtjs.org) which is a framework built on top of Vue that offers both Server Side Rendering (you need a Nuxt instance running, thus a server as well, a no-go for our project) and also offers Static Site Generator, which **compiles** all of your fancy Vue code into plain HTML and JS. That's exactly what we need for Netlify! _OH YEAH!_ . 
 
-Every time you push your code to the repo, Netlify pulls the latest version, and in my case, runs ```nuxt generate``` and then uploads the ```/dist``` folder into their CDN. And that's it! Your latest version is live in a minute or two. No need to upload anything manually or check what version is uploaded... Everything is *automated* now... Continuous Deployment FTW!
+Every time you push your code to the repo, Netlify get's notified through a webhook, then pulls the latest version, and in my case, runs ```nuxt generate``` and then uploads the ```/dist``` folder into their CDN. And that's it!  
+Your latest version is live in a minute or two. No need to manually upload anything or check what version is uploaded... Everything is *automated* now... Continuous Deployment FTW!
 
 ## Netlify CMS
 Last but not least. How can you manage your content like this?
@@ -64,7 +65,7 @@ Remember that the [JAMstack best practices](https://jamstack.org/best-practices/
 That's where [Netlify's CMS](https://www.netlifycms.org/) comes in. It's an Open Source Software, that helps you use your Github as a 'database' in a sense. Allowing you to create blog posts directly into ```.md``` files, which you can push into the repo to trigger the builds, creating new blog posts just like that.
 They have an easy to use interface, and even have an editorial workflow, that set articles to be deployed as Pull Requests on your Github, allowing you or your team to review them (using Netlify) before merging them.
 
-All in all, these are amazing tools that let us create blazing fast sites, in a modern environment and require very little configuration for such an amazing final product.
+All in all, these are amazing tools that let us create blazing fast sites, in a modern environment that require very little configuration for such an amazing final product.
 
 
 ## Getting started
@@ -98,11 +99,11 @@ This is what Netlify will be building on their server, and then uploading the re
 ## Configure your *new* repo  
 
 ### Netlify CMS
-You'll need to define your fields and files for your content. I'm using defaults very similar to what you can see in [dev.to](https://dev.to). Mostly covering the title, description and keywords for SEO purposes, also a little summary of the post as well as a main image which is used both in the ArticleCard.vue and the Header.vue in the blog post page.  
+You'll need to define your fields and files for your content. I'm using defaults very similar to what you can see in [dev.to](https://dev.to). Mostly covering the title, description and keywords for SEO purposes, also a little summary of the post as well as a main image which is used both in the `ArticleCard.vue` and the `Header.vue` in the blog post page.  
 
 You can configure these fields in: `static/admin/config.yml`, and feel free to check the [Netlify CMS Documentation](https://www.netlifycms.org/docs/configuration-options/) for extra customization.  
 
-While your local server is running, you can access [localhost:3000/admin/](localhost:3000/admin/) to modify the content of your blog. You can also do it once it's deployed when you have the Netlify's address that's given to you.
+While your local server is running, you can access [localhost:3000/admin/](localhost:3000/admin/) to modify the content of your blog. You can also do it once it's deployed when you have the Netlify's address that's given to you, so it'd look something like: https://yourrepo.netlify.com/admin/
 
 ### Routes
 In here, both Nuxt and Nuxtdown work together to create the routes in the website.