So I'm thinking about the structure for my restaurant web page which will use laravel as the back-end (routing and displaying blade views to the browser, easy auth system and sessions) and vue.js for the front-end (I have a single vue instance where I register components, this components are each one a view, a whole page, most of these pages have 2 or 3 components nested, like an image slider, to-top anchor, I use axios to fetch my API endpoints without refreshing the page plus many CRUD operations from an admin panel).
This is how my index.blade.php view looks ( www.domain.com/ ), I have many views like posts.index.blade.php...
@extends('layouts.master') @section('content') <page-index></page-index) @endsection
As you can see, I want to treat each page as a vue.component with many components nested inside of each page component).
I have a few questions about possible complications using this structure.
Is this a good practice, is this the best way to handle laravel + vue.js non-SPA? Is this a good abstraction of front-end and back-end?
How I will handle auth is by doing axios requests to laravel login endpoints.