Replies: 1 comment
-
Ah, I found it, it turned out I had two tailwind.css.config files one living at the root and one living at the resources/css/filament/company/tailwind.config.js folder from a different plugin that was controlling the active panel. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've encountered an issue while trying to implement a custom animated background in one of my FilamentPHP custom resource views and I am seeking help on how to properly integrate it across all themes. The goal is to add a gradient background to a specific view using the following HTML and CSS:
The animation works as intended when I manually include TailwindCSS via a <script> tag within the @Push('scripts') directive:
However, this approach isn't ideal as it forces me to include TailwindCSS again, potentially leading to issues. I'm looking for a way to integrate these styles seamlessly into the themes add-on, ensuring that the animated background applies to all views without needing to include TailwindCSS manually each time.
Has anyone faced a similar challenge or can offer advice on how to achieve this? Any insights on how to make these styles part of the global theme or a more efficient method to apply custom animations across Filament views would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions