As an example, if you want to create a booking site, you would need to store customer information such as their name and address. One solution would be to build a single, big part that contains all the logic and then a single view file that grows and grows. What is the most effective way to divide this into more manageable chunks using Livewire?
The way I use livewire is to break down each feature into it's own component.
Considering your example, a booking site might have:
A dashboard to list all mediums: This will be a livewire component to show the list.
A user profile: Store name and email will be one component. Resetting password would be another component. Setting notification preference would be another component.
I wouls still use web routing and inside that route's main blade file, I would add relevant livewire components.
@chaudigv that means I would need a different component for each form that I don't want on the same page? Say if I don't want the edit, create and update on the same page?
Correct. So your folder structure would look something iike Livewire.Component.Add, Livewire.Component.Delete, Livewire.Component-2.Add and so on. At least that way my CRUD operations for each feature would be under one folder.
