This small, but oh so handy feature is coming in the next build of Elements 3 
Small update on this to explain the feature…
Is this what you guys wanted? Did we miss anything?
This definitely looks like a handy feature.
Oh yes 
Thank you! An eye icon in the tree would be plenty for me, but the grey “visible but not published” option wins the award. It’s very useful, and it makes sense to have it in the inspector rather than the tree.
Brilliant!
I run a football club website and wanted to add a section of condolence for ex-players that have passed away. I didn’t want to create a whole new page but actually wanted it to appear on the home page so visitors automatically see it, now I can ‘hide’ and ‘not publish’ the rest of the page for a period of time before returning home page back to normal state.
This what I need
It would be great if this new hide/show feature could eventually be extended to connect with a calendar and timing rules, so elements could reappear automatically without manual attention.
I wonder if the Countdown component from @MultiThemes would work for you?
Thanks for the tip, but I like idea of the new show and hide function connected to a calendar better )
@barz-stacks offers some components for event management. And also a component. Smart Countdown
This is such a great implementation.
It’s this kind of thoughtfulness that makes Elements a delight to use. Easy to not publish anything, and a subtle visual cue showing that it won’t go live.
Dan I do actually use this feature all the time, in fact I use it on every webpage. Part of my main workflow is to test out several alternate ways to display something to see if there are better or more interesting ways to do something but of course I don’t want to have five variations on an idea posted when I go to upload so hiding is imperative.
I’m not looking to get a site done fast like with AI features I just want the best implementation which requires testing several ways that a feature can work. The way elements 2 has been setup I would have had to make a test page for every single page of the site just so I could try out new ideas, completely impractical workflow.
Also right now the function “hide in editor” does not have a way to unhide the element! In Classic the hide feature lets you see the title of the element so that you can easily make it visible again. Probably just a beta bug though.
Use the Node Browser to select the component you’ve hidden.
There needs to be a some kind of visual indication in the node browser that the element has been hidden. It is too confusing to click on an item and have nothing be selected in the main webpage area. Maybe even a viewing eye button next to the hidden item. If “do not publish” grays the element out on the page I can’t see why the same effect couldn’t applied to the node browser element.
@dan This new feature is incredibly handy, but I’m finding the fact that they are mutually exclusive a bit of a workflow hurdle. Very often I want some element to not be published but also be hidden; the only way I can accomplish that is by using the hidden option in the layout setting. My hope was that I could achieve this using these new options.
From a UI perspective, I think they would have been a lot more useful as checkboxes instead of a dropdown menu. If only because you can then glance at the inspector and see exactly what is going on without having to click. Although with the current implementation they would have to be radio buttons, I suppose. I can see situations where I would want at least the first two options to be active at the same time. This would be useful if I have a large section I don’t want to see in the editor, but I want it to be visible when previewed.
I also think it would be extremely helpful if there was some sort of indicator in the node browser as to the state of the element.
I agree that these states would be much easier to work with if they were visible at a glance in the Node Browser.
Being able to combine “do not publish” with “hide in editor” also seems useful, because those are really two different decisions: whether something appears in the editor, and whether it is included in the published site. Treating them independently would make the feature much more flexible.