|
|
|
|
|
by bryanrasmussen
1207 days ago
|
|
>you can easily override it from the article >First, you can customize your core UI components to suit whatever needs, designs, and tastes that you have. 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 and the generators continue to provide a great starting point for new features whether you’re a beginner, or seasoned expert building bespoke product features. I mean I would think easily overriding it would be sending a -notailwind parameter when using a site generator or something. The above is not easily although not hard either. With a small amount of effort that might irritate you if you don't want to use tailwind is what is sounds like. |
|
> 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