Add a 'workflow' section to the documentation.

[RyanPaiva56]

So, if someone is a big silly like me and didn't think about how Vite only exports CSS from Tailwind that actually gets used, copying new components from FluxUI wont work unless you're using npm run dev etc. I mean they'll work, but but they wont display correclty.

OF COURSE everyone is going to know this but for folks new to Laravel monolith or TALL stack, a little heads up will probably reduce the number of unncessary issues created here in the repo. Look at this goof creating what one can only describe as a perfect issue only to find out that he made a big brain fart: #496

Here's a draft of what could be included on the install docs:

Workflow Guide

If you're new to Laravel Monolith or TALL stack and FluxUI is your entry point into using Laravel as both your front and back-end, you should read Laravel's Vite documentation. It's important to know that Vite only builds JS and CSS that is actually used by your project. So, if you copy and paste a component example from the FluxUI documentation, it probably wont display properly until your project rebuilds. If you run the command npm run dev, this happens almost instantly and will keep you from having to manually refresh your page.