Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Help and Screen Options Missing #8745
Interface becomes inconsistent
Desktop (please complete the following information):
A decision was made to abandon these options because:
More discussion here #5841
I'm not certain about the help button, I think the NUX work (tips) are supposed to achieve the same goal but I may wrong cc @karmatosed
Thanks for the feedback
referenced this issue
Aug 9, 2018
Help likely will come back as we move to having keyboard shortcuts. Help could include maybe tutorials - likely a later consideration. If we did it would be that same modal. As far as screen options goes, we don't need that as the interface is different and we have pinning.
Tips is a guide and not meant to remove need for any help. It will though over time ease a lot of the things we used help in past for.
I'm thinking it would be good to keep the Help system consistent across WordPress.
Not sure what you mean about tips; generally, I've seen little tool-tip like hovering balloons or words in boxes when you mouse over a (?) next to an item that may warrant more explanation. Is that what you mean by Tips?
Definitely, and Gutenberg is providing the tools to do that for WordPress JS UIs (which we can expect more to come).
Yes, these are the tips I was talking about.
If it's ok to add my 2 cents, I think abandonning screen options is MASSIVE loss for WordPress devs who try to tailor the individual experience of their builds to their clients.
I have about 18 different metaboxes showing sometimes, and others aren't appearing for anyone (having to retrofit a lot of custom fields as we can't 'find' them in the Gutenberg interface, or delay rollout entirely). These are things our team switch 'on' or off on a per user basis when we're deploying a site to ensure their workflow is uncluttered. I do not what my clients stressing about seeing scripts added to certain pages or layout options that are targeted at specific pages. It completely interrupts their publish workflow. Screen options is a fantastic and built-in way to manage this, without having to add yet another bit of custom code or plugin to achieve something we've been able to do.
My argument is that screen options is most relevant to those of us who build sites for customers, and care about their workflow and experience of WordPress, with out us having to employ plugins or custom code to minimise the 'noise'.
I've added an example of what my client see's with, vs without screen options available.
I do not think we should have to add plugins or code to fix what was already perfectly adequate in WordPress previously.
I think you have a really good point there, and your screenshots really demonstrate the problem. I think the Gutenberg philosophy is that it will de-clutter the interface for you, and then you can rebuild the interface like you want to using the Rest API or some such thing.
However, for myself, I think the bar for learning that way of doing things is dramatically different and more difficult than the existing way that we have come to know and love.
Tammy, can the Gutenberg interface handle the additional metaboxes that are shown in the screenshots? "Groups" and "access restrictions"? Maybe this is something we would use the Advanced Custom Fields plugin for?
And is there a way to have a toggle to show the various custom fields that are used to create these metaboxes?
In this situation, there is an advantage to the power user who may know to show the hidden fields, and for the regular user to hide them.
Also it is great to be able to hide such things as the Comments or Tags metabox and so forth that we don't want to see. At the same time, some users may want to see them, so while that little help and screen options button set may be ugly, it is useful. :-)
Not having Help is an upgrade blocker for us on our (100+) clients' websites. We use it to add guidance on image sizes for certain types of Page or CPT, for example, and currently I don't see anywhere else we can put this apart from an external manual which people just won't consult. We've habituated users to check Help when they need to.