Israel Muñoz

Posted on Mar 2, 2019 • Originally published at israelmuca.dev

JAMstack and CD pipelines: Create a blog with Nuxt, Netlify CMS and Netlify

#jamstack #nuxt #netlify #webdev

This post was originally published on israelmuca.dev

The "old" ways

Say you wanted to create a blog, you could easily run a Wordpress site, with a Linux server distributing your content. On each page load, the server would generate the webpages, and serve them to the user.
Every request puts the server to work.
It's a perfectly viable option, although slower compared to more modern options, more insecure as you have to be doing the updates on your server (or paying more for a managed server), and it requires using PHP and having a database running.

JAMstack to the rescue!

So what is JAMstack? It stands for JavaScript, APIs and Markup. 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.

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), 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.

There is one caveat though. Every time you change anything, you have to rebuild your assets, and deploy them... ugh... but wait!, as that's where a CD pipeline comes into play!

CD pipelines...?

You've probably heard the terms CI/CD being thrown around, with CD sometimes referring to Continuous Delivery or Continuous Deployment. Arguments get quite long when debating about the PRECISE meaning of these words, as you can see in this Stack Overflow question.

In my case, I'm talking about Continuous Deployment, as explained by Netlify here.

Continuous deployment works by connecting a Git repository to a Netlify site and keeping the two in sync.

Easy peasy. We want our repo to be in sync with our site.

But how?

Netlify is an amazing PaaS that has SO MANY FEATURES, really, just to mention a few:

Automated builds and deployments via webhooks straight from your Git repository.
Rollbacks, as previous deployments are not erased.
Continuous Integration tests.
Deployment previews from Pull Requests.
Free SSL certificates.
A CDN.
AND S O, M U C H, M O R E.

Check out their features or dive straight into the documentation pleeeeeaaaase. As everything I mentioned is included in their VERY generous free tier.
So for our use case, we'll be using their automated build and deployment (as I am).

Nuxt.js + Netlify, a match made in heaven

In my case, I've been working with Vue.js and I wanted to build my blog with Vue, so for that, I used Nuxt.js 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!

Netlify CMS

Last but not least. How can you manage your content like this?
Remember that the JAMstack best practices mention that ideally, everything lives on your git, so anyone can, with a couple of clicks, get going and contribute to your project.

That's where Netlify's CMS 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.

Getting started

For this, we'll only be needing:

Github account
Netlify account
Vue/Nuxt understanding

Fork the repo

Using your Github account, go ahead and click here to fork the repo or just clone it.

Build Setup

Install all the dependencies

npm i

Now, you can run the code in development with:

npm run dev

This will serve your page in localhost:3000 with hot reload.

Once you're ready to generate your static assets for production:

npm run generate

This will create a /dist folder with the assets. This folder is not committed.
This is what Netlify will be building on their server, and then uploading the results to their CDN. We don't need to do this manually ever. We just do it for the sake of watching what happens inside Netlify.

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 here, dev.to. Mostly covering the title, description, and keywords for SEO purposes, also a little summary of the post as well as the 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 for extra customization.

While your local server is running, you can access 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.

Routes

In here, both Nuxt and Nuxtdown work together to create the routes in the website.

In the pages directory, you'll find an index.vue which is, as the name implies, the index of our site.
This is handled by Nuxt.

The pages/blog/ directory will work as a directory in our site as well (israelmuca.dev/blog/... in my case), which will hold all the blog posts that are created using the _blogpost.vue template inside. It will be compiled once for each .md in the content/blog/ directory. You can see how the content is fetched inside of that .vue file.
This is handled by Nuxtdown.

You can configure Nuxtdown in: nuxtdown.config.js, and please go ahead and check the Nuxtdown Documentation to further understand what is happening or to change the functionality.

The rest of the site

The rest of the site is a regular Vue + Nuxt app, I tried to comment the code where I think it's needed the most, and you can configure Nuxt in: nuxt.config.js, also, as usual, please check the Vue.js and Nuxt.js documentation to further understand this code if you have any questions.

Congratulations

By this point, you should have a fully functional Nuxt generated, Netlify hosted, blog site.

Issues

If you have any problems implementing this, please don't hesitate and create a Github Issue or send me a tweet.

Thanks

There's a phrase that I love and always try and remember:

If I have seen further it is by standing in the shoulders of Giants
Isaac Newton

Being true to that phrase, I have to acknowledge the many people that in one way or another contributed to this specific repo:

Thanks again, and read ya'll soon!

Top comments (8)

Gijo Varghese • Mar 3 '19

Gatsby vs NetlifyCMS?

Israel Muñoz • Mar 3 '19

I guess in this case a fair comparison would be Nuxt vs Gatsby, or Contentful vs NetlifyCMS, as that's what the alternatives would be!

In the case of Gatsby vs Nuxt, a simple way to sum it up would be if you'd like to work with React or Vue, as Gatsby is based off React, and Nuxt based off Vue.