How can a front-end developer collaborate with a back-end developer on a Phoenix 1.7 and LiveView project?

[Kurisu]

First of all, thank you for your valuable answers. I already have some ideas on how to put them into practice.

@Arz

To use Tailwind you should be using components (like you would in React etc.). If you don’t, then it will be hard to maintain the CSS.

Yes, that’s the feeling I had too. In fact we had already collaborated in the past on projects without LiveView and with versions of Phoenix prior to 1.7. There were no Components and it was easier to have a static HTML template that I integrated into Phoenix.

@Arz

Any specific questions please let me know. I’ll do what I can to help

You have already done a lot by sharing your valuable experience. This sheds a lot of light on my uncertainties. Maybe do you have any suggestions for reading (books) to learn Tailwind CSS quickly?

@eahanson

Just a note that Tailwind is only the default for the Phoenix generator. As far as I know, there’s no Phoenix-related downside to replacing Tailwind with something else, if there’s something else that you or the front-end dev prefers.

Maybe I am wrong but for example this thread (LiveView phx-no-feedback without tailwind) seems to suggest that I won’t have forms validation feedback out of the box in LiveView if I drop the default tailwind.config.js plugin for assets management. I saw some workarounds in the thread but also in a Blog post (Phoenix 1.7 and Bootstrap 5 - Tutorials and screencasts for Elixir, Phoenix and LiveView see 3.3 Form validation), but in my opinion that is more work to do.