With tailwind, it's sort of assumed that you're using e.g. React components. So all buttons will look the same because you'll import the button component, that's defined in a separate style.
Pollen seems to me closer to bootstrap: define classes for each thing, and then use them everywhere.
If you're designing a page or site without breaking your HTML into separate components, I can see the point of Pollen.
(I am not a front-end expert, and my opinion is based on my limited experience using bootstrap, tailwind and tailwindui+react.)
Yep, but they are called templates in backend frameworks, You write HTML with sprinkled in logic in Elixir/PHP/Python/Ruby etc.
Components is the terminus used in (usually) JavaScript frontend development where you write JS logic and HTML is only used in the render/view/etc function.
Even backend frameworks distinguish between templates and components.
For example, Laravel has Blade templates and Blade components. From the documentation on the latter:
"Components and slots provide similar benefits to sections, layouts, and includes"
If you use Tailwind with Blade templates, but don't use {components, sections, layouts, includes}, then you'll have a hard time keeping things consistent. Because you'll define how a button looks over and over in each template. In that case, something like Bootstrap or Pollen would be easier.
But the right way is probably to break your templates into smaller pieces (e.g. components) so you can use Tailwind but still share things like buttons between templates.
Pollen seems to me closer to bootstrap: define classes for each thing, and then use them everywhere.
If you're designing a page or site without breaking your HTML into separate components, I can see the point of Pollen.
(I am not a front-end expert, and my opinion is based on my limited experience using bootstrap, tailwind and tailwindui+react.)