Rethink architecture - Start the frontend

[abarreraaponte]

Ended up choosing Inertia but with React instead of Vue. DaisyUI + Tailwind

• [x] Login Page
• [x] Register
• [ ] Forgot Password
• [ ] Reset Password
• [ ] Email Verification
• [ ] Password Confirmation
• [ ] Base Dashboard and nav

Initially I wanted kitledger to be only the API. I'm reconsidering the approach as it will be important to launch an initial version with some kind of UI.

Options:

• Keep laravel as platform, add Inertia + Vue
• • This option is solid but heavily coupled. We basically forget about running kitledger hidden inside the VPN.
• Keep core as API, use an SSR framework for web
• -This option is harder to implement and deploy but it is certainly more secure, robust and flexible. Nuxt would likely be the candidate.
• Keep core as API, use a Desktop app as the client -- Similar to what Slack and Teams does. I like that it could be used as a single client from which the user can handle multiple servers. I think the performance can be amazing by leveraging the users device. Authentication becomes an issue. Even with Sanctum we still have to deal with Email verification, password resets, email confirmation.

[abarreraaponte]

I'll stop complicating things, the main system will be a monolith. The UI will be Inertia with either Vue or React. Auth via Breeze + Sanctum.

DaisyUI for styles, with Radix or Radix vue for more interactive components we don't yet have.

[abarreraaponte]

Next step is to setup Breeze again with the desired stack. Typescript is non negociable. Vue or React can still be debated.

[abarreraaponte]

Added DaisyUI + Breeze + React + Typescript + Tailwind + base themes.

Next step is to clean up the default breeze pages, remove unused components, fix Auth layout.