Is Nuxt.js Content The Next Big Headless CMS? Nuxt.js Content Tutorial, Nuxt.js Auto-Import Tutorial

[@jayrenegade3009]

Finally a nuxt version of vuepress, now i don't have to create my own dynamic sidebar on my documentation site. This is truly a feature I never knew I needed. Thank you Eric, you have once again showed me more ways to improve as a developer. I love your style of teaching and hope to learn more from you in the future. I'm glad I subbed to you 2years ago.

[@שמואלדישראלי-ב2י]

I fail to see how is this better then static HTML CSS and JS (for static sites) what does markdown add here that we couldn't do before? i get that it is new and fancy but what does it make possible or easy?

[@mtzrmzia]

How can we use Nuxt-content to fetch some data from some Headless CMS like Strapi?

[@evil1717]

Check out netlify cms if you are using netlify

[@atinux]

Just use the HTTP module for it, we are soon releasing @nuxtjs/strapi module, checkout our Twitter for updates (@nuxt_js)

[@junihh]

@@atinux Great. Nice to know that because I love Strapi.

[@yagelProject]

Work Generate? Npm run generate in content i18n

[@duketranslucent3rd]

Which VS extension is it that powers the "vbase" scaffold?

[@BenHayat]

Erik, what of those content (as you created static markdown) actually come from DB Via a REST call. Another words, I don't want to create static content like in About, but rather call a REST service to show in About. Or is Nuxt mainly for "Static" content Thanks!

[@igsx5252]

as for nuxt:2.14.0 the @nuxt/content goes to modules instead of buildModules ! i.e : modules: ['@nuxt/content'],

[@ErnestoCode]

What’s the name of the extension that lets you type in vbase and get that standard template? I find I get that same result simply by typing template and selection the Vue default option that begins to auto fill.

[@s4ndeep1203]

Why would you use the auto import though? It seems to remove clarity from the flow.

[@aldonisenberg1043]

Agreed! But if we still want this functionality with Vue 3 and have the code be explicit: www.vuemastery.com/courses/vue3-forms/auto-importing-components She does a great job of showing how to do this with just javascript in the main.js file. Without any extra plugins.

[@syofyanzuhad]

Great ! This is what a looking for a blog..

[@themindstorm9947]

This is amazing! I just hope that in a future update we can use components inside markdown without having to import them

[@atinux]

In the roadmap :)

[@themindstorm9947]

@@atinux OMG I didn't expect you to reply here! Thanks, and great to hear it's coming! Another think I was wondering was if we can use $content to import data from external sources. Is this on a roadmap? I'd like to use nuxt content to import content from an API. Either way, I'd like to thank you for making such a nice framework. It's an absolute pleasure to use 😁

[@manaflask8826]

Also I'm glad Nuxt finally has auto import of components. Declaring them, importing them over and over again is so stupid. The framework should be able to analyze the code, and now it finally can. Welcome to the Rails-feature-that-existed-more-than-a-decade-ago club.

[@youtubewts]

What are your thoughts on how this compares to the comparable parts of Gridsome?

[@devyanipatil5734]

Will you please make one video on how to use Nuxt-Content with JSON files and how to import components in JSON? All are showing how to create a blog using a markdown file.

[@richardegil]

Sticking with NPM myself. I have not read the docs yet but is it simple to make nested pages?

[@ProgramWithErik]

I like NPM too! It says in the docs to name your components with the folder structure. So if you have foo/bar then it would be FooBar.vue. I'm not sure if you can overwrite that easily..

[@CesarGalvez8]

Great! I'll give it a try. Btw what is the name of your vscode theme?

[@narcissisticcapitalist1842]

I’m new to cms and was going to learn storyblok until I seen this video. How does this stack up to storyblok ? I’d rather learn the new technology than something outdated. What’s your opinion

[@ProgramWithErik]

Storyblok is quite different. Nuxt.js is a fully featured Vue app creator.

[@kendalljackson9326]

Storyblok has slightly more latency since the content is not on the same domain, but allows for a front-end content editor for interns, copywriters, etc to add pages or articles. With nuxt-content, you'd have to use another service to convert text to markdown, yaml, etc. Those are the main differences, I would go with nuxt-content personally. Storyblok also has a lot of syntax that is very specific to them, which I didn't like too much.

[@narcissisticcapitalist1842]

Kendall Jackson makes sense and what do you use to translate text to html. I just spent all night with disclaimers, terms etc doing it manually

[@kendalljackson9326]

Great vid, super helpful

[@s4ndeep1203]

npm is faster to write than yarn (3char vs 4 char)

[@DavidSmith-ef4eh]

You could create an alias for yarn called "yar"

[@raj080288]

should I learn vue.js first before Nuxt or go directly to Nuxt?

[@david_chuka]

Nuxt is basically built on top of Vue. I feel like learning Vue first would do you a lot of good

[@ProgramWithErik]

Learn vue first~!

[@waytoprogramming]

This was really helpful!

[@hariztek]

I dont really want to use yarn wanna stick with npm but some source codes just break with npm cause they use yarn

[@AdarshMadrecha]

I am npm person too.. 😁

[@ProgramWithErik]

😄

[@ahmedadly]

Well done, Thanks

[@RobbertHock]

Super fast after last weeks announcement 👍🏻

[@ProgramWithErik]

Yeah, things are moving fast :)

[@duketranslucent3rd]

Sucks a bit that you have to manually import into your pages any components you want to reference in content. Can't really see the rationale for that, especially in light of the Nuxt Components breakthrough (i.e. not having to manually import components to use them in pages.)

[@ReuvenEtzion]

Yarn was better for a short period before NPM invested in expanding their features and security. NPM is far better than Yarn nowadays, IMO.

[@MrPoselsky]

Instead of creating cool stuff with nuxt, they could actually update their docs. Compared to quasar, their docs are horrendous.

[@atinux]

It is already in progress thank you, will be released as beta in few weeks :)

[@kevintlu]

@@atinux Finally, nice work dude!

[@gonzoartemis2503]

The docs are being taken care of lately and the idea of the new blog is great. There are a couple of interesting blog articles out there.

[@BenHayat]

Stay with npm as most people use it.

[@JoeMcBroom]

Npm all day

[@atomtopa]

NPM for me.

[@manaflask8826]

Responding to your NPM question: My organization lives with NPM because this whole npm vs yarn war is stupid. Both do the same thing. Deprecate one and move on with our lives please.

[@fredhair]

The problem with that is when one or the other introduces a breaking feature that's incompatible with your build its nice to have a choice. I use npm with pnpm to solve the node_modules size problem. Having choice isnt a bad thing especially if they're largely compatible with each other.

[@classicguy7813]

Yyuruf