Straw Poll - migration\merge or rebuild ?
I have bee experimenting with filament on some elements of an extensive existing SAAS product. Mainly as we have been asked to massively increase the scope of the product.
I'm sold. The dev time to create features is decimated.
The existing system is modern, on TALL latest version, high coding standards, a lot of Command, Handler, Validation split etc, over 1500 individual tests. It is also quite specific, no plugins etc.
Question is this...do we take our existing system, and lay it on top of Panels, integrate and replace as we go along. Or do we start from scratch, perhaps just preserving our models etc?
Apart from the authentication, (which I think you change to the panel preferred method from the outset), and the existing landing dashboard...could we easily incorporate existing forms and routes that are specific and will take time to re-build in filament. They also work well, so there would be no rush.
Or, is trying to run traditional Laravel assets within a Panel environment a proper PIA ?
I totally get, the answer is often...it depends....but If you've got any thoughts, experiences, or can point to any resources discussing this, be much appreciated.
0 Replies