I disabled purging for Tailwind, because there was some issue that's preventing the form fields to render correctly.
Also, if we disable it then it means that custom rendering from userland won't have access to Tailwind (or at least only a subset that's not purged yet).
Backoffice uses the backoffice.html layout file, but then that only references Backoffice's app.css, not css files from userland, so this means that we might need to provide a way for user to supply their custom css & js files, and then we can proceed to purge unused Tailwind classes.
The idea is probably for user to supply it in the layout page, just as they do with logo & links now.
I disabled purging for Tailwind, because there was some issue that's preventing the form fields to render correctly.
Also, if we disable it then it means that custom rendering from userland won't have access to Tailwind (or at least only a subset that's not purged yet).
Backoffice uses the
backoffice.htmllayout file, but then that only references Backoffice'sapp.css, not css files from userland, so this means that we might need to provide a way for user to supply their custom css & js files, and then we can proceed to purge unused Tailwind classes.The idea is probably for user to supply it in the layout page, just as they do with logo & links now.