turbolinks VS jetstream

However I still need SPA navigation and although there's a Turbo adapter [0], it looks like more of a prototype at the moment.

[0] https://github.com/livewire/turbolinks

Seems like a no go for now though: https://github.com/livewire/turbolinks/issues/23

For writing models I would suggest using Action Closes. One example of them can be found in Jetstream's sourcecode. Actions are great to test in isolation and link to user stories.

While I prefer python for everything else, I'd go with Laravel Jetstream[1] for an MVP, just like I did with the last one I had to build. It's laravel, you can use Vue (React or Svelte) for your views instead of the blade templating language that comes with the framework. Jetstream also comes with Auth, user login and subscription and other useful stuff.

And for the flavor, I'd just go with DaisyUI[2] again, since it's based on tailwindcss and it's what I've been using lately.

In my experience, I can build MVPs real fast with the stack described above.

[1] https://jetstream.laravel.com

A well-implemented example of this would be in Laravel Jetstream, where an Actions namespace is defined for performing user-oriented tasks in Laravel Fortify — such as updating the user profile.

This legacy package is a very simple authentication scaffolding built on the Bootstrap CSS framework. While it continues to work with the latest version of Laravel, you should consider using Laravel Breeze for new projects. Or, for something more robust, consider Laravel Jetstream.

Laravel provide us with robust solutions and starter kits for authentication so let's start by creating a new Laravel 9 project and install Jetstram

In terms off bullet points you added, I've made something pretty similar using Laravel with : Laravel Jetstream(application starter kit with inertia + vue stack) https://jetstream.laravel.com/