Best practice for responsive Tailwind design in Gutenberg?

Since Gutenberg doesn’t yet provide native ways of doing this (some issues linked below), I’d recommend looking at building editor plugins that add the specific controls that you need.

There is this approach if you are wanting to use Tailwind classes directly in the editor, but I would suggest trying to build out your own editor functionality that would cover any use-cases where you’d be having a user add Tailwind CSS classes — for example by adding to the InspectorControls on a per-block basis (or just build your own blocks with the settings you’d like).

3 Likes