In Filament tables, sometimes we show just the sum/count number cause we don't have enough space. So, let's add a Modal action to the column.
By default, the create button will be placed above the table. But we can move it to be in line with our Search toolbar.
Clusters are a great way to group navigation, but by default - they are only visible on List pages. Let's add them to the Create/Edit pages, too.
Having a search is great, but knowing what people search for - is key. So let's build a system where we can log all searches.
Sometimes, we have to show our Users what the result will look like. For example, if you enter the price in cents - we can instantly display what the amount equals by using prefix/suffix on the field.
To create a new record in Filament Resource, users typically go to the List page and click the "Add New" button. But what if you want to add that link to the sidebar navigation?
Filament has a white top bar, which might not match your design style. Let's change it to match the content colors.
The Filament has 84 Render Hooks in various places. That's why we prepared a simple Cheat Sheet to display where you can expect them to appear.
In complex tables, we often have a lot of filters. But losing them each time we click the edit/create buttons - is annoying! So, let's solve that with persistent filters.
Your application's everyday actions should be accessible as quickly as possible. So, using the Render Hooks and Livewire component, let's move them above our sidebar.
We are used to our tables having an order. Often, it's done by ID or any other column. But did you know that you can shuffle them with a single button click?
Some elements in your panel require an existing Tailwind CSS class, but often, it's not pre-compiled and doesn't work. So let's see how we can use any class!
Having a form with too much information can hurt the user experience. To solve this, we can put our Relation Managers into tabs on the edit page.
Filtering tables can be confusing or even slow, especially if you have to filter them often. That's why moving buttons to the top of the table and displaying them at all times can lead to a better user experience.
Wizard forms solve the issue of having too many input fields (big forms). But what if the user leaves mid-filling? In that case, you can auto-save a draft and let them edit the record at any point.
