nuxt VS vitepress

Today we are looking at Error Handling when building websites with Nuxt and Storyblok as CMS. If you haven't tried the two tools, go check out one of the awesome tutorials. It's a perfect match for all your projects.

Nuxt

Nuxt is an open-source framework for building performant websites and full-stack applications using Vue.js. It provides performance and SEO benefits, and adds full-stack capabilities for Vue apps.

The minimalist blog theme, powered by Nuxt.

The (devtools)[https://devtools.nuxt.com/] I want to talk about shortly are the (Nuxt)[https://nuxt.com/] devtools which are I would say by a landslide the best devtools out there. You don't need to trust me, just try it out, get a basic nuxt app running, open devtools, go to modules, add tailwind, maybe add an API route and play around with the dev tools a bit. I'm pretty confident in saying that it's the best experience out there in JS land, and belive it or not, the plan is to make it vue/nuxt agnostic, so it might become something react, svelte etc devs would enjoy in the future

Nuxt is a meta-framework built on top of Vue.js, a JavaScript library. It features SSR, SSG, SEO, File-System routing, Caching etc. It can be used to build ecommerce storefronts.

Thanks for reading!

The web tech stack is actually one of my biggest regrets. It's a static site generator called Gridsome[0] that the maintainers abandoned about three months after I used it to launch the TinyPilot website.

At the time I made the TinyPilot site, I was very excited about Vue, so a Vue-based SSG seemed great. Since then, I've come to find SPAs and most frontend frameworks to be way too much complexity, so I've moved away from Vue, but the TinyPilot website is still stuck on Vue 2.x and bootstrap-vue (which is tied to Vue 2 and Bootstrap 4).

So, it keeps creaking along, but building the 100ish pages on the site takes about five minutes, whereas I think something like Hugo could probably do it in a few seconds. Plus, we get random runtime errors[1] that are pretty hard to debug.

[0] https://gridsome.org/

[1] https://github.com/nuxt/nuxt/issues/5800

...and much more 🚀

Nuxt: The Intuitive Vue Framework

We're excited to introduce a new way to enhance your Nuxt development workflow! After the Vue plugin, we're introducing our new Nx plugin for Nuxt, @nx/nuxt. Designed for Nuxt developers and existing Nx users alike, this integration brings the best of both worlds into your development ecosystem, enabling you to leverage Nx's powerful capabilities seamlessly within your Nuxt projects.

There is a discussion related to naming on GitHub: https://github.com/vuejs/vitepress/discussions/548

> I initially gave VitePress a different name because I wanted to be able to explore a different architecture without worrying about backwards compat. After shipping the vuejs.org with VitePress, I believe VitePress is flexible enough to be a full replacement of current VuePress while offering better DX and better performance.

Given that version 1 landed as "VitePress" they probably decided to keep the name.

> ...

> I think we should ship VitePress stable as VuePress 3, but I am open to potential questions and concerns.

> Pros: Less confusion in the long run. There will be just one officially maintained SSG with better DX, better performance, and customization that fully aligns with standard Vite-based Vue apps.

> Cons: Potential confusion in the short run, since there are probably a lot of tutorials / integrations targeting VuePress 1. Still I think with the recent Vue 3 switch, users won't be surprised with a major upgrade for VuePress.

I was inspired by a great series of blog posts and decided to adapt the approach to my needs. In this blog post, I will go over the solution I used in my VitePress site but you can also check a more basic example in this CodePen.

While researching which static site generator we would use, we had a lot of frameworks to pick up from, but only some addressed our needs. While choosing, we needed it to have a good "default" template, out-of-the-box plugins, and be easy to extend its functionalities. From our research, the one that matched most criteria and felt the easiest to start and progress with was Vitepress.

They are using the default theme of VitePress which is a great tool for building content-centric websites such as documentation

Thankfully, an entire ecosystem of frameworks makes docs sites easy to build and services that make static sites easy to deploy. In this post, you'll learn how to build a docs site with VitePress and deploy it to the internet with Render.

I have a few Jekyll blogs including my personal one and I haven't had to touch the Jekyll part for quite a while (it takes a while to compile). I just write in Obsidian and then Github takes over.

I also maintain two VitePress[1] sites. Once I setup it up (I still use Sublime Text), I do the writing on Obsidian.

What I write and see in Obsidian is good enough that I have just done away with looking at how the site looks after I change/add/edit the text. I sometimes do but just to check build and if the sitemaps are generated, etc. -- routine hygiene.

1. https://vitepress.dev

Consider Nuxt instead of Vuepress/Vitepress. If you want the built-in theme in Vitepress, it's great, but if you want to make your own, using Nuxt with the Content plugin is probably better. I found the strong separation between theme and content to be too great, and if I have a docs SSG site using Vitepress and a webapp SSR site using Nuxt, I can't share themes easily anyway.

At least that was my conclusion starting with Vitepress, and ending up with Nuxt 3.

https://nuxt.com/

https://vitepress.dev/ (they haven't decided if they are going to replace Vuepress or not: https://github.com/vuejs/vitepress/discussions/548)

Another option vitepress