ntn-boilerplate VS vuesion

This is the way. A great and completely free stack is this Nuxt and Netlify CMS stack that uses the git repo for the CMS part. Works great for smaller blogs. But wouldn’t choose it if it was a bigger website that does more than a blog/portfolio.

Check out a boilerplate for Nuxt if you want to get into the gritty quickly or just test it out https://github.com/Knogobert/ntn-boilerplate

I use them in all of my input components: https://github.com/vuesion/vuesion/tree/next/src/components/input-and-actions

I can provide you with my knowledge about Vue 2/nuxt2: https://github.com/vuesion/vuesion and Vue 3/nuxt3: https://github.com/vuesion/vuesion5

https://github.com/vuesion/vuesion or for nuxt3/vue3: https://github.com/vuesion/vuesion5

I have a repo with Vue2 (Nuxt.js 2) + composition api and storybook: https://github.com/vuesion/vuesion

https://github.com/vuesion/vuesion has GQL setup included

one exception is using plugins like i18n, they can also be used inside presentational components because they are pretty easy to integrate (no specific set of configuration per use-case) into storybook and tests. if you want to see my setup, go to https://github.com/vuesion/vuesion

I have a nuxt2 boilerplate that uses composition api already. Should hopefully be easy to migrate to nuxt3 later this year: https://github.com/vuesion/vuesion. I hope it helps you to make a decision

We maintain a (nuxt) template project that new projects are forked from. It contains all the settings and libraries that we minimally need for an app. I think it's important to have your own template project, rather than use someone else's.

Give this a shot: https://github.com/vuesion/vuesion

I maintain a reference project as boilerplate here: https://github.com/vuesion/vuesion. let me know if you have any questions.