[wp-trac] [WordPress Trac] #50907: Add a method to opt-in to core auto-updates.
WordPress Trac
noreply at wordpress.org
Thu Oct 8 13:44:11 UTC 2020
#50907: Add a method to opt-in to core auto-updates.
-------------------------------------------------+-------------------------
Reporter: whyisjake | Owner: audrasjb
Type: enhancement | Status: accepted
Priority: normal | Milestone: 5.6
Component: Upgrade/Install | Version: 5.5
Severity: normal | Resolution:
Keywords: early needs-docs needs-unit-tests | Focuses:
needs-design has-patch |
-------------------------------------------------+-------------------------
Comment (by karmatosed):
Thanks for everyone's work, unfortunately on review I do come back to
encouraging some deeper exploring of what this is used for. There needs to
be a little consideration over what this page is doing and how easy it is
going to achieve that.
I really think there is a danger of over-complicating here with the
scheduling, but that could be an issue with some formatting. I also agree
this leans more into needing a dedicated not only API but section.
Overall, I think reviewing what we have on a few levels is a good way to
get a solution and ship to release. The bigger sweeping comments are to
consider line-height, spacing and hierarchy. This page is visually complex
and contains a lot of content, finding ways to distil that down is
crucial.
The biggest pain point for me right now, is the density of the page
itself, adding this section has caused the capacity for this page to be
reached visually. Is there any option over having multiple save buttons? I
really would like us to reconsider how many there are on this page. Could
sectioning work? Do all these needs to be seen at the same time? Really I
would encourage some exploration that avoids what I am seeing in the
current version where we have up to 5 buttons at once on a page
potentially.
For now, I am leaving this as needs-design, I am also happy to aid with
designs, but I know others are working on things here so don't want to
jump in unless that is desirable. Let's discuss and find a way through
that results in this section being more workable going forward and small
iterations over just adding to it and causing it to become more
problematic from an experience view.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/50907#comment:41>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list