Just an opinion regarding Enfold's responsiveness

At the time being I maintain about 20 Enfold installations. I really like the theme and use it in general with joy. The clients are happy when everything works and looks like they knew best it would be the best in the first place, they are indifferent about how it was done. As we know it. Their only annoyance is going the get that theme token in a universe they are not common to. But they survive and most thrive.

And they do not know about the massacre behind the scenes. Because when trying to reach elegant responsiveness I always have to duplicate entries in Enfold, change visibility and create an element massacre. And create pageload. Hurt their chances with google. The alternative would be to deep dive in the screen sizes in css and fiddle with directions and orders. Which I could avoid until now. And I want to keep it that way. When you have to edit something on those pages, there are feelings rising… You realise that you do not want your customers to change something for the better. And this is not good.

Some days ago I had to change a self made php-injection fed from a database un til then to static content for reasons. 60 pages plus in the first run. Now css handling for that is back with WordPress/Enfold and here the major annoyance starts. It was about coding now. Not just that it did not work smoothly to give a class name in developer settings to the column as – I think – it should: It did not show up until I put the generic name in both(!?) the class name fields and the id field. Whatever, maybe a fallback of some sorts I missed in the change log. In the end it worked, albeit clumsy.

Then I wanted to start designing and setup a place in the css section of “general styling”, which is my css playground. I realised that it is not just a mess to generally switch two columns in a 3 column design. It did not work for more than 2 hours and I did not know…
– did I forget to put any “!important” anywhere? It is not self explainatory where it would have to be used and where not to be used after all that time? Why do I do not know that after using Enfold seemingly from the beginning on?
– why cann’t I control settings that are presented to me as saveable settings with confidence and am unsure where the error lies? Or if there’s any? Or not? Or what?
– is there a pending bug? Should I go to the forum which is great tbh, but eats away my time?
– is it something about cacheing inside enfold? Is everything off (minification, combination, whatever) ans will I remember to put it back on after every minute change?

… and then I realised that this is not what I came to Enfold for.
I can write you down the css of what I want in a plain file just so. It is not that hard, even fluid design and flexboxes and the media stuff. I just look up what I have to. Then I debug it in a straight manner and then it is done. And it is all in plain sight for me. All in one place. Controllable. I know it’s rules and add mine. In the end I know what I’ve done and I know how and why it works.
Today for the first time I realised that Enfold, which I love, stands in my way of creating. And it does that too much to further ignore it. I developed habits around Enfold. Regarding responsiveness it was and is the burden to be overcome. But no, Sir. Creating websites and applications today is more than putting margins on headings reliably. In its core it should let me embrace a quick and controllable approach to responsiveness as well, imho.

I do not feel supported bny Enfold, which I regard as my companion.
We have come far together, don’t let me down on this, bro.

Please make responsiveness easier and more versatile. Let it have SOME user friendliness or even some elegance. Let it feel like working with a theme here, instead of working against it.
I started using enfold, because I did not want to be mainly a coder anymore and was seeking for help. And finding it in Enfold, back when mobile was far from being first.
Then everything became fluid and flexible and I now want to have a comfortable way of adapting to that and create with it. Badly.
Responsiveness is so basically needed today that a theme(!) with such a builder(!) should handle that way more elegant.
The CSS control in the theme is for corrections, not for handwritten code based handling of whole aspects of website deployment.

The technology is around for long now,
Please be the Enfold of 2021.

• This topic was modified 3 years, 6 months ago by eee_lala.