Sorry if I'm being dense, but your reply seems to repeat exactly all of my points without adding any new sources or new information. To be honest, it feels as if it was generated by an LLM. Did I miss something obvious?

If Tailwind is optional, why is it included? If it is going to conflict with MUI and styling the MUI way is preferred, why have it at all?

(Haha, The LLM bit I was confused about was for this answer above, not yours. I figured you wouldn't be! Maybe I shouldn't have mentioned it at all, my bad.)

I see, thanks for the insight! I am not used to such a « maximally equipped » approach (I don't think I even saw this « distribution » approach for web projects anywhere either), but think I see the appeal.

It would be nice to mention Tailwind somewhere in the docs, and/or to also include @tailwindcss/typography and wrap RichTextInput in it in the examples.

Anyway, thanks to all the work you've all put into this, and for taking the time to reply!

Oh, I assumed that an app created with create-client would live in it's own container as a separate thing, but looking at the doc it seems to run in the pwa app too! Is this actually the main reason for including tailwind?

I haven't used create-client, but I'd have thought that it would install tailwind (or bootstrap) itself when the command runs.

(For the record, the link to the client generator in the readme seems broken: https://github.com/api-platform/api-platform#:~:text=to%20the%20client%20generator. I think it should be this one https://api-platform.com/docs/create-client/ ?)