Additional packages suggestion

[mikemastercorp]

Hello Dennis.

I 've been working on a starter kit with some cool nonobstrusive features for Filament and every developer to start with. My focus was on two packages (Spatie settings) and User roles (no particular package).

My approach was to create a simple setup page that will include every possible input available in Filament as an example page so that if you need to populate some project settings, you have all type examples and you can replicate or remove any unnecessary. I've also added tabs so that the settings can be split in multiple screens etc. I would really loved to be able to have my tabs in a vertical order as it is In most platforms but at the time (a few months) I did not find an easy option other than a custom page.

U fortunately I freezed the project temporarily due to personal health issues requiring my attention but I am not giving up on it and will be able to continue eventually.

I am writing this message to propose you to add some similar functionality if you see such fit in your idea as it would be crucial for a starter pack to have roles and permissions, settings and some cool comments In the project which explains most used options for every page/form parameter with a direct link to documentation for reading the test of options. Feel free to have a sneak peak if interested, but the stage of the starter is not any way near an alpha yet.

Good luck with your project, I am sure it is well structured and dreamed like you to take away the hassle of starting a new project and repeating things over and over again every next time...

[CodeWithDennis]

Hi Mike!

Thank you for your message!

I wanted to share a few thoughts on your suggestions. First, I think it’s important to consider that not everyone uses roles and permissions in their projects. Including that feature might add unnecessary bloat for a large portion of users who rely on the basics of the boilerplate.

Additionally, while adding comments to the entire codebase is a nice idea, it might be a bit extreme since there’s already a lot of documentation available for Laravel and FilamentPHP.

I’ve also been thinking about implementing a wizard or installation setup to allow for more customization, but I haven’t had the time to figure out how that would work yet.

My main priority is to help developers quickly set up their projects using the packages and tools that 95% of them utilize. Adding too many extra packages could lead to bloat, which is something I want to avoid.

Feel free to keep coming up with suggestions!

[mikemastercorp]

I understand, Dennis. Everybody has his opinion. I've thought about what you said interns of the roles so I am thinking on adding a kill switch or an easy instruction about how to remove it and the steps should be really idiotic if one does not need it. Same can apply for such install but then it should be done as a module/plugin and I am afraid it won't be just 1-2 liners to install, configure and make available.

As for the settings, I believe that most websites would at least like to have logo options, SEO meta tags or any other extra options that can be easily edited via the admin.

Anyway, I will follow closely with your project as I myself am learning Fila (ment :) ) and wanted to know how things work when I initiated the starter

And yes, about the comments, I agree it is a bit cumbersome and I would potentially write some nice documentation and clear the code, but it becomes an overkill to the amazing fillament documentation so that is why I left (maybe too many) comments pointing directly to the actual topic.

Good luck with the project, your approach of using action classes was interesting and I can borrow some code to repurpose some repeatable actions within pages/forms etc.

That is what I love about open source - we can share views, approaches, improve our code etc.

[CodeWithDennis]

I welcome any suggestions/feedback and am glad you found the approach helpful!