and partially rewrites the SearchBar and DirectionsNullState to use it
and adds it in such a way that its reset styles (aka "preflight") don't interfere with MapLibre UI
but also disables the preflight entirely because it interferes with our own styles
My thinking is we can incrementally adopt TailwindCSS and once everything uses it, re-enable the preflight, because we do want it, and will be able to remove some boilerplate like having bg-transparent border-0 on the buttons.
Motivation for using TailwindCSS in the first place:
it gives us defaults and a system that are tuned by professional designers, instead of hand-writing everything.
it's recommended for use with Radix, a component library I want to use to get decent (accessible) dialogs, alerts, dropdowns, etc., and which has no CSS of its own
My thinking is we can incrementally adopt TailwindCSS and once everything uses it, re-enable the preflight, because we do want it, and will be able to remove some boilerplate like having
bg-transparent border-0on the buttons.Motivation for using TailwindCSS in the first place: