Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Experimental label from Autoloaded Options Site Health audit #409

Closed
mxbclang opened this issue Jun 30, 2022 · 3 comments
Closed
Labels
Needs Discussion Anything that needs a discussion/agreement [Plugin] Performance Lab Issue relates to work in the Performance Lab Plugin only [Type] Enhancement A suggestion for improvement of an existing feature

Comments

@mxbclang
Copy link
Contributor

As noted in #92, the Autoloaded Options Site Health audit is currently marked as Experimental, mainly because of the lack of documentation on how to clean up autoloaded options. We've created a new autoloaded options guide as part of the main WP Optimization guide, which will be updated in the plugin in v1.3.0 per #407.

This is an issue to discuss if we're now ready to remove the Experimental label from this module.

cc @felixarntz @manuelRod

@mxbclang mxbclang added [Type] Enhancement A suggestion for improvement of an existing feature [Focus] Site Health Needs Discussion Anything that needs a discussion/agreement labels Jun 30, 2022
@felixarntz
Copy link
Member

I think we could potentially remove the experimental label, certainly this is a lot closer than before. With that said though, I do think it would be great to define a bit more what the goal with this module should be. For example, there is #350 (and corresponding PR #353) which IMO would make this a lot more helpful. From that perspective, I still feel like the current implementation feels somewhat incomplete.

I think it would be good to at least have a bigger plan and outline any necessary issues for what this Site Health audit should encompass eventually. Maybe we can review the module holistically and think about it here. Are there more ways where we can help the site owner?

@manuelRod
Copy link
Contributor

We should remove the experimental label on #350 merge since it adds useful information.
@felixarntz why do you think this implementation is somewhat incomplete? I think at this stage it would have enough info to help the user (is true that not everyone would know how to do it, but at least we are pointing them in the right direction).

@felixarntz felixarntz added the [Plugin] Performance Lab Issue relates to work in the Performance Lab Plugin only label Jul 19, 2023
@mukeshpanchal27
Copy link
Member

mukeshpanchal27 commented May 27, 2024

Already fixed @sstopfer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Discussion Anything that needs a discussion/agreement [Plugin] Performance Lab Issue relates to work in the Performance Lab Plugin only [Type] Enhancement A suggestion for improvement of an existing feature
Projects
None yet
Development

No branches or pull requests

4 participants