Hi folks!
I’ve been developing themes for WordPress for a while, from time to time, and I understand that Full Site Editing is getting much more stable and maybe *becoming the new paradigm*.
However, I find that is *still lacking* on a particular front: **responsiveness**.
From what I could gather, most basic blocks *don’t have responsive options*, like alternative stylings for different screen sizes, or even options to show/hide depending on the size.
The few options I found on the basic blocks is the ability to **stack or not** on mobile.
Besides that, it seems that the only way to edit responsiveness is by *actually adding custom CSS*, which kind of defeats the “full site editing experience”.
Alternatives to this include installing specific themes and plugins that come with their own sets of blocks. But as I would really want to avoid plugin bloat, this is not my favorite option.
I find very little information on the subject, and this is why I’m posting it here: *to find out how you’ve been handling this.*
Thanks!
[ad_2]
The full site paradigm doesn’t make sense at the agency level. Or at least, I don’t see it happening. Our clients don’t want to be piecing together every aspect of the site as if they were designers, so it ends up being pointless overhead. We’ve been providing a suite of custom blocks that themselves are already responsive and seamlessly work with the core blocks, and then a handful of traditional plug and play templates it can all operate within. FSE and the customizer just get disabled.
The idea of just letting them go wild building everything in the theme from components is antithetical to what these big clients hire us to do. FSE just doesn’t make sense.
I don’t want to stick my head in the sand (after all we embraced Gutenberg), but the latest core theme’s approach is insanity. I don’t know what WP is thinking anymore, or who it’s market is as a CMS.
This is a helpful resource by Mike McAlister about responsiveness in FSE / modern WordPress:
[https://olliewp.com/a-native-and-iterative-approach-to-responsive-control-in-wordress/])
I agree that there is still a lot of work to be done in this area – especially when switching from page builders with robust, granular, no-code responsiveness settings.