@jhull Oooo, interesting. I need to check that out. I want to get into Vue.js for a few things...
@vincent dude. Save yourself some time and go straight to Nuxt. When you’re learning Nuxt, you’re learning Vue—but in an amazing way.
Let me know if you need any help.
@jhull alright! I have a project in mind where I can test this then. Does Nuxt work nicely with existing projects, where I can just Vue-ify specific sections on the page? (Haven’t read too much about it just yet).
@vincent download and install. create-nuxt-app
and decide whether you want Universal/SPA/Static - you can ALWAYS change this later. Took me awhile to understand the difference, but the basic gist is:
Universal: Sever-side rendered (hosted on Heroku) with both Client and Server bundles SPA: Client-side only Static: ALL pages generated ahead of time and served on a static hosting site (think Netlify). JS is then hydrated on top of it, so you get the SEO benefit of SSR along with all the great reactivity of JS
Then all you do is pull over the components from your previous project (if you have existing Vue components) or just start building pages. The pages
directory is unique to Nuxt - like PHP with folder structure mimicking URLs. index.vue
is the base route, _slug.vue
would be the dynamic routes.
If you're coming from a Laravel point of view, it really is just Laravel for Vue. You've got a Middleware
folder. You've got the pages
directory mimicking Routes. And a bunch of other greatness.
Let me know if you any of that makes sense!