Intro and Demo

@Adgower Great timing!

@iamputhea If you have a good reason to have a separate backend API, I would go with this architecture in the series where you have a separate backend for the API, and a web frontend with Nuxt. An example is if you know you need both a webapp and a mobile app.

However, if you know you only need a webapp I would prefer using Laravel/Inertia/Vue (or React). It removes a lot of the complexity of building traditional single page apps and is really easy to use if you already know Laravel. It even now supports server-side rendering if you were worried about your SEO taking a hit.

@drehimself Thanks for your explanations.

@syahmiibrahim Definitely learn Vue first, I am using a lot of the newer Vue 3 syntax like script setup. After learning Vue, I would also recommend learning Inertia (with Vue), as building apps that way is much simpler than having a separate backend API (like in this series).

Once you understand the different ways to build apps and their potential tradeoffs, then you can learn what Nuxt can do for you.

@drehimself thank you for sharing this wisdom, im not brand new to laravel or vue/nuxt but I used nuxt2, vue3/nuxt3 is throwing me for a loop and Ive been wondering in what order I should be learning this, thank you.