How do you become proficient enough at Filament to offer it to clients as a service?
Any suggestions on a path or paths to take to really feel a solid understanding of best practices and concepts around Filament to offer it confidently to clients as a service?
3 Replies
Start with the docs and build a system for confidence. Filament is flexible and can be customised for multiple use cases. ☺️
In addition to building as many projects with it as you can, or at least using as many of its features as you can, there are several more that will deepen your skills:
- look at v2 plugins and convert them to v3, or look at some that were converted to v3 and see what was done ... this will help expose some of the inner workings of v3
- go through all the #help posts here regularly, and find answers for the toughest questions. The frequently-asked-same-questions are easy to answer, but finding answers for the harder questions will make you dig, and sharpen your skill in the process ... making it less likely to get stumped on a client project.
- also use the #help requests as inspiration for PR's to contribute to Filament's core ... cuz the better your understanding of core code, the better your contributions, and of course the side-benefit is you will get familiar with lots of related internals along the way
- take some "old" work/client projects you've worked on, and rebuild them in Filament. The benefit to rebuilding is that you already "know" the business-domain and the requirements for the app, so there's less "wondering" about that, so you can focus on building.
Also remember: choose the best tool for the job. Filament is ideal for Admin back-end systems, and less-intended for use on public-facing sections ... so, try your hand at the thing it's less-intended for, and see what roadblocks you run into, so you know its limits. That way you'll be more confident in selling the right public-facing / front-end "app" (whether Filament or something else) regardless of using Filament on the backend. Knowing a tool's limits will help in a zillion ways, not the least of which is knowing what to commit to vs making (uninformed) assumptions in the quoting phase.
Appreciate the detailed response!