From fb2c91f7db900187eec44398181856a78f3f4e70 Mon Sep 17 00:00:00 2001 From: Gary Kovar Date: Fri, 14 Oct 2016 08:57:11 -0400 Subject: [PATCH] Add paragraph noting packages aren't plugins. https://github.com/binarygary/db-checkpoint/issues/6#issuecomment-253785111 --- docs/commands-cookbook/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/commands-cookbook/index.md b/docs/commands-cookbook/index.md index c68ea0f4..059966dc 100644 --- a/docs/commands-cookbook/index.md +++ b/docs/commands-cookbook/index.md @@ -21,6 +21,8 @@ _But_, the WordPress admin is a Swiss Army knife of infinite complexity. There's WP-CLI commands can be [distributed as standalone packages](/package-index/), or bundled with WordPress plugins or themes. For the former, you can use `wp scaffold package` ([repo](https://github.com/wp-cli/scaffold-package-command)) to dynamically generate everything but the command itself. +Packages are to WP-CLI as plugins are to WordPress. There are distinct differences in the approach you should take to creating a WP-CLI package. While WP-CLI is an ever-growing alternative to /wp-admin it is important to note that you must first write your package to work with the WP-CLI internal API before considering how you work with WordPress APIs. + #### Command types Internal commands: