^{Originally posted by zzap March 23, 2024}
WP-CLI is still scary to many developers, which is somewhat understandable given that it doesn't play nicely with Windows machines. A lot of developer tools, initially CLIs, have their GUIs today, and people opt to use them (which increases the fear of terminal).

So let's skip the setup part altogether and take a look at WP-CLI possibilities out of the box, i.e., hosting servers. The WP-CLI handbook already has a list of hosting providers with preinstalled WP-CLI and plugins with their custom WP-CLI commands, so we're clear on "not recommending any company or product".

We could go in general here and explain how WP-CLI can be used on the hosting provider's server, provide use cases, etc. If there were fewer providers, it would be beneficial to have a little walkthrough of the dashboard and show where the terminal is and how to start it, but each of them certainly has a guide on their blog, so we could just say, "Find the blog post and follow instructions".

I'd focus here mainly on site owners and administrators and what they can do in specific situations, e.g., manage user access (when the site is hacked or similar), install plugins for debugging and running various scans, switch to the default theme and deactivate all plugins to find the error, move a large number of posts to a different category/tag as a recommendation from an SEO agency, etc.

Goal: empower experienced users to be more advanced; support hosting providers with WP-CLI; support plugin authors who include custom WP-CLI commands; promote the WP-CLI tool as the most powerful and quickest tool for managing a WordPress instance.

The title is debatable. I don't like it, but it describes what the article is about.