[conradfr]

I agree.

> If you want to use Bulma or Bootstrap instead of Tailwind – no problem! Simply replace the function definitions in core_components.ex with your framework/UI specific implementations

"Simply" here means rewriting a 661 lines file. Maybe a more modular approach with only Tailwind support at release would have been better.

I know I'm always the "Symfony does it better" guy but in this framework to use Bootstrap (or Foundation etc) for my forms[0] I "simply" have to put:

> form_themes: ['bootstrap_5_horizontal_layout.html.twig']

Well maybe the first person to actually rewrite core_components.ex will share it in a Gist or something ;)

I also find the new collocated views in the controllers folder a bit messy and not really productive in practice IMHO.

[0]https://symfony.com/doc/current/form/form_themes.html

[sph]

It's 661 lines of default styling. Every website will have its own style guide and will have to rewrite those 661 lines anyway.

In fact my Tailwind project has completely replaced those lines anyway, and written three time as much (to have a unified component library)

[josevalim]

> Well maybe the first person to actually rewrite core_components.ex will share it in a Gist or something ;)

Yes, that's pretty much it. And we would also be glad to accept contributions so we can generate different core components out of the box.

[cultofmetatron]

its done in such a way that people will be able to write modules that automate this for you. I can already imagine a boilerplate generator being created for this