[wp-trac] [WordPress Trac] #47046: Site Health: Remove grading

[WordPress Trac]

#47046: Site Health: Remove grading
----------------------------+---------------------------------
 Reporter:  Cybr            |       Owner:  (none)
     Type:  enhancement     |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  site-health     |     Focuses:  ui, administration
----------------------------+---------------------------------

Comment (by Cybr):

 ''How was this assigned to "Shortcodes" in the first place?''

 Anyway, thank you so much @Clorith for your engaging interest and time
 spent on this project!

 I'd also like to thank you for the additional insights on some of the
 possible features we can integrate. I added those to my list!

 You're right on my code-rip; I was a few (200...) commits behind :) But,
 upon closer inspecting, I think the API overly prefers PHP 7.3, and it
 will emit a critical warning when 7.2 is used; regardless of it being up-
 to-date.

 I believe it should favor the latest version of all active branches. To
 only start showing warnings when the branch is phasing out, and finally
 with errors when it's no longer supported: https://www.php.net/supported-
 versions.php

 The reason I highlighted performance is that I chose and tweaked the
 extensions that were used by WordPress, so no less-favorable fallbacks
 were used. A few critical modules are missing in the list from the Hosting
 Team, so may I suggest these to be added (yes, a new ticket would be
 better...):
 - iconv
 - mbstring (this is a must, +7000x faster than fallbacks, plus
 [https://core.trac.wordpress.org/ticket/34631 not all functions are
 covered])
 - opcache (or equivalent)
 - zip

 I could go on in excruciating detail, like setting the php.ini's
 `serialize_precision` to `-1`. But, we digress even further.

 As for the wording in the documentation, this is what we'll find out after
 the fact. Support requests will paint a better picture. As far as I know,
 these tests have only gone by developers and enthusiasts, not the general
 public.

 One thing that comes to mind is that the Hosting Team's handbook page may
 have to inform the user on how to fix this. For instance, provide a link
 to the example letter to the hosting provider,
 [https://wordpress.org/support/update-php/#how-to-update-your-websites-
 php-version-for-a-faster-more-secure-website as done here]. Alas, I don't
 know if this is required; we'll have to wait and see. Ultimately, hosting
 providers should follow that list preemptively.

 Now, as for this comment:
 > [...] it's a progress indicator of how many tests are passing, maybe
 it's not super clear.

 Exactly, that's my initial concern. I still believe this is based on a
 point system, not a progress indicator—"x out of y" were marked completed,
 which is where I hope this will head to.

 So, instead of giving a % completed, give real numbers, no colors, gauges,
 or other game-esque stuff, simply put:
 "11/15 checks passed."

 I think we'll come a long way if we only change the "66%" to "11/15"
 (which is actually 73%...). Do mind the overflow.
 And, instead of coloring the wheel based on progression, I propose making
 it just blue (or the admin theme color).

 Again, I do believe these checks will help us all. I am, however, still
 afraid of future implications and turning this into a game. Although, I'm
 very thankful for handing us your reins :) Cheers!

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/47046#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform