Improve phx.new -no--tailwind?

I started a new phoenix project with --no-tailwind and found friction:

  1. delete tailwind classes from core components
  2. delete tailwind classes from layout files
  3. figure out how to add my own style sheet (not obvious that I needed to import it in app.js )

I believe this is technically working as intended as the docs say:

the generated markup will still include Tailwind CSS classes, those
are left-in as reference for the subsequent styling of your layout
and components

However, I feel that they are more of a hindrance. Most people using -no–tailwind probably have no interest in learning what all the class names mean.

I’d like to contribute a PR to phoenix that removes the tailwind classes when the project is created with --no-tailwind. Additionally, I’d like to add a very basic style sheet. This would make the generated pages a bit more usable and provide a nice example/starting point on adding additional css.

I want to gauge the interest/feasibility from the community before spending time on this though. Thoughts?

5 Likes