Actually, I take back what I said about NoSQL being any more integrated. Nuxt really is purely client-side so you'd have to have a separate REST or GraphQL to go along w/ it

As far as UI building goes, if you learn Tailwind you can make things like this in a matter of 30min. if you want to take a look, you can check it out here

I'm starting to like separate frontend/backend deployments for organizational reasons unless it's a static webpage, in which case you can actually use Nuxt (or NextJS for React) to have SSR static pages and speed up load time. If you have a ton of things built w/ CakePHP you would have to do some cost-benefit analysis to see if migrating to a new stack would be worth it resource and time-wise.

@umer936 Depends on what kind of stack you're going for. If you're willing to have a NoSQL backend it'll be highly integrated, but a separate ORM/SQL server with API endpoints works just as well. I've done it w/ React and Django. Vue is a little bit of a learning curve as it is.

Hmm maybe I should switch us to this then.

Also, I WILL shill for tailwind, honestly so convenient