Our current discussion of show/hide function from this thread is just one example of how Classic works quite well. In Classic the show/hide button is right on the toolbar so when my side bar is collapsed, as it often is when I view from a smaller laptop, this feature is still accessible.
Ideally both show/hide and “don’t publish” would be accessible without the side panels but Classic in this example is still working about 90% optimally. Other posters have made the point that you should look into other options besides the drop-down such as check-boxes, radio buttons.
In the past I’ve tried to mention stacks features that were useful to my workflow but some of those posts got deleted by the other Dan. It is hard for me to have that discussion about which features work on what framework and how they compare when my posts keep getting taken down. I’m okay spending some time talking about what a framework like elements might become but ultimately I’m going to talk about my production setup, of course, because it does all the work.
I understand it’s different to Classic/Stacks. It’s probably more useful in Stacks as you often want to hide things more often as they don’t look how they do in preview, so they are just getting in the way. But it’s a different story in Elements as it’s WYSIWYG.
There’s always a learning curve when switching to a new app, but we have been working super hard to ensure ALL the features, and so many more that users have been requesting for years are available and built-into Elements. Once you get the hang of Elements, you’ll wonder how you ever built website in Classic!
Are there any other specific features you’d like to see in Elements? Please let us know
