I had some problems using the visual style editor on my first try (in a Wordpress theme)
To begin with, I was searching all along the top icons for something which would invoke it (the short teaser video didn’t help me) and eventually found the words “VISUAL EDITOR” near the bottom - in case you’re still looking, any one, that’s what you click. (Obvious once you find it!)
So I got to play and created the new look I wanted - great functionality - but I couldn’t see how to save it. I wanted to modify an existing css rule but I could only see a way to create a new rule. My next challenge was to edit the actual css to copy the lines I had just saved up to the existing rule. I’ve now found how to edit the rules directly, but when I was doing this yesterday, I gave up and used an external editor. (Incidentally, the css produced by visual editor isn’t formatted nicely, the way it was from Pinegrow 2.)
My next problem was that Pinegrow 3 doesn’t appear to refresh when CSS is edited externally and saved, at least not for me. When I finally went to save in Pinegrow I got this message:
which I find confusing - the question is “Do you want to overwrite” and the possible actions are “cancel” and “save selected” and I ended up with save selected which blew away my changes. Luckily, Sublime Text" had the previous version available, Maybe “Overwrite Selected” would be better.
It’s also confusing that even when the only thing that I’m changing is in a css file, the thing that gets tagged as “changed” was (in my case) home.html and the only messages after the save name home.html.
I should note that I was getting some of these results in PineGrow 2 and I had thought it was because I was changing style.css which apparently gets special treatment. I’ve now separated out theme-specific rules into stylemods.css based on a suggestion in this forum, but it may not have helped.
It would be nice if after duplicating a css file which is enqueued, the new one is also enqueued, and there was some simple way to attach the new style to multiple pages, rather than doing it one at a time…
If all of this sounds negative, it’s not. I’m hoping that my feedback will affect the revised documentation for September, and just possibly initiate some changes in the interface. And it’s very possible that many of my problems are stemming from an inadequate grasp of how to use the product, and that someone will point out my error!!